eohrnb01
asked on
New Users question
Operating System -- NT
Version -- 4.0 sp3
Computer Make -- DELL
Computer Model -- Optiplex 5166
Memory (Mb of RAM) -- 64 MB
CPU Type -- 586/Pentium
CPU Speed (MHz) -- 166 MHz
This problem can be duplicated.
I am working with multiple PC's and this problem occurs on several of them.
Somehow the telephony drivers got trashed on two of my Winnt 4.0 SP3 systems. I know this because I double click on the telephony control panel applet and try and configure the 'Unimodem Service Provider' and get nothing.No error message, no dialog, nada. Since I have a program startre sound configured, and by watching in the NT Task Manager Processes tab, I know that rundll32.exe is trying to do something, but I can't figure out what.
The last thing that I did that appears to be related is downloading and installing several of the Outlook tools found on the http://www.microsoft.com/officefreestuff/outlook/default.htm page.
The same happens when I try and double click on the 'Modems' control panel applet. This iscausing RAS to not function, as it cannot find a device on which to communicate Event Log:
"Remote Access Connection Manager failed to start because it could not load one or more communication DLLs. Ensure that your communication hardware is installed and then restart the computer. If the problem persists, reinstall the Remote Access Service. "
I have tried to remove and re-install RAS, but when I do, it can't find the modem, and I can't add a modem.
Install Lineage:
NT 4.0 (formatted all drives)
Exchange Client (with Schedule Plus 7a)
Workstations Fax beta 2
Office 95 Pro
Office 97 Pro
NT 4 SP 3
Outlook: E-Mail Forms Fix Utility -- Beta
Outlook: SwitchForms Utility
Outlook: Internet Mail Enhancement Patch--Beta 2
Outlook: Microsoft Draw 97
Outlook: Outlook Driver for Microsoft Schedule+ 7.x
Outlook: Copy vCards into Outlook
Outlook: Rules Wizard Final Release!
Outlook: 3-Pane Extension add-in
Outlook: Microsoft Schedule+ Print Files
Registry corruption?
Two systems with the same identical problem after the same software was installed? Hmm. I suppose it couldn't be attributable to some environmental sort of impact. It appears that the common thread was the software installation as specified.
I used regedit to dump the entire registry to a .reg file and started looking at it. I am comaring it against a .reg dump of a machine who has not had the same software history, and does have the Unimodem driver properties available under the 'Telephony' control panel applet. I figure with enough poking around, I can check to see if the TAPI hive and settings are still there.
On one system the modem is an internal USR Courier V. Everything, and in the other case it's external. Both systems roughtly went through the same progression. Is it PNP? Yes I think it is, it is on the HCL for both Windows 95 and WindowsNT.
Both systems are installed as FAT only dual boot system (Win95/WintNT) It seems that the problem arised a few boots after the installation of the Outlook free tools, if not immediately after.
Yes Outlook works fine (it used to crash under NT and now it doesn't, it's just that RAS/TAPI is now gone), the Outlook crash I figure is a resolved problem.
The second machine, I have not touched for fear of invoking further evil demons form within (it's my primary work machine).
What command line does the rundll32 execute when you double click on the modem contaol panel applet? Can I run this from the command line seperatly? What about the rundll32 command line when you try and configure the Unimodem TAPI driver? Perhaps this is another staring point for research?
Using find file utility to find out what Unimodem support is in the sysdtem finds:
unimodv.* = No Files found
unimodem.* = No Files found
I did find the following:
Unimdm.tsp in c:\winnt\system32 Version 4.00 from Microsoft Corp. 1992-1995, file entry date stamp is Created August 9, 1996, modified 5/1/1997, and accessed June 5, 1997 and is Described as the Unimodem Service Provider.
Double click in the RasPhone.exe (Dialup Networking) gets you this error message:
Initialization of the dynamic link library: c:\winnt\system32\rasman.d
The process is terminating abnormally.
And then, Initialization of the dynamic link library c:\winnt\system32\rasscrpt
The process is terminating abnormally.
Double clicking on the devices control panel applet displays a dialog with:
Configuration Manager: This routine is not implemented in this version of the operating system.
In the event log, during the boot process, the following messages are entered:
Event ID: 8222 Source: NT Fax
Type: Error Category: Initialization/Termination
No fax devices were found.
Event ID: 8213 Source: NT Fax
Type: Error Category: Initialization/Termination
The fax service is stopped.
Event ID: 1008 Source: Perflib
Type: Error Category: None
The Open Procedure for service "Fax" in DLL "C:\WINNT\system32\faxperf
Status code returned is DWORD 0.
Event ID: 7024 Source: Service Control Manager
Type: Error Category: None
The Remote Access Connection Manager service terminated with service-specific error 615.
Event ID: 7001 Source: Service Control Manager
Type: Error Category: None
The Remote Access Autodial Manager service depends on the Remote Access Connection Manager service which failed to start because of the following error:
The service has returned a service-specific error code.
Event ID: 7001 Source: Service Control Manager
Type: Error Category: None
The Remote Access Server service depends on the Remote Access Connection Manager service which failed to start because of thefollowing error:
The service has returned a service-specific error code.
In the services control panel applet, we see that the "Telephony Service"
is up and running.
There appear to be no RAS related services running at all.
Another solution that I was considering was just installing NT Server over the top of what was currently there. I was thinking that NTS would be different enought that it would re-configure the TAPI drivers back to what they should be.
Where to next? How to recover? Any hints would be greatly appreciated.
Erik.
Erik Ch. Ohrnberger
email: Erik_Ch_Ohrnberger@bigfoot
Version -- 4.0 sp3
Computer Make -- DELL
Computer Model -- Optiplex 5166
Memory (Mb of RAM) -- 64 MB
CPU Type -- 586/Pentium
CPU Speed (MHz) -- 166 MHz
This problem can be duplicated.
I am working with multiple PC's and this problem occurs on several of them.
Somehow the telephony drivers got trashed on two of my Winnt 4.0 SP3 systems. I know this because I double click on the telephony control panel applet and try and configure the 'Unimodem Service Provider' and get nothing.No error message, no dialog, nada. Since I have a program startre sound configured, and by watching in the NT Task Manager Processes tab, I know that rundll32.exe is trying to do something, but I can't figure out what.
The last thing that I did that appears to be related is downloading and installing several of the Outlook tools found on the http://www.microsoft.com/officefreestuff/outlook/default.htm page.
The same happens when I try and double click on the 'Modems' control panel applet. This iscausing RAS to not function, as it cannot find a device on which to communicate Event Log:
"Remote Access Connection Manager failed to start because it could not load one or more communication DLLs. Ensure that your communication hardware is installed and then restart the computer. If the problem persists, reinstall the Remote Access Service. "
I have tried to remove and re-install RAS, but when I do, it can't find the modem, and I can't add a modem.
Install Lineage:
NT 4.0 (formatted all drives)
Exchange Client (with Schedule Plus 7a)
Workstations Fax beta 2
Office 95 Pro
Office 97 Pro
NT 4 SP 3
Outlook: E-Mail Forms Fix Utility -- Beta
Outlook: SwitchForms Utility
Outlook: Internet Mail Enhancement Patch--Beta 2
Outlook: Microsoft Draw 97
Outlook: Outlook Driver for Microsoft Schedule+ 7.x
Outlook: Copy vCards into Outlook
Outlook: Rules Wizard Final Release!
Outlook: 3-Pane Extension add-in
Outlook: Microsoft Schedule+ Print Files
Registry corruption?
Two systems with the same identical problem after the same software was installed? Hmm. I suppose it couldn't be attributable to some environmental sort of impact. It appears that the common thread was the software installation as specified.
I used regedit to dump the entire registry to a .reg file and started looking at it. I am comaring it against a .reg dump of a machine who has not had the same software history, and does have the Unimodem driver properties available under the 'Telephony' control panel applet. I figure with enough poking around, I can check to see if the TAPI hive and settings are still there.
On one system the modem is an internal USR Courier V. Everything, and in the other case it's external. Both systems roughtly went through the same progression. Is it PNP? Yes I think it is, it is on the HCL for both Windows 95 and WindowsNT.
Both systems are installed as FAT only dual boot system (Win95/WintNT) It seems that the problem arised a few boots after the installation of the Outlook free tools, if not immediately after.
Yes Outlook works fine (it used to crash under NT and now it doesn't, it's just that RAS/TAPI is now gone), the Outlook crash I figure is a resolved problem.
The second machine, I have not touched for fear of invoking further evil demons form within (it's my primary work machine).
What command line does the rundll32 execute when you double click on the modem contaol panel applet? Can I run this from the command line seperatly? What about the rundll32 command line when you try and configure the Unimodem TAPI driver? Perhaps this is another staring point for research?
Using find file utility to find out what Unimodem support is in the sysdtem finds:
unimodv.* = No Files found
unimodem.* = No Files found
I did find the following:
Unimdm.tsp in c:\winnt\system32 Version 4.00 from Microsoft Corp. 1992-1995, file entry date stamp is Created August 9, 1996, modified 5/1/1997, and accessed June 5, 1997 and is Described as the Unimodem Service Provider.
Double click in the RasPhone.exe (Dialup Networking) gets you this error message:
Initialization of the dynamic link library: c:\winnt\system32\rasman.d
The process is terminating abnormally.
And then, Initialization of the dynamic link library c:\winnt\system32\rasscrpt
The process is terminating abnormally.
Double clicking on the devices control panel applet displays a dialog with:
Configuration Manager: This routine is not implemented in this version of the operating system.
In the event log, during the boot process, the following messages are entered:
Event ID: 8222 Source: NT Fax
Type: Error Category: Initialization/Termination
No fax devices were found.
Event ID: 8213 Source: NT Fax
Type: Error Category: Initialization/Termination
The fax service is stopped.
Event ID: 1008 Source: Perflib
Type: Error Category: None
The Open Procedure for service "Fax" in DLL "C:\WINNT\system32\faxperf
Status code returned is DWORD 0.
Event ID: 7024 Source: Service Control Manager
Type: Error Category: None
The Remote Access Connection Manager service terminated with service-specific error 615.
Event ID: 7001 Source: Service Control Manager
Type: Error Category: None
The Remote Access Autodial Manager service depends on the Remote Access Connection Manager service which failed to start because of the following error:
The service has returned a service-specific error code.
Event ID: 7001 Source: Service Control Manager
Type: Error Category: None
The Remote Access Server service depends on the Remote Access Connection Manager service which failed to start because of thefollowing error:
The service has returned a service-specific error code.
In the services control panel applet, we see that the "Telephony Service"
is up and running.
There appear to be no RAS related services running at all.
Another solution that I was considering was just installing NT Server over the top of what was currently there. I was thinking that NTS would be different enought that it would re-configure the TAPI drivers back to what they should be.
Where to next? How to recover? Any hints would be greatly appreciated.
Erik.
Erik Ch. Ohrnberger
email: Erik_Ch_Ohrnberger@bigfoot
ASKER
Uninstalled NT4SP3, booted, on boot event log system log had following messages:
Event ID: 7001
Source: Service Control Manager
Type: Error
Category: None
Description:
The Remote Access Autodial Manager service depends on the Remote Access Connection Manager service which failed to start because of the following error:
The service has returned a service-specific error code.
Event ID: 7024
Source: Service Control Manager
Type: Error
Category: None
Description:
The Remote Access Connection Manager service terminated with service-specific error 615.
Event ID: 7001
Source: Service Control Manager
Type: Error
Category: None
Description:
The Remote Access Server service depends on the Remote Access Connection Manager service which failed to start because of the following error:
The service has returned a service-specific error code.
The application log had the following:
Event ID: 8222
Source: NT Fax
Type: Error
Category: None
Description:
No fax devices werefound.
Still No Modem/TAPI apparently.
Used ERD to restore the registry:
System Config: Restored
System Information: Restored
Default User: Not Restored - should not be affected
NTUser: Not Restored - should not be affected
Security: NotRestored - SP3 alters SAM database structure (as per SP3 readme.txt)
The following files were detected as being different from the origonal install media:
File Version Description
\winnt\system32\cfgmgr32.d
\winnt\system32\digsig.dll
\winnt\system32\imagehlp.d
\winnt\system32\mfc40.dll 4.1.61.39 MFCDLL Shared Library - Retail Version
\winnt\system32\mfc42.dll 4.21.7022 MFCDLL Shared Library - Retail Version
\winnt\system32\msvcrt.dll
\winnt\system32\msvcirt.dl
\winnt\system32\perfc009.d
\winnt\system32\perfh009.d
\winnt\system32\riched20.d
\winnt\system32\riched32.d
\winnt\system32\softpub.dl
\winnt\system32\stdole2.tb
\winnt\system.ini No Version Information
\winnt\system32\windows.cn
\winnt\system32\odbcjt32.d
\winnt\system32\drivers\nb
\winnt\system32\drivers\ne
\winnt\system32\drivers\nw
\winnt\system32\drivers\nw
\winnt\system32\drivers\nw
\winnt\system32\drivers\rd
\winnt\system32\drivers\sr
\winnt\system32\drivers\nd
\winnt\system32\drivers\ra
\winnt\system32\drivers\tc
\winnt\system32\drivers\ne
Boot.When booting, noticed that banner still read NT 4 SP3?
on boot event log system log had following messages:
Event ID: 20032
Source: RemoteAccess
Type: Error
Category: None
Description:
Remote Access Connection Manager failed to start becauseit could not load one or more communication DLLs. Ensure that your communication hardware is installed and then restart the computer. If the problem persists, reinstall the Remote Access Service.
Event ID: 7024
Source: Service Control Manager
Type: Error
Category: None
Description:
The Remote Access Connection Manager service terminated with service-specific error 615.
Event ID: 7001
Source: Service Control Manager
Type: Error
Category: None
Description:
The Remote Access Autodial Manager service depends on the Remote Access Connection Manager service which failed to start because of the following error:
The service has returned a service-specific error code.
Event ID: 8222
Source: NT Fax
Type: Error
Category: None
Description:
No fax devices were found.
Still No Modem/TAPI apparently.
I went and reported all the versions in the list of files above. Perhaps you can use this to find out what the problem is (the table is in comma delimited format, so copy it tonotepad and turn work wrap off).
Event ID: 7001
Source: Service Control Manager
Type: Error
Category: None
Description:
The Remote Access Autodial Manager service depends on the Remote Access Connection Manager service which failed to start because of the following error:
The service has returned a service-specific error code.
Event ID: 7024
Source: Service Control Manager
Type: Error
Category: None
Description:
The Remote Access Connection Manager service terminated with service-specific error 615.
Event ID: 7001
Source: Service Control Manager
Type: Error
Category: None
Description:
The Remote Access Server service depends on the Remote Access Connection Manager service which failed to start because of the following error:
The service has returned a service-specific error code.
The application log had the following:
Event ID: 8222
Source: NT Fax
Type: Error
Category: None
Description:
No fax devices werefound.
Still No Modem/TAPI apparently.
Used ERD to restore the registry:
System Config: Restored
System Information: Restored
Default User: Not Restored - should not be affected
NTUser: Not Restored - should not be affected
Security: NotRestored - SP3 alters SAM database structure (as per SP3 readme.txt)
The following files were detected as being different from the origonal install media:
File Version Description
\winnt\system32\cfgmgr32.d
\winnt\system32\digsig.dll
\winnt\system32\imagehlp.d
\winnt\system32\mfc40.dll 4.1.61.39 MFCDLL Shared Library - Retail Version
\winnt\system32\mfc42.dll 4.21.7022 MFCDLL Shared Library - Retail Version
\winnt\system32\msvcrt.dll
\winnt\system32\msvcirt.dl
\winnt\system32\perfc009.d
\winnt\system32\perfh009.d
\winnt\system32\riched20.d
\winnt\system32\riched32.d
\winnt\system32\softpub.dl
\winnt\system32\stdole2.tb
\winnt\system.ini No Version Information
\winnt\system32\windows.cn
\winnt\system32\odbcjt32.d
\winnt\system32\drivers\nb
\winnt\system32\drivers\ne
\winnt\system32\drivers\nw
\winnt\system32\drivers\nw
\winnt\system32\drivers\nw
\winnt\system32\drivers\rd
\winnt\system32\drivers\sr
\winnt\system32\drivers\nd
\winnt\system32\drivers\ra
\winnt\system32\drivers\tc
\winnt\system32\drivers\ne
Boot.When booting, noticed that banner still read NT 4 SP3?
on boot event log system log had following messages:
Event ID: 20032
Source: RemoteAccess
Type: Error
Category: None
Description:
Remote Access Connection Manager failed to start becauseit could not load one or more communication DLLs. Ensure that your communication hardware is installed and then restart the computer. If the problem persists, reinstall the Remote Access Service.
Event ID: 7024
Source: Service Control Manager
Type: Error
Category: None
Description:
The Remote Access Connection Manager service terminated with service-specific error 615.
Event ID: 7001
Source: Service Control Manager
Type: Error
Category: None
Description:
The Remote Access Autodial Manager service depends on the Remote Access Connection Manager service which failed to start because of the following error:
The service has returned a service-specific error code.
Event ID: 8222
Source: NT Fax
Type: Error
Category: None
Description:
No fax devices were found.
Still No Modem/TAPI apparently.
I went and reported all the versions in the list of files above. Perhaps you can use this to find out what the problem is (the table is in comma delimited format, so copy it tonotepad and turn work wrap off).
Have you tried to repair your installations using the emergency repair disk?
ASKER
Uninstalled NT4SP3, booted, on boot then
Used ERD to restore the registry:
System Config: Restored
System Information: Restored
Default User: Not Restored - should not be affected
NTUser: Not Restored - should not be affected
Security: NotRestored - SP3 alters SAM database structure (as per SP3 readme.txt)
Still No Modem/TAPI apparently.
Used ERD to restore the registry:
System Config: Restored
System Information: Restored
Default User: Not Restored - should not be affected
NTUser: Not Restored - should not be affected
Security: NotRestored - SP3 alters SAM database structure (as per SP3 readme.txt)
Still No Modem/TAPI apparently.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also check the Knowledge Base from MS at www.microsoft.com/kb using the topics "telephony", "Service Pack 3", "RAS"
ASKER
Still looking for the set of DLLs and their versions that make up the TAPI part of this problem. I figure that if I can get the right versions, I can get it up and working without rebuilding the systems.
ASKER
Rebuilding from scratch is really not what I want to do. It costs me at least a week on the slow system, and at least 2-3 days on the fast system (a real software heavy).
If there was a registry corruption, then it should not be so hard to merge in the settings that represent the Modem and make TAPI driver for UniModem active again. There might also be some reg settings that configure the UniModem drivers, and I could merge those back in also.
I have the spare disk space to put up a small NT install for just this type of registry snooping.
The question is which registry hives to I need to look at?
If there was a registry corruption, then it should not be so hard to merge in the settings that represent the Modem and make TAPI driver for UniModem active again. There might also be some reg settings that configure the UniModem drivers, and I could merge those back in also.
I have the spare disk space to put up a small NT install for just this type of registry snooping.
The question is which registry hives to I need to look at?
Format your computer !
try :
format c: [Enter]
try :
format c: [Enter]
ASKER