Ipswitch Forums / Ipswitch Products / WhatsUp Gold / ODBC error adding monitors after upgrade to 12 / Latest Posts

RE: ODBC error adding monitors after upgrade to 12

serverjunge23 — Mon, 30 Jun 2008 12:11:47 GMT

Hello,
I installed "SQL Server 2005 Express Edition with Advanced Services SP2 " and reinstalled WhatsUp and reimported wug12-database and now it works.

thanks for your help.

thomas

RE: ODBC error adding monitors after upgrade to 12

JS_Naples — Fri, 27 Jun 2008 17:20:57 GMT

thanks for the killer webex sessions ambar!

for all those involved still with the exact error i had it's not that hard of an overall fix. basically it is a reinstall of sql server 2005 ONLY, i feared having to reinstall wug so i had refused originally in this thread, and thankfully i didnt have to. all my settings and scripts and everything were restorable from teh database as well as what was installed with wug itself.

if anyone is having this problem, i can start by telling you to download:

http://www.microsoft.com/express/sql/download/default.aspx If it prompts you to register, just skip it. You are looking for "SQL Server 2005 Express Edition with Advanced Services SP2 " its [b]234 MB[/b] (on the right hand side)

I'd be glad to help you all out, as im sure ambar would now that he knows the quickest path to the solution as we had

EDIT: make sure you backup your WUG database from within WUG before you uninstall the SQL Server that came with WUG and install the version dowloaded here

RE: ODBC error adding monitors after upgrade to 12

JS_Naples — Wed, 25 Jun 2008 12:20:07 GMT

slight update: (this makes sense but i just now tried it)

if i add a new device it ends up NOT being pingable. the default Active Monitor of "ping" is NOT added to the device (probably for the same reason i can not add new active monitors to existing devices)

so now not only can i edit current devices, i've found i can't even add new ones properly if i want to.

please continue helping if you can

RE: ODBC error adding monitors after upgrade to 12

JS_Naples — Thu, 19 Jun 2008 16:32:58 GMT

mine has:

name

network_name
status
id
collation_name

connect_timeout query_timeout
------------------------------------------------------------------------------
--------------------------------------------------
------------------------------
-----------------------------------------------------------------------
----------------------------- ----
-----------------------------------------------------------------------
---------------------------------------------------------
--------------- -------------
NDWHATSUP\WHATSUP

NDWHATSUP\WHATSUP
rpc,rpc out,use remote collation
2
NULL

0 0
WhatsUp

WhatsUp
rpc,rpc out,data access,use remote collation
1
NULL

0 0

RE: ODBC error adding monitors after upgrade to 12

serverjunge23 — Thu, 19 Jun 2008 09:07:39 GMT

name

network_name
status
id
collation_name

connect_timeout query_timeout
------------------------------------------------------------------------------
--------------------------------------------------
------------------------------
-----------------------------------------------------------------------
----------------------------- ----
-----------------------------------------------------------------------
---------------------------------------------------------
--------------- -------------
RAS4\WHATSUP

RAS4\WHATSUP
rpc,rpc out,use remote collation
1
NULL

0 0

RE: ODBC error adding monitors after upgrade to 12

AmbarK — Thu, 19 Jun 2008 08:56:08 GMT

So if you run following command in a command prompt window, what does servers.txt have?

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

RE: ODBC error adding monitors after upgrade to 12

serverjunge23 — Thu, 19 Jun 2008 04:08:18 GMT

I also restarted the service serval times...

RE: ODBC error adding monitors after upgrade to 12

JS_Naples — Wed, 18 Jun 2008 16:39:50 GMT

sure did, i even just now stopped it entirely (and its dependent) and closed the whatsup program itself and then restarted everything...whereas the first time i just chose the restart service option and waited for it to stop the dependent

still the same error about data access

RE: ODBC error adding monitors after upgrade to 12

AmbarK — Wed, 18 Jun 2008 14:52:55 GMT

Did you restart the "SQL Server (WHATSUP)" service after running the rename_sql_server.sql?

RE: ODBC error adding monitors after upgrade to 12

JS_Naples — Wed, 18 Jun 2008 14:05:26 GMT

in catching up on this thread and following your directions, i'm at the same error the above user is at. however, it properly names my computer and dsn name in the message

Error=80004005
ErrorMessage=Unspecified error
Description=.... Server 'NDWHATSUP\WHATSUP' is not configured for DATA ACCESS.

edit: should your rename .sql file have been edited for case sensitivity towards the machine/dsn? other than that its perfect

RE: ODBC error adding monitors after upgrade to 12

