Re: Dialer, TAPI3.DLL Cont'd



Is the error message from Event Viewer or Dialog Window when you use
Dialer.exe?
Upon running Dailer, the error pops up immediately, before you can
do anything.

Event Viewer Log indicates: (Serveral Entries)
The Remote Access Connection Manager service depends on the following
nonexistent service: Tapisrv

Your Registry matches mine.

Plug and Play Service is started.

XP Pro.

What next?

Mark

PS - Sorry for making you walk. My wife says I need to walk MORE!


Larry Gardner wrote:
That's OK about W2K ... although you did make me get up and walk into my
bedroom and check my other system. Should dock you!!!!

OK, you got TapiSrv. Need to know answers to other questions. Is the error
message from Event Viewer or Dialog Window when you use Dialer.exe?
Have you checked Event Viewer for errors?

Now check this in that registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TapiSrv

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TapiSrv]

DependOnService REG_MULTI_SZ PlugPlay RpcSs
Description REG_SZ
Provides Telephony API (TAPI) support for programs that control telephony
devices and IP based voice connections on the local computer and, through
the LAN, on servers that are also running the service."
DisplayName REG_SZ
Telephony
ErrorControl REG_DWORD
0x00000001
ImagePath REG_EXPAND_SZ
%SystemRoot%\System32\svchost.exe -k netsvcs
ObjectName REG_SZ
LocalSystem
Start REG_DWORD
0x00000003
Type REG_DWORD
0x00000020

See how close yours our to mine.

When you look in Event Viewer, look under Applications and Systems,
specifically at the times the system shows rebooted. See if anything shows
ERROR.

Also I forgot to ask, check the Plug and Play Service. It should be
Automatic and Started.

What Windows XP (Home, Pro or Media Center)?


"mn_voyageur" <mn_voyageur@xxxxxxxxx> wrote in message
news:1149043282.888994.46470@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
My mistake on that one.

I am running XP SP2 current updates have been installed.

I found a similar question on another post for W2K OS. And regsvr32
was the fix.

The complete error message that I am receiving is:
Operation: Initializing Windows Telephony Services.
Details: Failed initializing a telephony service component
(TAPI3.DLL). System registry may be corrupted. If symptoms persist,
try restarting Windows or Using REGSVR32 to update registry settings
for the TAPI components.
Error: The operation failed for an unspecified reason.

Since the W2K post indicated that REGSVR32 was the fix, and my message
indicated that I might need to run REGSVR32, I ran REGSVR32.

I apologize for the confusion.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TapiSrv - IS
THERE.

What else do I need to find?

Mark

Larry Gardner wrote:
Sorry ... should have asked ... what Windows 2000 do you have ... and do
you
have Service Pack 4 and ALL patches?

Check this registry key (if you have):

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TapiSrv

Is it there?

Is this a new install of Windows 2000? Or did this just start happening.
Is this after a repair of Windows 2000?

"mn_voyageur" <mn_voyageur@xxxxxxxxx> wrote in message
news:1149040410.486971.284110@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Remote Procedure Call (RPC) is "Started"

Telephony is not in my list of services.

How do I add it?

Mark

Larry Gardner wrote:
Have you tried checking Telephony in Administrative Tools | Services?

Telephony should be set to Automatic and status should be Started.

Also Remote Procedure Call (RPC), which Telephony is dependent on,
should
also be Automatic and Started.

Did you check if there are any errors in Event Viewer?

"mn_voyageur" <mn_voyageur@xxxxxxxxx> wrote in message
news:1149032023.162167.106670@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
When I run/start dialer.exe I get this error message; "Failed
initializing a telephony service component (TAPI3.DLL). System
registry
may be corrupted.

When I go to Control panel/Phone and Modem I get the following
message;
"Phone and Modem services can not be opened. You may have a problem
with your telephony services."

Another post for Windows 2000 suggested:
regsvr32 c:\WINDOWS\system32\tapi3.dll
tapi3.dll is in this directory.
Did not fix the problem.

Any help would be greatly appreciated.

Mark




.



Relevant Pages

  • Re: System very slow, very difficult to access server, cpu usage l
    ... Windows saved user MARK4017DESKTOP\Owner registry while an ... application or service was still using the registry during log off. ... You need to post copies of the Error Reports from Event Viewer if I ...
    (microsoft.public.windowsxp.general)
  • Re: Dialer, TAPI3.DLL Contd
    ... Just to doubly making sure: when you checked the last registry key: you ... Provides Telephony API support for programs that control telephony ... Operation: Initializing Windows Telephony Services. ...
    (microsoft.public.windowsxp.basics)
  • Re: Dialer, TAPI3.DLL Contd
    ... Larry Gardner wrote: ... Just to doubly making sure: when you checked the last registry key: you ... Provides Telephony API support for programs that control telephony ... Operation: Initializing Windows Telephony Services. ...
    (microsoft.public.windowsxp.basics)
  • Re: Registry Mechanic
    ... may be especially noticed by those upgrading to Windows XP from an earlier version of Windows. ... Check whether all the programmes loading when Windows is started are really necessary. ... You can access Event Viewer by selecting Start, ... I tried 'registry' and couldn't ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Dialer, TAPI3.DLL Contd
    ... With Respect to Larry, Voyageur do you have this KEY in your Registry: ... Provides Telephony API support for programs that control telephony ... Operation: Initializing Windows Telephony Services. ...
    (microsoft.public.windowsxp.basics)