ODBC error adding monitors after upgrade to 12

To the Ipswitch web site

Ipswitch Forums
Home      Members   Calendar   Who's On
Welcome Guest ( Login | Register )
      


««1234»»»

ODBC error adding monitors after upgrade to 12Expand / Collapse
Author
Message
Posted 6/12/2008 8:31:51 AM
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Group: Forum Members
Last Login: 6/30/2008 12:56:56 PM
Posts: 43, Visits: 129
bump

anyone?

Post #44560
Posted 6/12/2008 9:15:05 AM
Time Traveler

Time TravelerTime TravelerTime TravelerTime TravelerTime TravelerTime TravelerTime TravelerTime Traveler

Group: Ipswitch Employees
Last Login: 2 days ago @ 4:00:28 PM
Posts: 152, Visits: 666
What is the name of the computer where your SQL Server hosting the WhatsUp database is installed (if you are using the default SQL Server 2005 Express, this is also the system where WhatsUp is installed)? Is it different that "MONITORWORLD"?
Post #44561
Posted 6/16/2008 7:46:56 AM
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Group: Forum Members
Last Login: 6/30/2008 12:56:56 PM
Posts: 43, Visits: 129
AmbarK (6/12/2008)
What is the name of the computer where your SQL Server hosting the WhatsUp database is installed (if you are using the default SQL Server 2005 Express, this is also the system where WhatsUp is installed)? Is it different that "MONITORWORLD"?

the computer name is called "ndwhatsup", same as it was with version 11 installed. Both the whatsup program and database are on teh same machine. I've tried switching the drivers back and forth between SQL Server 2005 "Microsoft SQL Native Client Version 09.00.3042" and what it was left as after the upgrade  "Microsoft SQL Server ODBC Driver Version 03.85.1117" which was what the version 11 used so it didn't seem right.

The test connections complete successfully, and the whatsup polling engine is connected...just get that wicked error mentioned in the first post

Post #44640
Posted 6/16/2008 9:15:49 AM
Time Traveler

Time TravelerTime TravelerTime TravelerTime TravelerTime TravelerTime TravelerTime TravelerTime Traveler

Group: Ipswitch Employees
Last Login: 2 days ago @ 4:00:28 PM
Posts: 152, Visits: 666
From the error message it looks like it is looking for SQL Server on a computer named "MONITORWORLD". Can you please send me the contents of the following registry key?

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\WhatsUp         (I am assuming that the DSN you are using is called WhatsUp)

Post #44644
Posted 6/16/2008 10:51:59 AM
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Group: Forum Members
Last Login: 6/30/2008 12:56:56 PM
Posts: 43, Visits: 129
AmbarK (6/16/2008)
From the error message it looks like it is looking for SQL Server on a computer named "MONITORWORLD". Can you please send me the contents of the following registry key?

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\WhatsUp         (I am assuming that the DSN you are using is called WhatsUp)

ohhh well im not the original poster, their server/instance was called monitorworld, but the error is otherwise the same on my system

regardless, here are the contents of that reg key:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\Whatsup]
"Driver"="C:\\WINDOWS\\system32\\SQLSRV32.dll"
"Description"="Whatsup Database"
"Server"="Ndwhatsup\\Whatsup"
"Database"="WhatsUp"
"LastUser"="ndbackup"
"Trusted_Connection"="Yes"

Post #44648
Posted 6/16/2008 11:13:16 AM
Time Traveler

Time TravelerTime TravelerTime TravelerTime TravelerTime TravelerTime TravelerTime TravelerTime Traveler

Group: Ipswitch Employees
Last Login: 2 days ago @ 4:00:28 PM
Posts: 152, Visits: 666
Run

osql -E -D WhatsUp -Q "sp_helpserver" -o C:\servers.txt

in a command prompt window on your WhatsUp system, and attach the servers.txt created on your C:\

Post #44651
Posted 6/16/2008 8:42:35 PM
Junior Member

Junior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior Member

Group: Forum Members
Last Login: 10/2/2008 10:05:51 AM
Posts: 16, Visits: 71
I ended up going back to sql 2k. I couldn't wait any longer.  Boo support
Post #44664
Posted 6/17/2008 7:58:02 AM
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Group: Forum Members
Last Login: 6/30/2008 12:56:56 PM
Posts: 43, Visits: 129
kind of funky formatting, but here ya go

 name                                                                         
                                                   
 network_name                  
 status                                                                
                               id  
 collation_name                                                        
                                                          
 connect_timeout query_timeout
 ------------------------------------------------------------------------------
 --------------------------------------------------
 ------------------------------
 -----------------------------------------------------------------------
 ----------------------------- ----
 -----------------------------------------------------------------------
 ---------------------------------------------------------
 --------------- -------------
 NDVMWARE\WHATSUP                                                             
                                                   
 NDVMWARE\WHATSUP              
 rpc,rpc out,use remote collation                                      
                               0   
 NULL                                                                  
                                                          
               0             0
 WhatsUp                                                                      
                                                   
 WhatsUp                       
 rpc,rpc out,data access,use remote collation                          
                               1   
 NULL                                                                  
                                                          
               0             0

 

@
 i don't have a recent enough backup of the database to do that i was in a rush and broke the rule of backing up before upgrading (sorta figuring it would work perfectly, it always bites me in the *** when i figure that...ya think i'd learn by now but i must be dense heh)

Post #44675