chrisk5 wrote:The "Object reference not set to an instance of an object." error message is rather generic error message, so I think we need some more information to decide what has gone wrong.
Would it be possible for you to try running a comparison in SQL Compare with the same two databases. I would like to know whether you encounter the same error message or if the comparison goes through. If you are able to recreate the same error message, please can you follow these steps.
- enable error logging, as described in this document:
http://www.red-gate.com/SupportCenter/C ... _log_files
- recreate the error message one more time.
- disable error logging, as described in the above document (the file can grow very quickly so please try not to leave this running too long).
- locate the log file and send to firstname.lastname@example.org quoting the support ticket number F0061318.
If you have any problems, then please let me know (either by email or posting back here).
"C:\\Program Files (x86)\\Red Gate\\SQL Packager 6\\SQLPackager.exe" /database1:NEW /u1:sa /p1:superpassword /database2:OLD /u2:sa /p2:superpassword /location:"C:\\Users\\Administrator\\Desktop\\test" /name:TestPKG /makeexe /verbose
Comparing database (local).NEW with database (local).OLD...
DGapp wrote:I get this error fairly frequently myself, and it almost always happens when there are newer table(s) and stored procs, and most often when the newer table(s) have no data on them. Usually I can exclude them and move on and some point later it works fine. I haven't been able to exactly pin it down, but it's almost always the "build" process when new tables are included or the very next one after they were introduced. It's quite frustrating
Users browsing this forum: No registered users and 0 guests