AmbarK — Wed, 18 Jun 2008 11:25:17 GMT

Ok, then change your rename_sql_server.sql to:

sp_addserver 'RAS4\WHATSUP'

save the changes and then run:

osql -E -D WhatsUp -i rename_sql_server.sql -o rename_output.txt

RE: ODBC error adding monitors after upgrade to 12

serverjunge23 — Wed, 18 Jun 2008 11:19:29 GMT

RAS4 It's on the same server where WhatsUp is installed.

RE: ODBC error adding monitors after upgrade to 12

AmbarK — Wed, 18 Jun 2008 11:08:20 GMT

What is the name of the system where SQL server is installed?

RE: ODBC error adding monitors after upgrade to 12

serverjunge23 — Wed, 18 Jun 2008 11:04:49 GMT

Hello,
I did this changes. But now the the file servername.txt seems:

------------------------------------------------------------------------------
--------------------------------------------------
NULL

(1 row affected)

and I have a different error in WhatsUp.
Error=80004005
ErrorMessage=Unspecified error
Description=.... Server 'NewServer\WhatsUp' is not configured for DATA ACCESS.

DNS and and registry is ok.

RE: ODBC error adding monitors after upgrade to 12

AmbarK — Wed, 18 Jun 2008 10:34:04 GMT

Sorry, I forgot to enclose the names is single qoutes.

Edit the rename_sql_server.sql to looks like:

sp_dropserver 'OLDNAME\WHATSUP'
go

sp_addserver 'NEWNAME\WHATSUP'
go

Also make sure that the DSN used by Whatsup (most likely called WhatsUp) points to NEWNAME\WHATSUP. To check this, look at 'Server' value under HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\WhatsUp (assuming that your DSN is called WhatsUp).

RE: ODBC error adding monitors after upgrade to 12

serverjunge23 — Wed, 18 Jun 2008 10:22:06 GMT

Hello,
I have the same problem with different servernames.
So I used your attached file and edit it for my system.
But I get an error in rename_output.txt

1> 2> Msg 102, Level 15, State 1, Server NewServer\WHATSUP, Line 1
Incorrect syntax near '\'.
1> 2> 3> Msg 102, Level 15, State 1, Server NewServer\WHATSUP, Line 2
Incorrect syntax near '\'.
1> 2>

Could you explain this?

Thanks.

RE: ODBC error adding monitors after upgrade to 12

AmbarK — Tue, 17 Jun 2008 15:25:38 GMT

Ah! - that makes a lot more sense now.

Extract the attached file to C:\ and then run following command in a command prompt window:

osql -E -D WhatsUp -i C:\rename_sql_server.sql -o C:\rename_output.txt

and then restart the "SQL Server (WHATSUP)" service

RE: ODBC error adding monitors after upgrade to 12

JS_Naples — Tue, 17 Jun 2008 14:48:39 GMT

please see my edited post back one page, which basically says the name of the computer is NDWhatsup and not ndvmware if the results of the command should ref the computer name.

when attempting to change an active monitor script that already exists, or when attempting to add a new monitor to an existing device i receive:

error window titlebar: Failed to update monitor type

error window description:

"Error = 80004005

ErrorMessage=Unspecified error

Description=[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server 'NDWHATSUP\WHATSUP' in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers."

i have executed the stored procedure, although not setting an output, which ran in a command window and did not display any errors. although it took me a few tries to get the command just right

RE: ODBC error adding monitors after upgrade to 12

AmbarK — Tue, 17 Jun 2008 14:39:04 GMT

Ok, that looks correct too. I am stumped as to why you would be getting the error message that you are. Can you please post your exact error message again?

RE: ODBC error adding monitors after upgrade to 12

JS_Naples — Tue, 17 Jun 2008 14:32:05 GMT

------------------------------------------------------------------------------
--------------------------------------------------
NDVMWARE\WHATSUP

(1 row affected)

edit: perhaps i slipped in not posting this in my prior post, but the name of the computer this is hosted on is NDWhatsup, and not NDVMWare. i don't know where these commands are getting NDVMWare from, but if it's supposed to ref the computer name, it's wrong

RE: ODBC error adding monitors after upgrade to 12

AmbarK — Tue, 17 Jun 2008 11:28:13 GMT

That looks correct.

Run

osql -E -D WhatsUp -Q "select @@servername" -o C:\servername.txt

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

RE: ODBC error adding monitors after upgrade to 12

JS_Naples — Tue, 17 Jun 2008 07:58:02 GMT

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

bgovoni

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)

RE: ODBC error adding monitors after upgrade to 12

bgovoni — Mon, 16 Jun 2008 20:42:35 GMT

