November 20, 2008 at 6:30 am
Errors ‘Specified cast is not valid’ when using SQLH2 One of the instance on the server reports the database other fails
19/11/2008 14:35:24 Status: Running SQL collector on SERVER NAME\SQL2000
19/11/2008 14:35:24 Status: Opening Unit 5 (Server Properties)
19/11/2008 14:35:24 Status: Closing Unit 5
19/11/2008 14:35:24 Status: Opening Unit 1 (Databases)
19/11/2008 14:35:28 Status: Closing Unit 1
19/11/2008 14:35:28 Status: Opening Unit 2 (Current Configuration)
19/11/2008 14:35:28 Status: Closing Unit 2
19/11/2008 14:35:28 Status: Opening Unit 3 (Running traces)
19/11/2008 14:35:28 Status: Closing Unit 3
19/11/2008 14:35:28 Status: Opening Unit 6 (Server Objects)
19/11/2008 14:35:28 Status: Closing Unit 6
19/11/2008 14:35:28 Status: Opening Unit 4 (Registry)
19/11/2008 14:35:28 Status: Collecting Watson settings from Registry
19/11/2008 14:35:28 Status: Collecting dumps info
19/11/2008 14:35:28 Status: Closing Unit 4
19/11/2008 14:35:28 Status: Initializing collector: SQL
19/11/2008 14:35:28 Status: Running SQL collector on SERVER NAME\SQL2005
19/11/2008 14:35:28 Status: Opening Unit 5 (Server Properties)
19/11/2008 14:35:28 Status: Closing Unit 5
19/11/2008 14:35:28 Status: Opening Unit 1 (Databases)
19/11/2008 14:35:39 ERROR: Specified cast is not valid.
19/11/2008 14:35:39 ERROR: Unit 1 failed
19/11/2008 14:35:39 Status: Closing Unit 1
19/11/2008 14:35:39 Status: Opening Unit 2 (Current Configuration)
19/11/2008 14:35:39 Status: Closing Unit 2
19/11/2008 14:35:39 Status: Opening Unit 3 (Running traces)
19/11/2008 14:35:39 Status: Closing Unit 3
19/11/2008 14:35:39 Status: Opening Unit 6 (Server Objects)
19/11/2008 14:35:39 Status: Closing Unit 6
19/11/2008 14:35:39 Status: Opening Unit 7 (SysPerfInfo)
19/11/2008 14:35:39 Status: Closing Unit 7
19/11/2008 14:35:39 Status: Opening Unit 4 (Registry)
19/11/2008 14:35:39 Status: Collecting Watson settings from Registry
19/11/2008 14:35:39 Status: Collecting dumps info
19/11/2008 14:35:39 Status: Closing Unit 4
April 3, 2009 at 3:18 pm
I have the same error, but only in a SQL server 2005 instance, because with an SQL Server 2000 instance it works fine
Guillermo
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply