"The specified module could not be found", Server Network Utility

Has any body had a problem whereby when you try and load the Server Network
Utility you get the error "The specified module could not be found". I have
SQL Server 2000 developer installed on my machine and 3 instances of MSDE and
2 of wMSDE. I have reinstalled sql server sp4, this has had no effect. Any
ideas anybody?
This issue is typically caused by a damaged installation of client tools. I
suggest that you reinstall the client tools through the following steps:
1. Insert the SQL Server 2000 compact disc into your CD-ROM drive. If the
compact disc does not autorun, double-click Autorun.exe in the root
directory of the compact disc.
2. Select SQL Server 2000 Components, select Install Database Server, and
then click Next at the Welcome screen of the SQL Server Installation Wizard.
3. In Computer Name dialog box, Local Computer is the default option, and
the local computer name appears in the edit box. Click Next.
4. In the Installation Selection dialog box, click Create a new instance of
SQL Server, or install Client Tools, and then click Next.
5. Follow the directions on the User Information, Software License
Agreement, and related screens.
6. In the Installation Definition dialog box, click Client tools only, and
then click Next.
7. In the Select Components dialog box, accept the defaults or select the
components you want, and then click Next.
8. In the Start Copying Files dialog box, click Next to complete the
installation of the client tools.
9. Check whether the Server Network Utility works correctly. If it works,
reapply SP4.
If the issue persists, I'd like to use the Dependency Walker tool to track
the module that cannot be loaded. To do so, follow these steps:
1) Download Dependency Walker utility from www.dependencywalker.com.
2) Create a new folder on your system and extract the files from this
executable into the folder.
3) Start Dependency Walker utility by double-clicking depends.exe.
4) From the File menu, click Open and choose the file C:\Program
Files\Microsoft Sql Server\80\Tools\Binn\svrnetcn.exe.
5) Click menu option Profile -> Start Profiling.
6) Select all checkboxes on the "Profile Module" dialog box.
7) Click OK to start profiling.
8) After the profiling finished, go to File-Save As-> save as svrnetcn.dwi.
9) Zip the .dwi file and e-mail it to me at v-rxwang@.microsoft.com.
Third-Party Link Disclaimer
===========
This response contains a reference to a third-party World Wide Web site.
Microsoft is providing this information as a convenience to you. Microsoft
does not control these sites and has not tested any software or information
found on these sites; therefore, Microsoft cannot make any representations
regarding the quality, safety, or suitability of any software or
information found there. There are inherent dangers in the use of any
software found on the Internet, and Microsoft cautions you to make sure
that you completely understand the risk before retrieving any software from
the Internet.
If anything is unclear, feel free to let me know.
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: "The specified module could not be found", Server Network
Utility
>thread-index: AcV5tMB8B0i7JmcNRia3obumQYfDXQ==
>X-WBNR-Posting-Host: 213.152.39.142
>From: "=?Utf-8?B?bmlja25hbWU=?=" <nickname@.online.nospam>
>Subject: "The specified module could not be found", Server Network Utility
>Date: Sat, 25 Jun 2005 11:36:08 -0700
>Lines: 5
>Message-ID: <02512271-F9D5-4CE4-8FE7-F9F92D841595@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.tools
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.tools:4640
>X-Tomcat-NG: microsoft.public.sqlserver.tools
>Has any body had a problem whereby when you try and load the Server
Network
>Utility you get the error "The specified module could not be found". I
have
>SQL Server 2000 developer installed on my machine and 3 instances of MSDE
and
>2 of wMSDE. I have reinstalled sql server sp4, this has had no effect. Any
>ideas anybody?
>

"key not valid for use in the specified state"

I upgraded to Windows 2003 SP1, and now I keep getting the message: "Key not
valid for use in the specified state" on any page of the Report Manager that
I try to access.
I've tried deleting and recreating the keys with no success. The search that
I've done in the MS Site have all pointed me to EFS errors. Anybody have any
ideas where I should go next?
Thanks.
DerrickI had that problem 6 months ago. After opening a support call with MS
and after many attempts to fix it, in the end the only process that
worked was to completely erase all traces of RS from the system and then
do a fresh install. Below is a list of the steps to take (note
especially step 5 - this was the deciding factor for me on the reinstall
fixing the problem)
1. Backup your existing solution files, such as .sln, .rdl, .rds files.
2. If the machine is a domain controller, do not install Reporting
Service on it. Use another machine instead.
3. Run Setup.exe of the SQL Server 2000 Reporting Services to launch the
Setup window.
4. Click "Remove Microsoft SQL Server 2000 Reporting Service" button in
the Setup window.
5. From Explorer, navigate to x:\Documents and Settings\<service
account>\Application Data\Microsoft\Crypto\RSA\S-1-5-20 and delete all
files located in this folder.
6. Delete all Reporting services related files under this folder
"x:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services" if present
7. Delete all Reporting Services Virtual Directories (ReportServer and
Reports) from IIS Manager if present.
8. Delete all Reporting Services Databases (ReportServer and
ReportServerTempDB) from SQL Server Enterprise Manager if present.
9. Re-boot the machine and log on using an Administrators group account.
10. Reinstall SQL Server 2000 Reporting Service on the machine.
brian smith
Derrick Powell wrote:
> I upgraded to Windows 2003 SP1, and now I keep getting the message: "Key not
> valid for use in the specified state" on any page of the Report Manager that
> I try to access.
> I've tried deleting and recreating the keys with no success. The search that
> I've done in the MS Site have all pointed me to EFS errors. Anybody have any
> ideas where I should go next?
> Thanks.
> Derrick
>