Video Screencast Help

Event 6281 IStorageOnlineOpns (0x80072afc)

Created: 23 Aug 2013 • Updated: 03 Oct 2013 | 13 comments
Jochen Köcher's picture
This issue has been solved. See solution.

Hi there,

I have the following error rahter often on my EV servers.

Does anybody know and how to solve this?

Many thanks

Jochen.

 

Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault
Date:          23.08.2013 12:10:09
Event ID:      6281
Task Category: Web Application (WP)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     
Description:
Could not obtain the computer name on which to query for an IStorageOnlineOpns interface
The requested name is valid, but no data of the requested type was found.  (0x80072afc)

For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&languag...
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Enterprise Vault " />
    <EventID Qualifiers="49156">6281</EventID>
    <Level>2</Level>
    <Task>99</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-23T10:10:09.000000000Z" />
    <EventRecordID>1837527</EventRecordID>
    <Channel>Symantec Enterprise Vault</Channel>
    <Computer>%server.fqdn%</Computer>
    <Security />
  </System>
  <EventData>
    <Data>The requested name is valid, but no data of the requested type was found.  (0x80072afc)</Data>
  </EventData>
</Event>

Operating Systems:

Comments 13 CommentsJump to latest comment

Pradeep_Papnai's picture

Good morning Jochen,

Do you see error 6287 along with error 6281 you have mentioned? I am not sure if triggered dtrace can be taken as you seen these errors very intermittently.

I would also advice to ask support if they have any situation around above error.

Regards
EV-C

Jochen Köcher's picture

Hi EV-C

I do see 6287 warnings... I cannot say they are along. Very few 6281 errors do come with a 6287 warning. most of the time the warnings (6287) and the errors are separated.

I thought about contacting support. I always believe I cannot be the only one seeing these errors... ;-)

Thanks for your response;
Jochen.

Pradeep_Papnai's picture

These errors have seen internally as well, but reason & solution is still unknown, so if you contact support then they would be able to give more insight about this situation.
 

JesusWept3's picture

If I had to guess it would be from a shortcut that doesn't belong in the site
You could always just configure backtrace and leave that goin till you see it happen again

You may also want to look in your iis logs, for anything like viewmessage or download.asp for those time ranges and see I'd you can narrow it down to a user

Jochen Köcher's picture

Hi there,

I activated a backtrace and found the following:

