Upload DB to EpicWeb

Yahoo Archive
1

I am having problems and logged a support call with Epicor.

 

However, I found out this morning – that they have no record of my support call – however – I have a support email with a call number.

 

The file looked like it was transferring – never completed – and then starts transferring again.

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Thursday, November 19, 2015 1:44 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Upload DB to EpicWeb

 

 

Does anyone else have trouble uploading a database to EpicWeb? I've done it in the past with the same setup I'm on now without problems. In March I ended up having to mail a copy of our DB on a zip drive to support after numerous failed attempts to upload our db. Tech support kept telling me I had a bad backup. I tried zipping the DB backup (both off and on line backups), unzipping and restoring it to a test DB on the same and on a different server with absolutely no errors. I restore DB backups to test databases and test servers on a regular basis and have never had one fail. The file uploads using FileZilla without errors.The same thing is happening again. They get "CRC failed. The file is broken." errors. I have absolutely no idea what to do. Support just keeps telling me the same thing...do another backup and try again. I wait a week for an answer that the file is bad and to do another backup and try again. Getting pretty frustrated! Any ideas? Our DB backup zipped size is a little under 3 GB, the unzipped size is a little over 13 GB.

Sue

 

2
Does anyone else have trouble uploading a database to EpicWeb? I've done it in the past with the same setup I'm on now without problems. In March I ended up having to mail a copy of our DB on a zip drive to support after numerous failed attempts to upload our db. Tech support kept telling me I had a bad backup. I tried zipping the DB backup (both off and on line backups), unzipping and restoring it to a test DB on the same and on a different server with absolutely no errors. I restore DB backups to test databases and test servers on a regular basis and have never had one fail. The file uploads using FileZilla without errors.The same thing is happening again. They get "CRC failed. The file is broken." errors. I have absolutely no idea what to do. Support just keeps telling me the same thing...do another backup and try again. I wait a week for an answer that the file is bad and to do another backup and try again. Getting pretty frustrated! Any ideas? Our DB backup zipped size is a little under 3 GB, the unzipped size is a little over 13 GB.

Sue


3
That issue most of the times is because they are trying to restore to the wrong version of SQL. (I've seen) Can you check what version of SQL you ahve VS what they are loading it?


Jose C Gomez
Software Engineer


T: 904.469.1524 mobile

Quis custodiet ipsos custodes?

On Thu, Nov 19, 2015 at 3:44 PM, snielsen.hipco@... [vantage] <vantage@yahoogroups.com> wrote:

 
<div>
  
  
  <p>Does anyone else have trouble uploading a database to EpicWeb? I&#39;ve done it in the past with the same setup I&#39;m on now without problems. In March I ended up having to mail a copy of our DB on a zip drive to support after numerous failed attempts to upload our db. Tech support kept telling me I had a bad backup. I tried zipping the DB backup (both off and on line backups), unzipping and restoring it to a test DB on the same and on a different server with absolutely no errors. I restore DB backups to test databases and test servers on a regular basis and have never had one fail. The file uploads using FileZilla without errors.The same thing is happening again. They get &quot;CRC failed. The file is broken.&quot; errors. I have absolutely no idea what to do. Support just keeps telling me the same thing...do another backup and try again. I wait a week for an answer that the file is bad and to do another backup and try again. Getting pretty frustrated! Any ideas? Our DB backup zipped size is a little under 3 GB, the unzipped size is a little over 13 GB. <br><br>Sue<br></p><p><span><br></span></p><p></p>

</div>
 


<div style="color:#fff;min-height:0;"></div>

4
We don't use SQL, we're on Progress, but I will ask if they're restoring it to an environment that matches mine. There's got to be something wrong somewhere. Thanks!

Sue
5
>>Upload
Are you using the latest upload instructions from Epicor?
For the most part they should work, I think they recommend FileZilla now.

But, I've still had problems at times... from different sites, SQL and Progress.
Recently FTP uploads started failing after they had been working. Something had changed on their end. It took about two weeks back & forth with tech support before they got it working again.


At another site we never could find a solution. In that case we finally burned the db to a disk and mailed it in to the Minneapolis address. Only 2 days to get loaded then... after a month fighting FTP.
6
My last DB upload to EpicWeb was done on 01/27/2014 using FileZilla. The next attempt was in March of 2015 and it bombed. I did the same thing...mailed it to them. I didn't have much luck working with tech support on the upload. My support person just forwarded emails between tech support and me suggesting that the backup was bad, do a fresh backup (sometimes an offline backup was suggested), and try again. I even signed up for a trial on another ftp site to test the process; no problems there. I think I'll try placing a new support call with the upload issue and see if I can get it resolved that way. I appreciate your reply, at least I know it's not just me with the problem!

Sue


---In vantage@yahoogroups.com, <bruce.d.ordway@...> wrote :

>>Upload
Are you using the latest upload instructions from Epicor?
For the most part they should work, I think they recommend FileZilla now.

But, I've still had problems at times... from different sites, SQL and Progress.
Recently FTP uploads started failing after they had been working. Something had changed on their end. It took about two weeks back & forth with tech support before they got it working again.


At another site we never could find a solution. In that case we finally burned the db to a disk and mailed it in to the Minneapolis address. Only 2 days to get loaded then... after a month fighting FTP.