Can't Create OTMAuthentication Interface: Error code .800706ba

[nortelty]

thread798-1004740
I have a Nortel CS1000 TM3 installation on a Server 2003 machine. I'm trying to install the client software on a Windows 2000 pro machine. I originally received an error upon login that is in the referenced thread. I was able to export/import the COM+ application. I then received a different error code of .800706ba. Any ideas? I've checked share/NTFS permissions, COM+ settings, and DCOM. Does anyone know what this error refers to? The machines are in a common workgroup, not a domain.

 

[Tman45]

Not to thread crap, but:
Bottomline OTM sucks. Sometimes you have to hear the hard truth.
You shouldn't be using 2003 or 2000 as they are End of Life (aka security holes waiting to be abused). I guess you can have 'extended' 2003 support but there doesn't seem to be much point in extending the inevitable.
You need to invest in upgrading - plain and simple.
We had so many problems with OTM we rarely used it - this would be yet another reason to not use it.
In my opinion this would not be the right forum to search/post for answers anyway.
I wish I could help you, but I have not experienced an issue like this with OTM.

 

[intelligentium]

Try this

1) Reboot the PC and log in using the local admin account. Do not attempt to log into OTM.

2) Start --> Programs --> Administrative Tools --> Component Services

3) From Component Services expand the following folders --> Computers --> My Computer --> COM+ Applications

4) Right click and select properties of the OTM Application.

5) Select the Identity tab. Change the radio button from Interactive user to This User. Use the browse button to locate the Local Administrators account and select it. Input and confirm the password. Apply. Okay. Log into OTM.
========
Also this if not

enable DCOM through component services...start\control panel\administrative services\component services

when the console opens up double click the component services icon(takes a sec) then double click the computers folder. right click on My Computer and go into properties. Click the default properties tab and enable DCOM....

 

[DFKSydney]

Taken from a Nortel bulletin:



Can't create OTM authentication instance 800706ba
Problem Description

Fact:
Nortel Communication Server 1000 Telephony Manager
Optivity Telephony Manager
OTM
Client receives IP address via DHCP
Previously logged on


Symptom:
Can't create OTM authentication instance 800706ba
Authentication fails
Error: Can't create OTMAuthentication Instance
Event LogCOM got error "Class not registered" from the computer <Name> when attempting to activate the server...
Error: Authentication: 800706BA


Cause:
The 800706BA number means: Could not connect to the server. There are multiple causes that produce the error message.
A. Lease on IP address expired. Machine has a new IP address.
B General networking issues.
C. Client or server cannot resolve IP address from host name.
D. OTM was installed on the server using an account that was not a member of Administrators group
E. Software/settings on Client PC are preventing RPC from operating as intended.
Note: Review the PC Event Log and look for Service Control Manager having Issues.

Problem Resolution

Fix:
A. Edit client's IP address on server to match the new address:

1. From the Navigator window select Utilities, then Clients.
2. Highlight the correct machine name.
3. Click the Edit button.
4. Replace the IP address.
5. Click OK.

Do not remove the entire entry because the only way to restore it is to re-install the client.

Notebook users who frequently connect to different subnets may prefer to use the Web Client instead of constantly editing their IP address at the server.

B. Verify that the server exists, that it has correct network and DNS settings, and that the credentials supplied have administrative privileges on the server. Ensure port 135 is not being blocked by a router.

C. Build a Hosts table on the Client resolving the Sever IP to the Server Name and on the Server to resolve the Client IP to Client Name. Also, build an LMHosts table, see Optivity Telephony Manager Installation and Configuration (553-3001-230 September 2004) for OTM 2.2 starting at page 311.

Or

On the client PC: Go to Control Panel-->Administrative Tools-->Component Services-->Computers-->My Computer-->COM+ Application-->Right click on OTM Application-->Properties-->Activation-->Under Remoter PC ensure that the name entered is the name of the OTM server, if not edit to match server.

D. Un-install and re-install Nortel Communication Server 1000 Telephony Manager (formerly known as OTM) using the correct account.

E. Verify that The Operating System has the correct SP and verify that Q823980 hot fix has been installed.
OR
Re-install the operating system and patches, then re-install Nortel Communication Server 1000 Telephony Manager (formerly OTM).

 

[nortelty]

Ok, thanks guys. I had done all of those things, except enabling name resolution on my segmented network. Now I'm getting the 80070005 error when trying to log into the client. Does your manual have the meaning of that error code? Also, I decided to try an XP machine for the client, instead of a W2K.

 

[nortelty]

The only unusual thing that I noticed while trying your suggestions is that when I try to edit the identity of the Com+ application on the client, I cannot. The message at the bottom of the Window says "Proxy Applications do not have identities".

 

[nortelty]

Any ideas? Anybody?

 

[Firebird Scrambler]

I've found this extra record below.

Error message ' Can't create OTMauthentication Instance ' followed by
' Authentication 800706ba ' on TM 3.2 client

Solution
Allow TCP/UDP port 135 and TCP port 139 on any firewalls between client and server

Full solution
Error message ' Can't create OTMauthentication Instance ' followed by ' Authentication ' 800706ba ' on Telephony Manager ( TM 3.2 ) client when trying to login to TM server.
It was found that port 135 was blocked on a firewall between the Lan where the TM client was connected and the Lan where the TM server was connected. Once port 135 was unblocked all was OK. Note that port 139 should also be unblocked for successful logon.
See NTP NN43050-300 Telephony Manager 3.2 Installation and Commissioning for full list of ports required by Telephony Manager.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.