Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1663
  • Last Modified:

Unable to open svrnetcn utility for MSDE - Rather Urgent

My company is beginning a trial of some Blackberrys and I have been trying to configure the BES to relay messages to no avail.  Working with RIM support, one of the steps tried was to make sure the appropreate protocols are enabled by opening the svrnetcn utility.  When I try I recieve a "126, Specified moduld could not be found." message.  Why? What do I do?

It is running MSDE, on a 2003 server, with Exchange 2003 SP1 System Manager installed.  I also have SharePoint services installed on this server which is also using MSDE, which I could remove if necessary, but RIM said that shouldn't be an issue.
0
benhar
Asked:
benhar
  • 7
  • 7
1 Solution
 
ptjcbCommented:
Are you blocking port 1433? Try to telnet from the outside -

Telnet yoursevername 1433

What does that return?


0
 
benharAuthor Commented:
I get a cannot connect to host message.  I don't have any setup here that get's me an outside IP, so this was done from home.  I figured it wouldn't work anyway.
0
 
ptjcbCommented:
This link will give you some basic troubleshooting techniques:

http://www.mcse.ms/archive83-2005-6-1696963.html
0
Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

 
benharAuthor Commented:
How would I reinstall the client tools if this is only MSDE 2000 installation?
0
 
ptjcbCommented:
Check the C:\Program Files\Microsoft SQL Server\80\Tools\Bin

You should have the svrnetcn.exe there even with a MSDE installation.


0
 
ptjcbCommented:
Looking through the net several people used depends.exe (found at http://www.dependencywalker.com/) to find their problem.
0
 
benharAuthor Commented:
It says I'm missing MSJAVA.dll.  I did a search on the local drives for it and nothing was found.  Can I copy it from another machine using MDSE?
0
 
benharAuthor Commented:
I ran depends.exe against the svrnetcn.exe on a different machine, it came up with missing help.dll, but no where in that dependency is msjava.dll.  svrnetcn works on that machine too.  (Working machine is server 2000, whereas where it's not working is 2003, if that matters.)
0
 
benharAuthor Commented:
00:00:01.172: LoadLibraryW("C:\Program Files\Microsoft SQL Server\80\Tool\BINN\svrnetcn.dll") returned NULL by thread 1. Error: The specified module could not be found (126).

I did a profile, this is the one error.
0
 
ptjcbCommented:
It may be that there is a firewall blocking port 1433 in Win2003 (you also could not connect to 1433 earlier). Can you telnet to 1433 on the Wind2000 server?
0
 
benharAuthor Commented:
As I said, I don't have an outside ip setup here, but if I still try to telnet both servers on 1433 here, the w2k server fails with "could not open communication to host".  the w2003 seems that it works, but just get a blank cmd window (no prompts or errors).
0
 
ptjcbCommented:
Ok - this is becoming confusing:

Do you have a C:\Program Files\Microsoft SQL Server\80\Tools\Bin? Or is it C:\Program Files\Microsoft SQL Server\80\Tool\BINN\svrnetcn.dll? Notice there is a TOOLS\Bin in one and the dependency walker is looking in TOOL\Bin.

What is on the Win2000 box (where it works)?

Maybe all you need to do is create a TOOL\Bin and copy svrnetcn.dll there?
0
 
benharAuthor Commented:
BAM!

My path was C:\Program Files\Microsoft SQL Server\80\Tools\Binn.  I created a ...\tool\binn folder and copied everything over, and it now works!

Thanks so much for the help! (Not guaranteed that this will solve my BES comm problem, but it's a step.)
0
 
ptjcbCommented:
Cool. Sometimes it is just looking at everything...
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 7
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now