11-05-2001 02:04 AM - edited 03-12-2019 01:10 PM
We have an Xpressions Site where the customer can not access System Admin screens.<br>They receive a screen which states<br>Access denied<br>Your Windows Domain Account [TRSNT\xadmin] is not associated with a Xpressions Subscriber.....<br>The application log pegs the following event<br>11/5/01,1:48:57 PM,AvCsServices_MC,Information,Warning ,1077,N/A,XPRESSIONS,Gateway FindCsComponents failed [, 0x80070005] (caller is denied access). <br><br>The other piece of information that is strange is when Xpressions is booting I see the following errors<br>11/5/01,10:47:30 AM,AvCsServices_MC,Information,Init ,1024,N/A,XPRESSIONS,AvCsMgr: Component Arbiter initialize succeeded. <br>11/5/01,10:47:29 AM,AvCsServices_MC,Error,Error ,1086,N/A,XPRESSIONS,Gateway Run failed : [0x80004005] <br>11/5/01,10:47:29 AM,AvCsServices_MC,Error,Error ,1087,N/A,XPRESSIONS,Gateway: Initialization of Doh security failed : [0x80004005] <br>11/5/01,10:47:29 AM,Doh_MC,Error,Error ,32023,N/A,XPRESSIONS,Doh logon failed due to caledaring component validation error: Unspecified error<br> <br>11/5/01,10:47:29 AM,AvCs_MC,Error,None,100,N/A,XPRESSIONS,Exception occurred and handled in File: h:\CommSvr\Sources\doh\SrcCache\AvDohSession.cpp at Line: 388 - Error: 80004005H Call stack: <br> <br>11/5/01,10:47:29 AM,AvWM_MC,Information,Init ,29000,N/A,XPRESSIONS,532:727: The server monitor thread has started <br>11/5/01,10:47:29 AM,AvWM_MC,Information,Stop ,29001,N/A,XPRESSIONS,532:707: The server monitor thread has stopped <br><br>Any suggestions?<br><br><br><br>
11-05-2001 08:02 AM
The usual approach when you can't get into the SA is to assocate the currently logged in NT account with the Example Administrator Exchange account, wait for a cache resync and then access the SA. I know the Xpressions product might not have an "Example Administrator" created by its default database but it should have some account created by default that's not bound to an NT account and is a member of the Administrator COS
however your other event log messages are odd. The calendaring component shouldn't even be loading (the calendaring features were never completed and those modules shouldn't even be starting). Can you pop open the MaestroTools application and see if the calendaring modules are listed in the components to be started on the registry tab? If so, you might back them out of the components to be started and restart Unity. Not sure if this is related to your authentication issues but seeing any kind of failure in the DOH startup is generally not good.
Can you access the SA from any account or is it just a particular account having trouble?
Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)
11-06-2001 09:13 AM
Thanks Jeff.
The issue was system-wide multiple users, multiple clients.
They could not logon to Xpressions Admin, Xpressions Assistant or initiate TRAP Calls.
The issue has since cleared up however. The last thing done was the site deleted the _CallHandlerCache.doh and _MailUserCache.doh , then rebooted the Xpressions Server.
In addition the doh errors did not return in the app log during the Xpressions reboot.
For now, we'll keep on eye on this and see if the issue returns.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide