Comments
2 comments
-
-M-
We think we have a fix for this issue, but the problem we have is that this error message can occur for a number of reasons. The first step to debuging the problem is for you to run a SQL Server profiler trace as the databases are registering. Stop profiler after the error has occur and send me the trace. I will then advise you as to the next steps, if you have some example schema of the problem that would be useful too.
My email address is: jonathan [dot] watts [at] red [dash] gate [dot] com.
Kind regards,
Jonathan -
Jonathan,
Thanks for letting me know you found a fix which will be released in a couple of days.
Can you tell me how to get the release, once it's available? Will it be posted to these boards or can I run the "check for updates" within the application to pick up the fix when it comes out?
Thanks
Add comment
Please sign in to leave a comment.
At the bottom is the message saying "Object reference not set to an instance of an object"
Any ideas. I compare these two databases frequently using SQL Compare 5.
Thanks.