Hi,

This issue is fixed in NMSQL 5.2 sp1 build 320 and higher. (latest 334)

After the upgrade, the error will go away.

Hope this helps.

Regards

Bruno

I use NMSQL 5.2 sp1 build 299，this is the only version I can find to download.

Hi

Try this build:

ftp://ftp.emc.com/outgoing/nmsql521_win_x86.zip

Regards,

Bruno

Thank you.

Now I can open the Networker Module for sql.

I think this problem is about the Compatibility level of "master" database.

I have the exact same problem, but I cannot seem to download the fix from the ftp site.

Hi,

Try again:

ftp://ftp.emc.com/outgoing/nmsql521_win_x86.zip

Regards,

Bruno

Thanks for the quick reply, but...this file is build 299 and I thought this was the one with the bug???

Larry

Hi Larry,

Just downloaded and checked the build again, it is the latest. 347.

Make sure that you are not overwriting a previous version when you download.

Try to download the package to an empty folder, and unzipp it inside that folder.

Lets me know if it still comes up with build 299

Regards,

Bruno

I downloaded the file again, this time to the sql server, rather than to networker. After extracting the files, when the installation is started, it said it was build 299. Launching the sql client (Help/About) said it was build 299. Still fails. I changed the master compatibility level to 2005 and the backup went fine (Thanks nicktang). One more piece of info. Out of our 3 sql servers, this was the only one which was upgraded from a SQL 2000 server to a SQL 2005 server. The other 2 were just SQL 2005 servers. Thanks for everyones help.

Larry

You must uninstall and reinstall the NWSQL,it works fine for me.

Nick Tang

Shaz

I'm finding problem to download the SQL SP2 5.1 Build 300 (or above), can you help me?

I never did get a client over .300

I am using .299

I took nicktang's advice and changed the compatability of the master db

to anything but sql 2000.

See his message dated 26 Feb above.

mig kindly advice...

i installed the .299 version which is available ... but couldn't find the .300 (or above) to fix this..

The objects "master.sys.databases" and "master..sysdatabases" in the FROM clause have the same exposed names. Use correlation names to distinguish them...