M
Mark
I'm running the OMPM OffScan.exe to collect document information and
importing into an OMPM database on SQL Server 2005. During the import I am
running into frequent errors which indicate:
"CRITICAL ERROR: The mapping phase of import unexpectedly failed. Your
database may be in an unstable or corrupt state.
[Microsoft][ODBC SQL Driver][SQL Server]Violation of PRIMARY KEY constraint
'PK_FileIssue'. Cannot insert duplicate key in object 'dbo.omFileIssue'.
Please see the OMPM documentation for more information:
http://technet2.microsoft.com/office/f/?en-us/library/eabaaa29-afc9-4cb3-bdd0-2f09d3fae1831033.mspx"
Frustratingly enough, the url indicated says that if you receive this error
message, your database is now corrupted and you have to do the following:
• Delete the existing database.
• Create a new database.
• Move all of the CAB files out of the OMPMImported folder.
• Re-import the scan data and action CAB files.
I've received this error 4 or 5 times while importing about 200 CABs so far.
I've begun backing up my database before every batch of imports so that I can
restore when I get this error and not have to go through the imports all over
again.
When I run into a CAB that generates this error, I've resorted to extracting
the CAB and importing the XML files in smaller batches. Oddly enough, if I
import in small enough batches it seems to successfully import all of the XML
files without error. This is inconsistent however and I've had to restore SQL
backups enough times that I feel like I can do it in my sleep now.
Has anybody else run into this problem? I've still got a lot more scans to
import and this trial and error process of backing up, importing, and
restoring when I see an error has taken up far more time than expected with
this tool.
If anybody has advice on making these imports more successful I would be
very grateful. Thanks!
/Mark
importing into an OMPM database on SQL Server 2005. During the import I am
running into frequent errors which indicate:
"CRITICAL ERROR: The mapping phase of import unexpectedly failed. Your
database may be in an unstable or corrupt state.
[Microsoft][ODBC SQL Driver][SQL Server]Violation of PRIMARY KEY constraint
'PK_FileIssue'. Cannot insert duplicate key in object 'dbo.omFileIssue'.
Please see the OMPM documentation for more information:
http://technet2.microsoft.com/office/f/?en-us/library/eabaaa29-afc9-4cb3-bdd0-2f09d3fae1831033.mspx"
Frustratingly enough, the url indicated says that if you receive this error
message, your database is now corrupted and you have to do the following:
• Delete the existing database.
• Create a new database.
• Move all of the CAB files out of the OMPMImported folder.
• Re-import the scan data and action CAB files.
I've received this error 4 or 5 times while importing about 200 CABs so far.
I've begun backing up my database before every batch of imports so that I can
restore when I get this error and not have to go through the imports all over
again.
When I run into a CAB that generates this error, I've resorted to extracting
the CAB and importing the XML files in smaller batches. Oddly enough, if I
import in small enough batches it seems to successfully import all of the XML
files without error. This is inconsistent however and I've had to restore SQL
backups enough times that I feel like I can do it in my sleep now.
Has anybody else run into this problem? I've still got a lot more scans to
import and this trial and error process of backing up, importing, and
restoring when I see an error has taken up far more time than expected with
this tool.
If anybody has advice on making these imports more successful I would be
very grateful. Thanks!
/Mark
