2 Replies Latest reply: Oct 17, 2012 7:50 AM by SinfoMichele RSS

    Problem with DRL Attachment

    SinfoMichele
      Hi, I have a problem with DRL Attachment.
      In GSM Spec, when I try to attach a file (few Kb) in Supporting Document Section, upload works fine. But when I try to download attached file returns this error:

      Server Error in '/drl' Application.
      --------------------------------------------------------------------------------

      Microsoft.Web.Services2.Security.SecurityFault: The security token could not be authenticated or authorized ---> System.Exception: WSE565: The password provided the SecurityTokenManager does not match the one on the incoming token.
      at Microsoft.Web.Services2.Security.Tokens.UsernameTokenManager.VerifyPlainTextPassword(UsernameToken token, String authenticatedPassword)
      at Microsoft.Web.Services2.Security.Tokens.UsernameTokenManager.VerifyPassword(UsernameToken token, String authenticatedPassword)
      at Microsoft.Web.Services2.Security.Tokens.UsernameTokenManager.VerifyToken(SecurityToken securityToken)
      at Microsoft.Web.Services2.Security.Tokens.SecurityTokenManager.LoadXmlSecurityToken(XmlElement element)
      --- End of inner exception stack trace ---
      at Microsoft.Web.Services2.Security.Tokens.SecurityTokenManager.LoadXmlSecurityToken(XmlElement element)
      at Microsoft.Web.Services2.Security.Tokens.SecurityTokenManager.GetTokenFromXml(XmlElement element)
      at Microsoft.Web.Services2.Security.Security.LoadToken(XmlElement element, SecurityConfiguration configuration, Int32& tokenCount)
      at Microsoft.Web.Services2.Security.Security.LoadXml(XmlElement element)
      at Microsoft.Web.Services2.Security.SecurityInputFilter.ProcessMessage(SoapEnvelope envelope)
      at Microsoft.Web.Services2.Pipeline.ProcessInputMessage(SoapEnvelope envelope)
      at Microsoft.Web.Services2.WebServicesExtension.BeforeDeserializeServer(SoapServerMessage message)

      Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.


      Exception Details: System.Web.Services.Protocols.SoapHeaderException: Microsoft.Web.Services2.Security.SecurityFault: The security token could not be authenticated or authorized ---> System.Exception: WSE565: The password provided the SecurityTokenManager does not match the one on the incoming token.
      at Microsoft.Web.Services2.Security.Tokens.UsernameTokenManager.VerifyPlainTextPassword(UsernameToken token, String authenticatedPassword)
      at Microsoft.Web.Services2.Security.Tokens.UsernameTokenManager.VerifyPassword(UsernameToken token, String authenticatedPassword)
      at Microsoft.Web.Services2.Security.Tokens.UsernameTokenManager.VerifyToken(SecurityToken securityToken)
      at Microsoft.Web.Services2.Security.Tokens.SecurityTokenManager.LoadXmlSecurityToken(XmlElement element)
      --- End of inner exception stack trace ---
      at Microsoft.Web.Services2.Security.Tokens.SecurityTokenManager.LoadXmlSecurityToken(XmlElement element)
      at Microsoft.Web.Services2.Security.Tokens.SecurityTokenManager.GetTokenFromXml(XmlElement element)
      at Microsoft.Web.Services2.Security.Security.LoadToken(XmlElement element, SecurityConfiguration configuration, Int32& tokenCount)
      at Microsoft.Web.Services2.Security.Security.LoadXml(XmlElement element)
      at Microsoft.Web.Services2.Security.SecurityInputFilter.ProcessMessage(SoapEnvelope envelope)
      at Microsoft.Web.Services2.Pipeline.ProcessInputMessage(SoapEnvelope envelope)
      at Microsoft.Web.Services2.WebServicesExtension.BeforeDeserializeServer(SoapServerMessage message)

      Source Error:

      An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

      Stack Trace:

      *[SoapHeaderException: Microsoft.Web.Services2.Security.SecurityFault: The security token could not be authenticated or authorized ---> System.Exception: WSE565: The password provided the SecurityTokenManager does not match the one on the incoming token.*
         *at Microsoft.Web.Services2.Security.Tokens.UsernameTokenManager.VerifyPlainTextPassword(UsernameToken token, String authenticatedPassword)*
         *at Microsoft.Web.Services2.Security.Tokens.UsernameTokenManager.VerifyPassword(UsernameToken token, String authenticatedPassword)*
         *at Microsoft.Web.Services2.Security.Tokens.UsernameTokenManager.VerifyToken(SecurityToken securityToken)*
         *at Microsoft.Web.Services2.Security.Tokens.SecurityTokenManager.LoadXmlSecurityToken(XmlElement element)*
         *--- End of inner exception stack trace ---*
         *at Microsoft.Web.Services2.Security.Tokens.SecurityTokenManager.LoadXmlSecurityToken(XmlElement element)*
         *at Microsoft.Web.Services2.Security.Tokens.SecurityTokenManager.GetTokenFromXml(XmlElement element)*
         *at Microsoft.Web.Services2.Security.Security.LoadToken(XmlElement element, SecurityConfiguration configuration, Int32& tokenCount)*
         *at Microsoft.Web.Services2.Security.Security.LoadXml(XmlElement element)*
         *at Microsoft.Web.Services2.Security.SecurityInputFilter.ProcessMessage(SoapEnvelope envelope)*
         *at Microsoft.Web.Services2.Pipeline.ProcessInputMessage(SoapEnvelope envelope)*
         *at Microsoft.Web.Services2.WebServicesExtension.BeforeDeserializeServer(SoapServerMessage message)]*
      System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) +431714
      System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) +204
      Xeno.Prodika.XenoDoc.Handlers.DRL.DrlService.GetAttachment(tIdentifier Identifier) +50
      Xeno.Prodika.XenoDoc.Handlers.DRL.DrlWebServiceLifecycleHandler.Load(IXDocument xdoc, String pkid) +151
      Xeno.Prodika.XenoDoc.BaseLibraryManager.LoadDocumentPhaseII(IXLibraryConfiguration libConfig, IXDocument xdoc, String pkid) +42
      Xeno.Prodika.XenoDoc.BaseLibraryManager.LoadDocument(String pkid) +18
      Xeno.Prodika.XenoDoc.XDocumentSystem.LoadDocument(String library, String pkid) +39
      Xeno.Prodika.XenoDoc.XDocService.LoadDocument(String library, String pkid) +24
      Xeno.Web.UI.Common.Controls.Popups.DRL.DrlAttachmentViewerPopup.OnLoad(EventArgs e) +320
      System.Web.UI.Control.LoadRecursive() +50
      System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
      --------------------------------------------------------------------------------

      this problem happened to anyone?
      Thanks.
        • 1. Re: Problem with DRL Attachment
          Trey
          You didnt say whether this is 6.1 or 6.0, but if 6.1, make sure the domain user you have set in SetupAssistant for DRL Service has access and is using the correct password to the file share where the files are stored.
          If 6.0 the user and password are in the environmentvaribales.config file.
          Hope that helps.
          --Trey                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           
          • 2. Re: Problem with DRL Attachment
            SinfoMichele
            Thanks Trey, problem solved. The password was not set in Setup assistant correctly.