I ended up going back to sql 2k. I couldn't wait any longer. Boo support

RE: ODBC error adding monitors after upgrade to 12

AmbarK — Mon, 16 Jun 2008 11:13:16 GMT

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:\

RE: ODBC error adding monitors after upgrade to 12

JS_Naples — Mon, 16 Jun 2008 10:51:59 GMT

[quote][b]AmbarK (6/16/2008)[/b][hr]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)[/quote]

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"

RE: ODBC error adding monitors after upgrade to 12

AmbarK — Mon, 16 Jun 2008 09:15:49 GMT

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)

RE: ODBC error adding monitors after upgrade to 12

JS_Naples — Mon, 16 Jun 2008 07:46:56 GMT

[quote][b]AmbarK (6/12/2008)[/b][hr]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"?[/quote]

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

RE: ODBC error adding monitors after upgrade to 12

AmbarK — Thu, 12 Jun 2008 09:15:05 GMT

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"?

RE: ODBC error adding monitors after upgrade to 12

JS_Naples — Thu, 12 Jun 2008 08:31:51 GMT

bump

anyone?

RE: ODBC error adding monitors after upgrade to 12

JS_Naples — Wed, 04 Jun 2008 11:01:46 GMT

@rkesser

upon your fresh reinstall, what sql driver is the whatsup odbc using?

I've tried changing that around and i've tried running the stored procedure sp_addlinkedserver like the error message recommends, but nothing has yet fixed this problem

not only can you not add active monitors, you can't modify active monitor scripts either...needin some help here :)

EDIT: i even ran the database upgrade script which only needed to run 1 script, which it did, with no errors

RE: ODBC error adding monitors after upgrade to 12

JS_Naples — Mon, 02 Jun 2008 11:30:40 GMT

it says that the whatsup license for v11 was "replaced by" and gives the corresponding serial # to the one above it in this list. the one that refers to wugv12.

if i click "manage this license" on the wugv11 license, there is no option to deactivate it.

RE: ODBC error adding monitors after upgrade to 12

Ferry Kohlmann (Heureka) — Wed, 28 May 2008 04:43:34 GMT

This error occurs if whatsup is activated with the same license on more than one computer. Please go to www.myipswitch.com, select "my licenses", click on "manage this license" and click on "deactivate".

For more informations concerning WhatsUp please visit www.heureka.com

RE: ODBC error adding monitors after upgrade to 12

rkesser — Tue, 27 May 2008 13:42:00 GMT

I solved this problem by completely deinstall WUG 12 and cleanup the directories of WUG 12 and MS SQL. Then I made a clean installation of WUG 12 and imported the backup of the WUG 11.0.3 database. Finally I executed the database update-script.
I checked the result by adding an active monitor to a switch and saved it. The same problem I had with the WUG 12 Technical Preview.
I think it looks like a problem with the update program.

RE: ODBC error adding monitors after upgrade to 12

bgovoni — Mon, 26 May 2008 15:31:03 GMT

I went from sql 2k enterprise to sql 05 full I believe. Can we get some support on this, we got a few others now. I would love to start working on the upgrade but obvious I can't until we get this taken care of.

RE: ODBC error adding monitors after upgrade to 12

rkesser — Mon, 26 May 2008 13:35:00 GMT

I have the same problem after upgrading from WUG 11.0.3 to WUG 12. The Database was upgraded from MSDE to MS SQL 2005 express.
The Setup exits without any errors.

RE: ODBC error adding monitors after upgrade to 12

AmbarK — Fri, 23 May 2008 08:03:38 GMT

Were you using MSDE before the upgrade or a "full" SQL Server 2000?

RE: ODBC error adding monitors after upgrade to 12

JS_Naples — Thu, 22 May 2008 14:33:22 GMT

I'll add my name to this list, just found this problem today

RE: ODBC error adding monitors after upgrade to 12

bgovoni — Fri, 16 May 2008 09:44:55 GMT

Im having this same problem too and need this to complete my upgrade. To note, I upgraded from sql 2000 to 2005 in the process.

ODBC error adding monitors after upgrade to 12

Nic65535 — Fri, 09 May 2008 06:45:17 GMT

Having upgraded from v11.0.3 to v12 I am unable to add monitors to new or existing devices. Attempting to save the monitor from the WUG application gives:

Error=80004005 ErrorMessage=Unspecified Error Description=[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server 'MONITORWORLD\WHATSUP' in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers.

This only seems to be effecting monitors (active, passive and performance). I can 'tweak' anything else.

I have e-mailed support but no response so far so looking for answers.

TIA

Nic