157    12:19:43.983     [20536]    (w3wp)    <13488>    EV:L    {VaultCoCreateInstanceEx} CLSID [{F019A230-FF92-11D1-8C20-0000F87502DE}] Server Name [alias.fqdn.de] Used Server Name [alias.fqdn.de] Num of attempts [1] Total elapsed [0.003s] Result [Success  (0)]
158    12:19:43.983     [20536]    (w3wp)    <13488>    EV:M    GetStorageObject - Checking MULTI_QI.hr
159    12:19:43.983     [20536]    (w3wp)    <13488>    EV:L    {CClientAuthenticate::GenAuthString:#361} Generating auth string...
160    12:19:43.999     [20536]    (w3wp)    <13488>    EV:M    ClientAuthHelperImpl::GenAuthString Authentication Type: Currently impersonated user Client:(null) ==> AuthToken:host.fqdn.local vyuh*****
161    12:19:44.296     [20536]    (w3wp)    <13488>    EV:L    CAuthHelper::Reset Cancel registration? True CancelId: 13203040
162    12:19:44.296     [20536]    (w3wp)    <13488>    EV:L    {CAutoStorageOnline::GetOnlineAttachmentFileSize} (Exit) Status: [Success]
163    12:19:44.296     [20536]    (w3wp)    <13488>    EV:L    {CAutoStorageOnline::~CAutoStorageOnline} (Entry)
164    12:19:44.296     [20536]    (w3wp)    <13488>    EV:L    {CQueue::Delete} (Entry)
165    12:19:44.296     [20536]    (w3wp)    <13488>    EV:H    {CQueue::Delete}|Deleting queue:
166    12:19:44.296     [20536]    (w3wp)    <13488>    EV:L    {CQueue::Delete} (Exit) Status: [Success]
167    12:19:44.296     [20536]    (w3wp)    <13488>    EV:L    {CAutoStorageOnline::~CAutoStorageOnline} (Exit) Status: [Success]
168    12:19:44.296     [20536]    (w3wp)    <13488>    EV:L    {CQueue::~CQueue} (Entry)
169    12:19:44.296     [20536]    (w3wp)    <13488>    EV:L    {CQueue::~CQueue} (Exit)
170    12:19:55.076     [20536]    (w3wp)    <11204>    EV:L    {CQueue::CQueue} (Entry)
171    12:19:55.076     [20536]    (w3wp)    <11204>    EV:L    {CQueue::CQueue} (Exit)
172    12:19:55.076     [20536]    (w3wp)    <11204>    EV:L    {CAutoStorageOnline::GetStorageComputer} (Entry)
173    12:19:55.076     [20536]    (w3wp)    <11204>    EV:M    DirectoryConnection: Function call: CVersionUpdate::NewInstallation |
174    12:19:55.076     [20536]    (w3wp)    <11204>    EV:L    CBaseDirectoryServiceWrapper::CreateDirectoryService() - Entry [m_nNumTries = 40]
175    12:19:55.076     [20536]    (w3wp)    <11204>    EV:L    CBaseDirectoryServiceWrapper::CreateDirectoryService() - Will try to connect to EV Directory Service on ALIAS (1)
176    12:19:57.357     [20536]    (w3wp)    <11204>    EV:L    {VaultCoCreateInstanceEx} Attempt [1] to create COM object failed. CLSID [{F4D3EB5B-C7C5-11D1-90DB-0000F879BE6A}] Server Name [ALIAS (1)] Elapsed [2.277s] Result [The RPC server is unavailable.  (0x800706ba)]
177    12:19:59.825     [20536]    (w3wp)    <11204>    EV:H    VaultCoCreateInstanceEx GetMachineNameUsingHostNameHelper failed. Server Name [ALIAS (1)] Error [The requested name is valid, but no data of the requested type was found.  (0x80072afc)]
178    12:19:59.825     [20536]    (w3wp)    <11204>    EV:M    CBaseDirectoryServiceWrapper::CreateDirectoryService() failed.|Hr: 0x80072afc|Retries: 0|TryLocal: false|Directory Name: ALIAS (1)|
179    12:19:59.825     [20536]    (w3wp)    <11204>    EV:H    {CBaseDirectoryServiceWrapper::GetInterface} HRXEX fn trace : Error [0x80072afc], ref(1): [ALIAS (1)], [.\DirectoryServiceWrapper.cpp, lines {629,656,680}, built Jul 10 17:51:39 2013].
180    12:19:59.825     [20536]    (w3wp)    <11204>    EV:H    {CDirectoryConnectionObject::ReadStorageServiceComputerByVault} HRXEX fn trace : Error [0x80072afc], [.\DirectoryConnectionObject.cpp, lines {1059,1067}, built Jul 10 17:51:39 2013].
181    12:19:59.825     [20536]    (w3wp)    <11204>    EV:L    {VaultCoCreateInstanceEx} CLSID [{F4D3EB5B-C7C5-11D1-90DB-0000F879BE6A}] Server Name [(null)] Used Server Name [(null)] Num of attempts [1] Total elapsed [0.001s] Result [Success  (0)]
182    12:19:59.825     [20536]    (w3wp)    <11204>    EV~E    Event ID: 6281 Could not obtain the computer name on which to query for an IStorageOnlineOpns interface|The requested name is valid, but no data of the requested type was found.  (0x80072afc) |
183    12:19:59.888     [20536]    (w3wp)    <11204>    EV:H    {CAutoStorageOnline::GetStorageComputer} (Exit) Status: [The requested name is valid, but no data of the requested type was found.  (0x80072afc)]
184    12:19:59.888     [20536]    (w3wp)    <11204>    EV:L    {CAutoStorageOnline::~CAutoStorageOnline} (Entry)
185    12:19:59.888     [20536]    (w3wp)    <11204>    EV:L    {CQueue::Delete} (Entry)

What I find surprising is the fact it looks for ALIAS (1). With the blank and (1) it's no official name to be queried and obviously fails.

I have no idea though where this (1) would come from. I keep looking. Just an update from my side.
Regards,
Jochen.

Jochen Köcher's picture

Each error event goes along a IIS error from a user. While the server was updated to EV 10.0.4, the Outlook plugins are still 10.0.2. I receive errors dating back a few months... so it might be version independant.

2013-08-26 13:05:38 10.10.151.58 POST /EnterpriseVault/GetVaultInformation.aspx x=evoutlookext&evhost=https://alis.fqdn.de/EVAnon 443 DOMAIN\user IP 10.10.64.42 EnterpriseVaultOutlookExt-V10.0.2.1210 500 0 0 4765

The request comes from an IP address of a users desktop. But still it goes to "https://alis.fqdn.de/EVAnon 443". The IIS response is 500 and not as expected "HTTP Error 403.6 - Forbidden".

This is really getting interesting.

JesusWept3's picture

ok so quick question
i'm guessing you swapped out ALIAS and alias.fqdn.de for your actual domain names right?

Does ALIAS = alias.fqdn.de?

i.e. if i have evsite.myDomain.com
is it saying evsite.mydomain.com = success
but evsite = failed?

Cos i see this line here:
157 12:19:43.983 [20536] (w3wp) <13488> EV:L {VaultCoCreateInstanceEx} CLSID [{F019A230-FF92-11D1-8C20-0000F87502DE}] Server Name [alias.fqdn.de] Used Server Name [alias.fqdn.de] Num of attempts [1] Total elapsed [0.003s] Result [Success (0)]

So it can connect to Alias.fqdn.de just fine
but here it cannot connect to ALIAS

175 12:19:55.076 [20536] (w3wp) <11204> EV:L CBaseDirectoryServiceWrapper::CreateDirectoryService() - Will try to connect to EV Directory Service on ALIAS (1)

it may be worth doing a quick query like this

USE EnterpriseVaultDirectory
SELECT ComputerName, ComputerNameAlternate
FROM ComputerEntry

Then make sure you can ping each Computer Name (EV Server Alias) and each Computer Name Alternante (The actual machine name)

Would still suggest going through your IIS logs to around this time: 12:19:55.076, which in IIS will be UTC, so the time stamp should be 10:19:55, this will hopefully give you who was requesting the message, what username and what ip address

Jochen Köcher's picture

Yes, for protection of customer anonymity I changed the domain names. - All servers can connnect to all other EV servers just fine with alias, alias.fqdn, hostname, hostname.fqdn.

What is not working and what is startling me is the fact a request was made to "alias (1)" - see backtrace above. It says:

Server Name [ALIAS (1)] Error [The requested name is valid, but no data of the requested type was found.  (0x80072afc)]
JesusWept3's picture

yeah the 0 is success and 1 is failure

So if you look at this
Used Server Name [alias.fqdn.de] Num of attempts [1] Total elapsed [0.003s] Result [Success (0)]

that's succesful, but this gives an error
Server Name [ALIAS (1)]

Quick question, is IPv6 enabled on the 10 SP4 EV Server?

Jochen Köcher's picture

In a call with Symantec we found the cause of these errors.

  • In the enterprise vault server event was the above mentioned error.
Could not obtain the computer name on which to query for an IStorageOnlineOpns interface
The requested name is valid, but no data of the requested type was found.  (0x80072afc)
  • In the IIS log of the server was the following 500 error for GetVaultInformation.aspx.
YYYY-MM-DD HH:MM:SS EV-IP-Address POST /EnterpriseVault/GetVaultInformation.aspx x=evoutlookext&evhost=https://FQDN/EVAnon 443 %domain%\%username% IP-Adress EnterpriseVaultOutlookExt-V10.0.2.1210 500 0 0 4734

We figured out that the user had two MDC files on the desktop computer pointing to the same archive ID. In my cases the vault cache did not update properly.

Generally when the user adds the archives of other users to be stored in the local vault cache, there are multiple MDC files. But the name of the MDC files will be different for each user added. In our case, the names of the MDC files were the same; the only difference was a (1) at the end of the name, e.g.:

1BA8B85F435531F4188E23A9BC308973B1110000servername.mdc
1BA8B85F435531F4188E23A9BC308973B1110000servername (1).mdc

That was leading to an error and the Vault Cache did not update properly. We have no idea how on 6 users' desktops out of multiple thousand the MDC file could be created twice. The EV client is not doing that in any possible way. If you want to rename the MDC file, the file extension should be named to .old. All other processes as in a VC reset, all vault cache related files (incl. MDC files) will be deleted.

We did a VC reset and the problem disappeared.

SOLUTION
Pradeep_Papnai's picture

Many thanks for update Jochen.

Merv's picture

FYI - Faced this issue to after an upgrade from EV9.0.4 to 10.0.3. Thanks for the solution of deleting the duplicate (1).mdc files from the Vault Cache which has stopped the errors.

Pradeep_Papnai's picture

Good to know :) Merv.