Quantcast
Channel: Symantec Connect - Archiving and eDiscovery - Discussions
Viewing all articles
Browse latest Browse all 3821

EV 11 for Domino Search error with SSO

$
0
0
Oui, j'ai besoin d'une solution

I'm having issues trying to get EV 11 for Domino search to allow users to login with Web SSO.

I have run through the test process suggested here;

https://www-secure.symantec.com/connect/forums/ev-...

And I can reach names.nsf on the EVDG server but the EnterpriseVaultDomino/search/DominoLogin.aspx login fails every time.

When I run a DTrace I see the follow error but am not sure what this means or what I do to fix it, any suggestions, the server has been rebooted.

8    11:11:29.344     [2900]    (w3wp)    <3804>    EV:L    CBaseDirectoryServiceWrapper::CreateDirectoryService() - Entry [m_nNumTries = 40]
9    11:11:29.344     [2900]    (w3wp)    <3804>    EV:L    CBaseDirectoryServiceWrapper::CreateDirectoryService() - Successfully communicated with an EV Directory Service on the local machine
10    11:11:29.344     [2900]    (w3wp)    <8048>    EV-L    {EVS} Begin ContentManagementService::GetDominoServer()
11    11:11:29.344     [2900]    (w3wp)    <8048>    EV-L    {EVS} Begin ContentSource::GetDominoServer() For Domaincpxmiglab
12    11:11:29.422     [2900]    (w3wp)    <8048>    EV-L    {EVS} Server string successfully retrieved from Database, value is cpxevdg01.cpxmiglab.local:443@S
13    11:11:29.422     [2900]    (w3wp)    <8048>    EV-L    {EVS} End ContentSource::GetDominoServer() For Domaincpxmiglab
14    11:11:29.422     [2900]    (w3wp)    <8048>    EV-L    {EVS} End ContentManagementService::GetDominoServer()
15    11:11:29.438     [2900]    (w3wp)    <8048>    EV-H    {EVS} Exception: The underlying connection was closed: An unexpected error occurred on a send. Info:Exception occured while validating user 'evadmin%2fcpxmiglab'. ||  Diag: Type:System.Net.WebException ST:   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)|   at System.Net.HttpWebRequest.GetRequestStream()|   at Symantec.EV.Search.Client.Presentation.Presenters.LoginPresenter.AuthenticateDominoUser(String userName, String password, String dominoDomain) Inner:System.IO.IOException: Authentication failed because the remote party has closed the transport stream.|   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)|   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)|   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)|   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)|   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)|   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)|   at System.Net.TlsStream.CallProcessAuthentication(Object state)|   at System.Threading.ExecutionContext.runTryCode(Object userData)|   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)|   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)|   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)|   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)|   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)|   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)|   at System.Net.ConnectStream.WriteHeaders(Boolean async)


Viewing all articles
Browse latest Browse all 3821

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>