Manually store and restore does not work using Outlook and tcp/ip (LAN) connection

[Tips]

Why does manually store or restore not work while Outlook is connected using tcp/ip connection (LAN)?

Store and restore works fine, while Outlook is configured with rpc over http.

Store error message: 0x800706ba (RPC server unavailable)
Restore error message: Enterprise Vault is not runnign at the moment, so none of the Enterprise Vault functionality is available.
There are also events in Windows Event log, Even ids are: 8229 and 8390

Oultook 2003 Clients are in different domain than Evault 8 and Exhcange 2007server. Ev and Exchange are in same domain.
All network traffic are allowed between these domains and trusts are verified.

[Michael_Bilsbor]

Hi,

The EV client has two different ways to communicate with the EV server.  Either using DCOM or HTTP.  When using rpc over http then the requests are unsurprisingly done using http and so that appears to be working.  So I presume that the client is currently configured to use the DCOM method of communcating with the EV server and failing.

Depending upon which EV client you have installed you can make the client use HTTP if you wish and that should avoid whatever the underlying issue is.  You need to check though the EV documentation , as the two clients work slightly differently which may or may not be an issue for you.

The events you mention, can you post them here.  Also are you sure that they appear when you get the end user request failing(it;s possible but i'd want to be sure)?  If you are getting events on the EV server at the same time then it feels like some kind of underlying server issue, are there other problems with the system right now?  Perhaps a DNS alias resolution issue for example.

Cheers.

Mike

[Tips]

Hi Mike,

As you presumed Clients are Enterprise Vault Client 8.0.3.1845.0 (DCOM).

Enterprise Vault Event Ids appear at the same time with enduser pop-up error messages.
DNS alias resolution works ok, client can ping and connect (http:\\alaisname) using aliasname.

There is one interesting line EVSERVERS in the ev_client_log. Line value is fqdn of EVault aliasname and short netbiosname. Should both name be fqdn? (Client can't ping Evault using netbiosname, they must you fqdn to find resources in domain.local)

For example if Evault server netbiosname is myserver1 and aliasname  is evserver1 and Evserver is located in domain.local. Then line  setting is: EVSERVERS = evserver1.domain.local, myserver1. Is this ok? 
Or should there be EVSERVERS = evserver1.domain.local, myserver1.domain.local.
From where can we change this EVSERVERS -value?

Here are Enterprise Evault Event Ids attached:
Id 8390: Type: Error, Description: Not found from source Enterprise Evault



Id 8229
Type: Information
Description not found from source Enteriprise Evault


There was also two DCOM events in System log. I'll translate those shortly here:

Event Id 10000 (DCOM):  Unable to start a DCOM Server: {306......}. The following error message appeared while starting C:\Program Files\system32\sglogp~1.exe –Embedding: “No process is on the other end of the pipe.”



Event Id 10016 (DCOM):
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: Date
Time: Time
User: NT AUTHORITY\SYSTEM
Computer: "EV-client computer"
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {24.....} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18). This security permission can be modified using the Component Services administrative tool.



It seems to have DCOM communication promlem. How should Clients' DCOM be configured right to communicate with EV server? Which are Required settings for DCOM to work? There are not any clients working ok using DCOM. DCOM is enabled in EVault, but there are no rcp:135 networtk traffic from client to EVault (if client is configured to use DCOM). There are only rcp:135 traffic from client to Exchange server.

There are two types of clients in this Organisation: other can use http and other must use DCOM.

[Tips]

I monitored Client DCOM status (configuring registry settings DCOMOverrideRCPHTTP and DCOMPollInterval)

CDCOMStatus::MonitoringThread: DCOM Status = Unavailable

[Tips]

Clients and EV are in separate domains (forests). How should DCOM be configured in clients and Evault Server to communicate with each other?
Which are required settings for DCOM to work? Clients and EV server have DCOM enabled and all firewall ports opened and still not working.

[bagrationi]

I have the same issue in my production, do you have resolved it or still waiting to some solution... ?

Thanks,

[JesusWept3 · Accepted solution]

most likely the issue is that if you are in two different domains, you need to add the 2nd domain to the DNS Suffix in the properties of the TCP/IP protocol under your network card