|
Home > Archive > Windows 2000 Networking > May 2004 > Netmeeting causes Dr. Watson error
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Netmeeting causes Dr. Watson error
|
|
| Ripper 2004-05-24, 4:29 pm |
| Getting the following error when attempting to start
Remote Desktop Sharing in Netmeeting.
MNMSRVC.exe has generated errors and will be closed by
Windows. You will need to restart the program.
When checking the Dr. Watson log the following info
appears.
Application Exception occured:
App: mnmsrvc.exe (pid=2472)
Exception number: c0000005 (access violation)
Any assistance is greatly appreciated.
| |
| Larry Stotler 2004-05-25, 11:30 pm |
| Hello,
This issue can occur if the Schannel.dll file is missing, damaged, or the
wrong version.
To try to resolve this issue, determine the version of the Schannel.dll
file you need, and then extract the correct version of this file from the
Internet Explorer.cab files. For additional information about how to
determine the version of the Schannel.dll file you need, click the article
number below to view the articles in the Microsoft Knowledge Base:
287164 Internet Explorer 5.5 Service Pack 1 File List for Windows (Article
1 of
http://support.microsoft.com/?id=287164
310504 Internet Explorer 6.0 File List 1 of 2
http://support.microsoft.com/?id=310504
For additional information about how to extract files, click the article
number below to view the article in the Microsoft Knowledge Base:
Q129605 How to Extract Original Compressed Windows Files
Larry Stotler, MCSE
Microsoft Product Support
NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose
| |
| Andrew Hayes 2004-05-27, 4:31 pm |
| Hi Larry,
Thought I'd tag onto Rippers thread as I'm seeing the same/similiar issue.
I can start a secure NetMeeting call between my machine and the server with no problems, but if I activate RDS on the server and try to connect, the Remote Desktop Sharing Service crashes with these events in the event log.
Event Type: Information
Event Source: mnmsrvc
Event Category: None
Event ID: 16
Date: 2004/05/27
Time: 17:54:44
User: N/A
Computer: SOLO
Description:
NetMeeting RDS Service Start
-----------------------------------
Event Type: Error
Event Source: Schannel
Event Category: None
Event ID: 36869
Date: 2004/05/27
Time: 17:54:45
User: N/A
Computer: SOLO
Description:
The SSL server credential's certificate does not have a private key information property attached to it. This most often occurs when a certificate is backed up incorrectly and then later restored. This message can also indicate a certificate enrollment fa
ilure.
-----------------------------------
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Date: 2004/05/27
Time: 17:55:05
User: N/A
Computer: SOLO
Description:
The NetMeeting Remote Desktop Sharing service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: No action.
-------------------------------------
Event Type: Information
Event Source: DrWatson
Event Category: None
Event ID: 4097
Date: 2004/05/27
Time: 17:54:52
User: N/A
Computer: SOLO
Description:
The application, mnmsrvc.exe, generated an application error The error occurred on 05/27/2004 @ 17:54:52.533 The exception generated was c0000005 at address 6AC96112 (T120_CreateControlSAP)
Data: *deleted*
----------------------------------
The Schannel DLL is version 5.00.2195.6899, but I don't know what certificate it would be using for SSL. Would it be the same as for SLL on IIS?
Any further assistance would be appreciated.
| |
| Larry Stotler 2004-05-29, 11:31 pm |
| Hello,
The problem is with the Certificate on the Server not your client. It is
either a bad cert or the bad cert registry settings. First make sure you
are logged in as Administrator when trying to generate the cert request.
The following step have resolved similar issues in the past. PLEASE
remember to backup the key as the instructions say before proceeding.
1. Click Start, click Run, and then type "regedit" (without the
quotation marks) to open the standard Registry Editor.
2. Locate and click the following registry key:
HKEY_USERS\Default\Software\Microsoft\Cr
yptography\Providers\Type 001
3. Click the Providers key, click "Export Registry File" on the
Registry menu, and then type the location where you want to save this
file. Save this file to a location where you can easily access it at a
later time if necessary.
4. Press DELETE, and then click Yes to confirm that you want to delete
this registry key.
5. Restart the server. You are able to perform any of the tasks which were
formerly not possible because of the Cryptography APIs issue.
Larry Stotler, MCSE
Microsoft Product Support
NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose
|
|
|
|
|