Dialer, TAPI3.DLL Cont'd

[mn_voyageur]

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

 

[Larry Gardner]

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]

Remote Procedure Call (RPC) is "Started"

Telephony is not in my list of services.

How do I add it?

Mark

 

[Larry Gardner]

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]

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]

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]

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!

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)?

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

 

[Guest]

Hi Voyageur,
With Respect to Larry, Voyageur do you have this KEY in your Registry
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Telephony\Handoffpriorties.
And in the Right Pane or [Window] Rather check if you have the KeyString of
DIALER.EXE.
If not try to Right click there on the Blank space and Select New and Select
String and in the Edit String Window type this Under the Value Name:
RequestMakeCall
And Under Value Data:
DAILER.EXE, Click Ok and Exsit the Registry Editor and Reboot and See if the
Issue Resolved.
Hope this helps
Regards
nass

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!

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)?

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?

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?

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

 

[mn_voyageur]

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Telephony\Handoffpriorties.

YES - Dialer.exe is there.

Thanks for the help. Any other suggestions?

Hi Voyageur,
With Respect to Larry, Voyageur do you have this KEY in your Registry:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Telephony\Handoffpriorties.
And in the Right Pane or [Window] Rather check if you have the KeyString of
DIALER.EXE.
If not try to Right click there on the Blank space and Select New and Select
String and in the Edit String Window type this Under the Value Name:
RequestMakeCall
And Under Value Data:
DAILER.EXE, Click Ok and Exsit the Registry Editor and Reboot and See if the
Issue Resolved.
Hope this helps
Regards
nass

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!

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)?


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?

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?

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

 

[Larry Gardner]

Make sure that you have C:\Windows\System32\tapisvr.dll. Open a command
prompt (STart Menu | Run, enter cmd)

1. CD C:\windows\system32
2. DIR tapi*.*

Compare to these:

08/10/2004 19,200 tapi.dll
08/10/2004 858,624 tapi3.dll
08/10/2004 181,760 tapi32.dll
08/10/2004 5,632 tapiperf.dll
07/08/2005 249,344 tapisrv.dll (newest of list ... time 12:27p)
08/10/2004 78,848 tapiui.dll

The tapisrv.dll was modified. To verify, check registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows
XP\SP3\KB893756\Filelist\0

Notice they are building SP3 ... KB893756 is the knowledge Base item.

Just to doubly making sure: when you checked the last registry key: you
were under CurrentControlSet not any of the other ControlSet### keys,
correct?

Also check:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TapiSrv\Parameters and
ensure the there is a value:

ServiceDll REG_EXPAND_SZ
%SystemRoot%\system32\tapisrv.dll

I searched my registry and that is the only places tapisrv.dll is referenced
.... thos keys.

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!

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)?

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?

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?

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

 

[mn_voyageur]

My DIR tapi*.* =
08/29/2002 19,200 tapi.dll
08/04/2004 858,624 tapi3.dll
08/04/2004 181,760 tapi32.dll
08/29/2002 5,632 tapiperf.dll
07/08/2005 249,344 tapisrv.dll (I have 12:27p)
08/29/2002 78,848 tapiui.dll

Files sizes match, some dates do not.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\WindowsXP\SP3\KB893756\Filelist\0
Does show tapisrv.dll / Fri Jul 08 12:27:56 2005 /
C:\WINDOWS\system32 / 5.1.2600.2716

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TapiSrv\Parameters
Does Match

Mark

Make sure that you have C:\Windows\System32\tapisvr.dll. Open a command
prompt (STart Menu | Run, enter cmd)

1. CD C:\windows\system32
2. DIR tapi*.*

Compare to these:

08/10/2004 19,200 tapi.dll
08/10/2004 858,624 tapi3.dll
08/10/2004 181,760 tapi32.dll
08/10/2004 5,632 tapiperf.dll
07/08/2005 249,344 tapisrv.dll (newest of list ... time 12:27p)
08/10/2004 78,848 tapiui.dll

The tapisrv.dll was modified. To verify, check registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows
XP\SP3\KB893756\Filelist\0

Notice they are building SP3 ... KB893756 is the knowledge Base item.

Just to doubly making sure: when you checked the last registry key: you
were under CurrentControlSet not any of the other ControlSet### keys,
correct?

Also check:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TapiSrv\Parameters and
ensure the there is a value:

ServiceDll REG_EXPAND_SZ
%SystemRoot%\system32\tapisrv.dll

I searched my registry and that is the only places tapisrv.dll is referenced
... thos keys.

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!

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)?


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?

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?

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

 

[Larry Gardner]

Will have to think on this some more. May need to check version numbers.
Don't know why Telephony does not display in Services. Your
CurrentControlSet shows that it should. Nothing indicates why it is not
there.

Your are logged in as an Admin user, correct?

 

[Larry Gardner]

By the way, without a dialup ... how are you currently connecting to the
Internet?

 

[mn_voyageur]

Yes, I am Administrator.

I am on cable.

I have Fax software that works fine.

My contact manager does not work because it uses dialer.

Mark

 

[Larry Gardner]

What contact manager, can you say?

It maybe that dialer.exe doesn't work because Telephony was not setup ...
because it is not needed on Cable Modem systems. Basically, you have a
Always On network.

To see what is installed based on hardware:

1. Open Control Panel | System Properties \ Hardware | Device Manager
2. Click on View and set Show Hidden Devices
3. Then check what is installed as far as Network Adapters

You should see whether or not Telephony is needed.

Does everything else work as pertaining to the network, E-Mail, Browser,
Instant Messenger, Media Players, ...?

 

[mn_voyageur]

Everything works that does not use Telephony.
My fax software works, because it just runs the modem directly.

I never would have thought that Telephony was a Network Adapter.

No, Telephony is not listed under Hardware | Device Manager | Network
Adapters.

So, how do I add Telephony to my Network Adapter List?

Mark

 

[Larry Gardner]

Telephony should not be under Network Adapters. I just wanted you to see
jow your system is enabled when using a Cable Modem.
Should have been more explicit.

What is your Contact Manager you are having a problem with? MS Outlook?

 

[mn_voyageur]

Act!

When I called them about not being able to dial, they instructed me to
run Dialer from Start | Run.

When dailer failed ... end of troubleshooting for the Act! Technician.


Mark

 

[Larry Gardner]

Don't know if I asked this before. Windows XP Pro/Home? All ServicePacks
AND Patches?

 

[mn_voyageur]

XP Pro and all SP's and patches.

Mark

Don't know if I asked this before. Windows XP Pro/Home? All ServicePacks
AND Patches?