object reference not set to an instance of an object?

• 
  When I compare any 2 databases it fails during the Registering Databases step on the [servername].[databasename]-Reading object text with the error "Object reference not set to an instance of an object".
  
  Both servers are remote and are SQL 2005
  I'm running Windows XP SP2 fully patched

  Tobyh May 16, 2007 04:58

  - 0 +
• 
  Just being doing some more checking, and found it is just one of our databases.
  
  Tried comparing 10 others and they compare fine so far.
  
  It is just the one database, I can't find any logs created by your program. Is there away to turn logging on so I can give you more information ?
  
  Toby

  Tobyh May 16, 2007 05:26

  - 0 +
• 
  Tobyh,
  
  Is this a regression, can you check whether it is happening with SQL Compare 5 too? Unforuntately there isn't any logging with SQL Compare as such. The best thing to is run a trace with SQL Profiler on the affected database, and send us the trace.
  
  My email is jonathan [dot] watts [at] red [dash] gate [dot] com.
  
  Thanks,
  
  Jonathan

  JonathanWatts May 16, 2007 06:29

  - 0 +
• 
  Hi ,
  I had the same error message.
  
  I tried 4 databases and nothing to do.
  With every possible pattern.
  
  I had Toolsbelt 5 installed, XP , SQL 2000.
  
  Thanks

  rickybibi May 16, 2007 07:14

  - 0 +
• 

  Jonathan Watts wrote:

  Tobyh,
  
  Is this a regression, can you check whether it is happening with SQL Compare 5 too? Unforuntately there isn't any logging with SQL Compare as such. The best thing to is run a trace with SQL Profiler on the affected database, and send us the trace.
  
  My email is jonathan [dot] watts [at] red [dash] gate [dot] com.
  
  Thanks,
  
  Jonathan

  
  Works fine on SQL Compare 5 and I've sent you the trace

  Tobyh May 16, 2007 07:25

  - 0 +
• 

  Tobyh wrote:

  Jonathan Watts wrote:

  Tobyh,
  
  Is this a regression, can you check whether it is happening with SQL Compare 5 too? Unforuntately there isn't any logging with SQL Compare as such. The best thing to is run a trace with SQL Profiler on the affected database, and send us the trace.
  
  My email is jonathan [dot] watts [at] red [dash] gate [dot] com.
  
  Thanks,
  
  Jonathan

  
  Works fine on SQL Compare 5 and I've sent you the trace

  
  Thanks. I or one of my colleagues will start looking into this shortly.
  
  rickybibi
  
  This issue can occur in SQL Compare 5 too, usually due to permissions or full text index issues, so the first thing we need to establish is if this is a regression.
  
  If you can run SQL Compare 5 against the same databases and tell me if you get the same error this would be very helpful.
  
  Regardless of whether this occurs in SQL Compare 5 or both versions then the best way for us to find out what the problem is if you run a SQL Server profiler trace as the databases are registering. If you stop profiler after the error has occur and send us the trace we may be able to work out where SQL Compare is going wrong.
  
  My email address is: jonathan [dot] watts [at] red [dash] gate [dot] com.
  
  Kind regards,
  
  Jonathan

  JonathanWatts May 16, 2007 07:27

  - 0 +
• 

  Jonathan Watts wrote:

  
  Thanks. I or one of my colleagues will start looking into this shortly.
  
  rickybibi
  
  This issue can occur in SQL Compare 5 too, usually due to permissions or full text index issues, so the first thing we need to establish is if this is a regression.
  
  If you can run SQL Compare 5 against the same databases and tell me if you get the same error this would be very helpful.
  
  Regardless of whether this occurs in SQL Compare 5 or both versions then the best way for us to find out what the problem is if you run a SQL Server profiler trace as the databases are registering. If you stop profiler after the error has occur and send us the trace we may be able to work out where SQL Compare is going wrong.
  
  My email address is: jonathan [dot] watts [at] red [dash] gate [dot] com.
  
  Kind regards,
  
  Jonathan

  
  I've sent a trace of both version 5 and 6. Currently we are not having any problems with version 5.
  
  Toby

  Tobyh May 16, 2007 07:46

  - 0 +
• 
  I'm seeing it on a 2000 database while "Reading Ojbect text". It works on version 5, but it does slow down on 5 while going through that step. This is the first 2000 database I've run it against. It looks to be this database because I've checked different servers that have it. Let me know if you need more information.

  Grant Fritchey May 16, 2007 08:43

  - 0 +
• 
  Granted,
  
  If you can sent me the trace, see instructions above, I will take a look and see if this is the same problem or a different one.
  
  Thanks,
  
  Jonathan

  JonathanWatts May 16, 2007 09:08

  - 0 +
• 

  Jonathan Watts wrote:

  Granted,
  
  If you can sent me the trace, see instructions above, I will take a look and see if this is the same problem or a different one.
  
  Thanks,
  
  Jonathan

  
  On it's way.

  Grant Fritchey May 16, 2007 09:39

  - 0 +
• 
  I can successfully compare all of my databases in either SQL 2000 or SQL 2005 using SQL compare 5. The problem only occurs if I switch to SQL compare 6. I do have full-text indexes in each database.

  rbennet8 May 16, 2007 10:22

  - 0 +
• 
  Okay, it looks like we have a regression, we are taking this problem very seriously as it is effecting so many of you and is having a very negative effect on the Beta. Hopefully, if we find a fix we can patch the beta.
  
  If you can sent me a trace as described above I will see what I can do about debuging this problem. However, we haven't seen this during any of our testing, but there are a number of possible causes of this error, and without a trace we cannot tell where the problem is occuring.
  
  Regards,
  
  Jonathan

  JonathanWatts May 16, 2007 10:57

  - 0 +
• 

  Jonathan Watts wrote:

  Okay, it looks like we have a regression, we are taking this problem very seriously as it is effecting so many of you and is having a very negative effect on the Beta. Hopefully, if we find a fix we can patch the beta.
  
  If you can sent me a trace as described above I will see what I can do about debuging this problem. However, we haven't seen this during any of our testing, but there are a number of possible causes of this error, and without a trace we cannot tell where the problem is occuring.
  
  Regards,
  
  Jonathan

  
  Were you able to replicate the problem with scheme I sent you ?
  I my case it seems to be a problem with the store procedures.
  
  Toby

  Tobyh May 17, 2007 05:28

  - 0 +

Add comment

Please sign in to leave a comment.