Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 2 of 2

Thread: WSI crazyness

  1. #1
    MikeSaunders is offline Member
    Join Date
    Feb 2013
    Location
    Cardiff UK
    Posts
    37

    Question WSI crazyness

    We are going around in circles with the WSI service we have source code version and non source version of the store using the same web.config file

    with the non source version WSI runs fine

    if we try to run WSI on the source version we get config errors even though we are using the same web.config file ?

    This is the error
    Code:
     --- End of inner exception stack trace ---
     --- End of inner exception stack trace ---
    L data error - System.Web.Services.Protocols.SoapHeaderException: Server unavailable, please try later ---> System.ApplicationException: WSE842: The service pipeline could not be created. ---> Syste
    Configuration.ConfigurationErrorsException: WSE032: There was an error loading the microsoft.web.services3 configuration section. ---> System.Configuration.ConfigurationErrorsException: WSE040: Type
    spDotNetStorefront.ASPDNSFUsernameTokenManager could not be loaded. Please check the configuration file. (D:\vhosts\fastpartswales.co.uk\storefront\web.config line 293)
    the error relates to the following line

    Code:
    <microsoft.web.services3>
        <security>
            <securityTokenManager>
              <add type="AspDotNetStorefront.ASPDNSFUsernameTokenManager" namespace="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" localName="UsernameToken" />
            </securityTokenManager>
          </security>
      </microsoft.web.services3>

    Anyone know what might be the cause of this is there anything different in the source version of the store compared to the non source version (other than the obvious) ?

  2. #2
    MikeSaunders is offline Member
    Join Date
    Feb 2013
    Location
    Cardiff UK
    Posts
    37

    Default

    I commented out that section and it seems to work ??