Import DB Heath Error

Epicor ERP 10
1

This morning I was doing an fix for the Min Max Safety issues I noticed. And I told Epicor help that my system was 10.1.400.19, and in fact, under help, that is what it says. However, I got an error that said, can’t apply the fix 10.1.400.19 to a 10.1.400.0.

System.Exception: The following error happened while trying to import SQL scripts:

Data Fix for Version 10.1.400.19. Cannot be installed on 10.1.400.0. —> System.Exception: Data Fix for Version 10.1.400.19. Cannot be installed on 10.1.400.0.

at Epicor.Tools.DataFixImport.Import.CallImport(String dataFixId, DataClassesDataContext context, String username, List`1 datafixProcs)

at Epicor.Tools.DataFixImport.Import.LoadFixStoredProcedure(String dbServer, String dbName, String authenticationMode, String userID, String password, String filename)

at Epicor.Mfg.Administration.ServerManagement.DatabaseManager.Forms.WorkInProgressForm.BackgroundWorker_ImportSqlScripts(String sqlServerName, String databaseName, String authenticationMode, String databaseUserName, SecureString userPassword, List`1 sqlScriptFilePaths)

— End of inner exception stack trace —

at Epicor.Mfg.Administration.ServerManagement.DatabaseManager.Forms.WorkInProgressForm.BackgroundWorker_ImportSqlScripts(String sqlServerName, String databaseName, String authenticationMode, String databaseUserName, SecureString userPassword, List`1 sqlScriptFilePaths)

at Epicor.Mfg.Administration.ServerManagement.DatabaseManager.Forms.WorkInProgressForm.BackgroundWorker_DoWork(Object sender, DoWorkEventArgs e)

at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)

at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

2

Fix1
Fix1.JPG1661×281 33.1 KB

3

Call back into support with what you described here. There WAS an issue with the version checking at one point. I thought that was fixed long ago though.

2 Likes
4

Yeah I did that. Just didn’t know if anyone here had ran into something similar. I don’t understand why that error was given considering it even says it the .19 version.

5

I remember we had an ‘if/then’ check that got messed up checking that but though we fixed that up long ago #interested

6

In the zip file that comes with our health checker there is an assembly that must be copied to “C:\Program Files (x86)\Common Files\Epicor Software\Database Manager Extensions\3.1.X00\Epicor.Tools.DataFix.DLL” on before the import of the .DF file (where 3.1.X00 is the release you’re on). Not using the .dll with the particular heath checker/data fix before import can cause an error like this.

image

1 Like
7

@aidacra My menu path is C:\Program Files (x86)\Common Files\Epicor Software\Database Manager Extensions\3.1.400

I had a tech do a webex to verify everything and we even redid everything and go the same error. The tech was very confused. And the original guy helping me is probably pulling his hair out because he keeps telling me to use the files, and I’m like, yeah, that’s what we did.

8

fix2
fix2.JPG1200×669 94.3 KB

9

So would the fact that my file path doesn’t state 3.1.400.19 cause an issue if my system is 10.1.400.19?

10

fix3
fix3.JPG1206×643 46.9 KB

11

can you send me the data fix we sent you to naanderson AT epicor DOT com? I’ll test it internally just to make sure everything is as expected.

12

Just did.

13

I have a 10.1.400.14 database (otherwise, all other dbs I have access to are 10.1.400.25+) and it was successful against that. All I did was replace the existing Epicor.Tools.DataFix.dll

image
image.png1077×282 27.4 KB

with the one in the data fix .zip file

image

restarted my EAC, and it imported without issue :confused:

14

Ok, restarted the EAC, whats taht?

15

EAC = Epicor Administration Console.

16

Ah, how do you restart that?

17

Close the Epicor Administration Console (File > Exit within the EAC or click on the X on the top right of the EAC window) and then relaunch the EAC from the Start Menu / desktop on your Epicor server.
image

18

Ok, I’m leaving the office soon, so I’ll do this tomorrow morning and see how it goes. But very much a pain.

19

@aidacra Well, I had to open the Admin Console, then put the dll in, then restart the console. That worked. Don’t know why, but if I did it any other way, it just wouldn’t work.

On a completely different issue, any knowledge of why the price list, when exported from Epicor, rounds the numbers to the nearest cent instead of leaving exactly what has been inputted into Epicor? BAQ shows the exact price, and the exact price shows up every other time, but not when exporting.