Regarding message level authentication in WSDL

Hi,
We developed scenario like below.
There is a consumer webservice interface which we developed through proxy class.
When we created the binding, selected 'Message level authentication' with 'Username and password' option.
But in the XML I couldn't see any tags asking for user name and password.
The requirement is to take the credentials through message header.
My queries are:
How do I edit the <sp:WssUsernameToken10 /> in XML to input username and password?
I tried to research and found out that IF_WSPROTOCOL_WS_HEADER can be used here but dont know where to call this in my code.
Also how this will validate the user name and password?
Or is there any other way to include username and password in the XML?
Please help as this is causing so much issues.

>
Anitha SAP wrote:
> Hi Rajesh,
>
>       I have to use only FTPS. Because my client is suggesting that only. Isn't possible using FTPS ?
> And Tell me The Difference Between FTPS for Control Connection and FTPS and Control and Data Connection .
> Neccesity of Public key certificate from FTP Sever?
>
> Thanks.
> Anitha.
PI supports FTPS. you can use the File adapter for the same.
The basic difference when we talk about FTPS for Control Connection* and FTPS and Control and Data Connection is that in case of FTPS and Control and Data Connection, you data is also encrypted. Else the connection is secure but the data level encryption will not be active
FTPS works with Certificates and hence the need for the same

Similar Messages

  • OSB message level authentication fault and predicate

    Hi,
    I have successfully configured MLS on my proxy service and it works fine.
    However, the fault thrown back by OSB does not give you much when authorization fails.
    Is it possible to get the predicate that has not been fulfilled? It would be more useful to the consumer of the service.
    Also, is it possible to at least trace/log the predicate on authorization failure?
    The logs contain the operation that failed but not the predicate
    \[OSB Security:386004\] Message-level access control denied access to proxy service Main/Proxy Service/LocalFundPS, operation findAllSchemes, subject: XXX
    Thanks
    Arnaud
    <faultcode>soapenv:Server</faultcode>
    <faultstring>
    BEA-386102: Message-level authorization denied
    </faultstring>
    <detail>
    <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
    <con:errorCode>BEA-386102</con:errorCode>
    <con:reason>Message-level authorization denied</con:reason>
    <con:location>
    <con:path>request-pipeline</con:path>
    </con:location>
    </con:fault>
    </detail>
    </soapenv:Fault>

    I have authentication providers configured as below (in the same order)
    Custom authenticatio provider - REQUIRED
    DefaultAutentication Provider - OPTIONAL
    I did configured message level authentication in proxy service for custom username/password token.
    Craeted a new user in weblogic console.
    Invoked proxy service with newly created username/password.
    I expect the user should not be authenticated since authetication with custom authentication provider will fail, which is required.
    I'm getting user authenticated and business service invoked and got a valid response.
    If i open another browser window and try to login with the weblogic admin password, it does not let me in because the user is not authenticated by my custom provider.
    Hope this makes scenario clear.

  • X509 message level authentication - Unable to validate identity assertions

    Hi All,
    I am creating a proxy service that will authenticate a soap request with incoming x509 certificate.
    I configured weblogic server following the below blog post
    http://tim.blackamber.org.uk/?p=831
    I also setup SSL and keystore tab in the weblogic server by following steps in the the below URL
    http://biemond.blogspot.com/2009/06/ws-security-in-osb.html
    In my proxy service I am using pre-defined policy "Auth.xml"
    The proxy service is attached below
    I am running the proxy service from test console. I have a security provider created pointing the keystore and selected while running the proxy service from test console ( no user name/password provided)
    I was expecting that proxy service will read the security token and map the CN name correspons to the security token key (my default User name mapper attribute is CN) to an user created in weblogic server and able to authenticate it.
    But I am getting following error. Please suggest.
    <An error ocurred during web service security inbound request processing [error-code: Fault, message-id: 1345281693794990467-5e61805e.1324a2f888f.-7f8a, proxy: myPrototypes/ProxyService/ProxyServiceExtBizV2, operation: null]
    --- Error message:
    <env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope"><env:Header/><env:Body><env:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><Code xmlns="http://www.w3.org/2003/05/soap-envelope"><Value>env:Sender</Value><Subcode><Value>wsse:InvalidSecurity</Value></Subcode></Code><Reason xmlns="http://www.w3.org/2003/05/soap-envelope"><Text xml:lang="en-US">Unable to validate identity assertions.</Text></Reason></env:Fault></env:Body></env:Envelope>
    weblogic.xml.crypto.wss.WSSecurityException: Unable to validate identity assertions.
    *     at weblogic.wsee.security.wss.SecurityPolicyValidator.doIdentity(SecurityPolicyValidator.java:144)*
    *     at weblogic.wsee.security.wss.SecurityPolicyValidator.processIdentity(SecurityPolicyValidator.java:107)*
         at weblogic.wsee.security.wss.SecurityPolicyValidator.processInbound(SecurityPolicyValidator.java:78)
         at weblogic.wsee.security.WssServerPolicyHandler.processInbound(WssServerPolicyHandler.java:54)
         at weblogic.wsee.security.WssServerPolicyHandler.processRequest(WssServerPolicyHandler.java:30)
         at weblogic.wsee.security.WssHandler.handleRequest(WssHandler.java:74)
         at com.bea.wli.sb.security.wss.wls.Wls92InboundHandler.processRequest(Wls92InboundHandler.java:164)
         at com.bea.wli.sb.security.wss.WssHandlerImpl.doInboundRequest(WssHandlerImpl.java:223)
         at com.bea.wli.sb.context.BindingLayerImpl.addRequest(BindingLayerImpl.java:289)
         at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:87)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
         at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:332)
         at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:79)
         at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:137)
         at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:135)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
    proxy service definition:
    <?xml version="1.0" encoding="UTF-8"?>
    <xml-fragment xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:env="http://www.bea.com/wli/config/env" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:con="http://www.bea.com/wli/sb/services/security/config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:con1="http://www.bea.com/wli/sb/pipeline/config" xmlns:con2="http://www.bea.com/wli/sb/stages/logging/config" xmlns:con3="http://www.bea.com/wli/sb/stages/config" xmlns:con4="http://www.bea.com/wli/sb/stages/publish/config">
    <ser:coreEntry isProxy="true" isEnabled="true">
    <ser:serviceProvider ref="myPrototypes/x509keyprovider"/>
    <ser:security>
    <con:inboundWss processWssHeader="true"/>
    </ser:security>
    <ser:binding type="abstract SOAP" isSoap12="true" xsi:type="con:AnySoapBindingType" xmlns:con="http://www.bea.com/wli/sb/services/bindings/config"/>
    <ser:monitoring isEnabled="false">
    <ser:aggregationInterval>10</ser:aggregationInterval>
    <ser:pipelineMonitoringLevel>Pipeline</ser:pipelineMonitoringLevel>
    </ser:monitoring>
    <ser:reporting>true</ser:reporting>
    <ser:logging isEnabled="true">
    <ser:logLevel>debug</ser:logLevel>
    </ser:logging>
    <ser:sla-alerting isEnabled="true">
    <ser:alertLevel>normal</ser:alertLevel>
    </ser:sla-alerting>
    <ser:pipeline-alerting isEnabled="true">
    <ser:alertLevel>normal</ser:alertLevel>
    </ser:pipeline-alerting>
    <ser:ws-policy>
    <ser:binding-mode>service-policy-bindings</ser:binding-mode>
    <ser:policies>
    <ser:service-policy>
    <ser:predefined-policy>Auth.xml</ser:predefined-policy>
    </ser:service-policy>
    </ser:policies>
    </ser:ws-policy>
    </ser:coreEntry>
    <ser:endpointConfig>
    <tran:provider-id>http</tran:provider-id>
    <tran:inbound>true</tran:inbound>
    <tran:URI>
    <env:value>/myPrototypes/ProxyService/ProxyServiceExtBizV2</env:value>
    </tran:URI>
    <tran:inbound-properties/>
    <tran:all-headers>true</tran:all-headers>
    <tran:provider-specific>
    <http:inbound-properties/>
    </tran:provider-specific>
    </ser:endpointConfig>
    <ser:router>
    <con1:pipeline type="request" name="PipelinePairNode1_request">
    <con1:stage name="stage1">
    <con1:context/>
    <con1:actions>
    <con2:log>
    <con3:id>_ActionId-3973507234039169612-4f70a750.1323cbeae66.-7e09</con3:id>
    <con2:logLevel>info</con2:logLevel>
    <con2:expr>
    <con3:xqueryText>$header</con3:xqueryText>
    </con2:expr>
    <con2:message>osb_extbiz_log:request side:hdr is</con2:message>
    </con2:log>
    <con4:route>
    <con3:id>_ActionId-3973507234039169612-4f70a750.1323cbeae66.-7866</con3:id>
    <con4:service ref="myPrototypes/BizService/BizServiceExtBiz" xsi:type="ref:BusinessServiceRef" xmlns:ref="http://www.bea.com/wli/sb/reference"/>
    <con4:outboundTransform/>
    </con4:route>
    </con1:actions>
    </con1:stage>
    </con1:pipeline>
    <con1:pipeline type="response" name="PipelinePairNode1_response">
    <con1:stage name="stage1">
    <con1:context/>
    <con1:actions>
    <con2:log>
    <con3:id>_ActionId-3973507234039169612-4f70a750.1323cbeae66.-7cd6</con3:id>
    <con2:logLevel>info</con2:logLevel>
    <con2:expr>
    <con3:xqueryText>$header</con3:xqueryText>
    </con2:expr>
    <con2:message>osb_extbiz_log:response side:hdr is</con2:message>
    </con2:log>
    <con2:log>
    <con3:id>_ActionId-3973507234039169612-4f70a750.1323cbeae66.-79d3</con3:id>
    <con2:logLevel>info</con2:logLevel>
    <con2:expr>
    <con3:xqueryText>$outbound</con3:xqueryText>
    </con2:expr>
    <con2:message>osb_extbiz_log:response side:outbound is</con2:message>
    </con2:log>
    <con2:log>
    <con3:id>_ActionId-3973507234039169612-4f70a750.1323cbeae66.-79b6</con3:id>
    <con2:logLevel>info</con2:logLevel>
    <con2:expr>
    <con3:xqueryText>$inbound</con3:xqueryText>
    </con2:expr>
    <con2:message>osb_extbiz_log:response side:inbound is</con2:message>
    </con2:log>
    </con1:actions>
    </con1:stage>
    </con1:pipeline>
    <con1:flow>
    <con1:pipeline-node name="PipelinePairNode1">
    <con1:request>PipelinePairNode1_request</con1:request>
    <con1:response>PipelinePairNode1_response</con1:response>
    </con1:pipeline-node>
    </con1:flow>
    </ser:router>
    </xml-fragment>
    Edited by: 818591 on Sep 8, 2011 4:47 PM

    For anyone watching this thread for any relevant information,
    after adding sign.xml policy, it started working

  • Message Level Security

    Hi All,
      In the PI to PI scenario i used certificates for sigining and encryption. For this i followed message level security document.
    In PI1 message is signed and encrypted, but the sign is not validated and message is not decrypted in PI2 server. Output from PI2 server is coming in  encrypted form. How to solve this issue.
    PI1 SP is 11 and PI2 SP is 06.
    Kindly suggest some solution.
    Regards
    Prakash

    Hi,
    Message-Level Security
    Message-level security allows you to digitally sign or encrypt documents exchanged between systems or business partners. It improves communication-level security by adding security features that are particularly important for inter-enterprise communication. Message-level security is recommended and sometimes a prerequisite for inter-enterprise communication.
    ●      A digital signature authenticates the business partner signing the message and ensures data integrity of the business document carried by a message.
    Signatures are used in two scenarios:
    ○       Non-repudiation of origin
    The sender signs a message so that the receiver can prove that the sender actually sent the message.
    ○       Non-repudiation of receipt
    The receiver signs a receipt message back to the sender so that the original sender can prove that the receiver actually received the original message.
    ●      Message-level encryption is required if message content needs to be confidential not only on the communication lines but also in intermediate message stores.
    SAP NetWeaver usage type Process Integration (PI) offers message-level security for the XI protocol itself, for the RosettaNet protocol, for the CIDX protocol, and for the SOAP and Mail adapters. The table below summarizes the message-level security features of these protocols and adapters.
    Message-Level Security Features
    XI Protocol (XI 3.0)
    Messaging components
    Integration Server and PCK
    SOAP
    Adapter Engine and PCK
    Mail
    Adapter Engine
    RNIF 2.0
    Adapter Engine
    RNIF1.1/CIDX
    Adapter Engine
    IIly
    Signature
    X
    X
    X
    X
    X
    Non-repudiation of origin
    X
    X
    (Web service security)
    X
    X
    Non-repudiation of receipt
    X
    X
    X
    Encryption
    X
    X
    X
    X
    Technology
    Web service security (XML signature)
    Signed parts are the SAP main header, the SAP manifest, and the payloads (SOAP attachments).
    Encrypted parts are the payloads (SOAP attachments).
    S/MIME or
    Web service security (XML signature)
    The SOAP body is signed.
    S/MIME
    S/MIME
    PKCS#7
    XI 3.0 is the XI protocol valid for both SAP NetWeaver ´04 and SAP NetWeaver 7.0.
    Message-level security is not guaranteed across the entire communication path of a message, but only for the intended B2B connections, which can be the following communication paths, as described under Service Users for Message Exchange.
    ●      XI protocol
    ○       (s4) Integration Server to Integration Server, PCK to Integration Server
    ○       (r4) Integration Server to Integration Server, Integration Server to PCK
    ●      SOAP protocol
    ○       (s3) SOAP sender to Adapter Engine or PCK
    ○       (r3) Adapter Engine or PCK to SOAP receiver
    ●      Mail protocols
    ○       (s3) Mail server to Adapter Engine or PCK (IMAP4/POP3)
    ○       (r3) Adapter Engine or PCK to mail server (IMAP4/SMTP)
    ●      RNIF and CIDX protocol
    ○       (s3) RNIF or CIDX sender to Adapter Engine
    ○       (r3) Adapter Engine to RNIF or CIDX receiver
    You define whether and how message-level security is to be applied to messages in the Integration Directory by using sender agreements on the inbound (sender) side in scenarios (s3) and (s4) and by using receiver agreements on the outbound (receiver) side in scenarios (r3) and (r4). For more information about configuring message-level security, see Security Configuration at Message Level.
    Message-level security relies on public and private x.509 certificates maintained in the J2EE keystore, where each certificate is identified by its alias name and the keystore view where it is stored. Certificates are used in the following situations:
    ●      When signing a message, the sender signs it with its private key and attaches its certificate containing the public key to the message.
    The receiver then verifies the digital signature of the message with the senderu2019s certificate attached to the message. There are two alternative trust models to verify the authenticity of the senderu2019s public certificate:
    ○       In the direct trust model, the signeru2019s public key certificate is compared with the locally maintained, expected public key certificate of the partner. Therefore, the direct trust model requires offline exchange of public key certificates, which can be self-signed or issued by a CA.
    ○       In the hierarchical trust model, the signeru2019s public key certificate is validated by a locally maintained public certificate of the CA that issued the signeru2019s public certificate. In addition, the subject name and the issuer of the signeru2019s certificate is compared with the expected partneru2019s identity configured in a receiver agreement on the receiver side.
    Generally, the hierarchical trust model enables chains of certificates attached to the message. The XI 3.0 message format, however, does not support such chains; the certificate used for signing has to be signed by a root CA.
    In the hierarchical trust model, the sender and the receiver only need to agree upon the CA and the subject name that the sender has used in its certificate.
    The following trust models are supported:
    ○       The RNIF and CIDX adapters support both a direct and a single-level hierarchical trust models.
    ○       The XI protocol and the SOAP adapter (with Web service security) only support a single-level hierarchical trust model.
    ○       The Mail adapter and the SOAP adapter (with S/MIME) support a multi-level hierarchical trust model.
    ●      When encrypting a message, the sender encrypts with the public key of the receiver (also verifying the correctness of the receiveru2019s certificate by using the public key of the certificateu2019s root CA).
    The receiver decrypts with its private key certificate.
    For more information about the certificate store, see Certificate Store.
    Whenever a message is signed, the receiver archives the signed messages for non-repudiation purposes. See Archiving Secured Messages.
    reg,
    suresh

  • Message Level Security in XI  7.0

    Hi,
    Have someone worked on Message level Security in XI 7.0 for transferring a file from one system to an external third party system?
    If so can u provide me with links or documents?
    Thanks
    Manjula

    Hi,
    Please Find the Required Details in the Links
    http://help.sap.com/saphelp_nw04/helpdata/en/f7/c2953fc405330ee10000000a114084/content.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d024ca8e-e76e-2910-c183-8ea4ba681c51
    Reward Points if Helpful
    Regards
    Khanna

  • SOAP receiver - Message level security - Encryption

    Hello,
    I want to use message level security when using HTTPS. Client provided us the encryption certificate which we have uploaded in the keystore, also done the necessary settings in PI 7.1 but we are getting the below mentioned error.
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: apply( Message, CPALookupObject ). Message: SecurityException in method: apply( Message, CPALookupObject ). WSSEThread-Exception: SecurityException in method: run(). Message: Connection timed out: connect. To-String: java.net.ConnectException: Connection timed out: connect; To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: run(). Message: Connection timed out: connect. To-String: java.net.ConnectException: Connection timed out: connect. To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: apply( Message, CPALookupObject ). WSSEThread-Exception: SecurityException in method: run(). Message: Connection timed out: connect. To-String: java.net.ConnectException: Connection timed out: connect; To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: run(). Message: Connection timed out: connect. To-String: java.net.ConnectException: Connection timed out: connect
    Thanks & Regards,
    Rahul Nawale

    I agree
    Try executing a Full CPA Cache refresh.

  • Configure Network Level Authentication for Remote Desktop client

    We publish Remote Desktop in our Windows 2008 R2 terminal server.
    However, in Windows 2008R2 , the remote desktop client will a lillte bit slow
    I found out that if I modify the setting in default.rdp
    authentication level:i:0
    enablecredsspsupport:i:0
    it will increase the speed a lot
    however, how can I set all user use remote desktop will disable those feature as well?
    Thanks

    Hi Kenneth, 
    I suggest you to see similar thread "disable
    Network Level Authentication Terminal Server 2008"
    If above thread does not helps, seek help from RDS/TS experts in here.
    Or wait until any of our moderator move this post to respective forum.
    Thank you for understanding.
    Regards, Ravikumar P

  • Message Level Security with SOAP Adapter

    Hi,
    I need to use Message Level Security with my SOAP Adapter. Please let me know if anyone has done the same in the past?
    What are the steps I would need to do? How can I use WSS based security in the SOAP Adapter?

    Hi,
    Message-level security is recommended and sometimes a prerequisite for inter-enterprise communication.
    It improves communication-level security by adding security features that are particularly important for inter-enterprise
    Message-level encryption is required if message content needs to be confidential not only on the communication lines but also in intermediate message stores.
    Refer
    How to use Client Authentication with SOAP Adapter
    XML Encryption Using Web Services Security in SAP NetWeaver XI
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0650f56-7587-2910-7c99-e1b6ffbe4d50
    http://help.sap.com/saphelp_nw04/helpdata/en/a8/882a40ce93185de10000000a1550b0/frameset.htm
    Thanks
    swarup

  • Jax-ws: Encrypt at message level, not using SSL

    Hello everyone,
    I have a non functional requisite that is very hard to accomplish. I have an architecture like the following: a Tomcat (web) that calls webservices that runs in a Weblogic or JBoss. The easiest solution for encrypting the communication I think is using SSL with an integration user (login/password).
    Well, the client wants the following: encrypt and sign the message at message level, not at transport level. I am using jax-ws as webservice technology.
    I am trying with Metro, but it is difficult to make it work in weblogic (and I suppose worse in JBoss).
    Any ideas?
    Thanks in advance.

    Hi David,
    Many thanks! I appear to have completely missed that artical while seaching for a solution.  I have run through the steps, and the replica appears to be using SSL OK, in as much I can connect to it using SSL.
    I have looked at the communication between the master & replica, and it appears that they are still using port 389 for comms, which surgests that replication traffic between the two servers is still unencrypted, which seems a little odd, again have I missed something?
    Regards
    Matt

  • Message Level Security and Performance

    Hi All,
    Does the implementation of Message Level security features Like SSL and Encryption degrade the performance of the server in Processing the messages ?
    regards,
    Rahul

    Encryption related performance issue is purely related to size of messages.
    In my opinion, SSL wouldnt affect the performance for large messages. SSL will take its usual time for checking for security.
    And the volume and size could anytime affect the performance
    Regards,
    Prateek

  • NLA Disabled. Still can't RDP; "requires Network Level Authentication"

    Had a server I could RDP onto without any issue running Hyper V.
    I removed the Hyper V role.
    I then rebooted and attempted to RDP onto the server and can't:
    The remote computer that you are trying to connect to requires Network Level Authentication (NLA), but your Windows domain controller cannot be contacted to perform NLA. If you are an administrator on the remote computer, you can disable NLA by using
    the options on the Remote tab of the System Properties dialog box.
    OK... Never needed before.
    I checked the network settings remotely with netsh and confirmed correct DC as DNS. So I'm scratching my head why Microsoft are lying to me?
    OK, so I check the NLA settings remotely, sure enough is enabled. So I disabled via remote registry, reboot the machine, confirm the registry is set to NLA disabled again remotely and attempt to connect.
    And... Same message.
    I can access any other of the 2012 R2 servers on my domain without issue. I can open AD or any other Domain tools from other servers with the same DC as the problem server as their primary DNS.
    How can I get that message when both the DC is contactable and NLA is disabled?
    How did removing a role cause this BS suddenly?

    Hi,
    Thank you for posting in Windows Server Forum.
    Which version of client RDP you are using?
    You can use RDP v8.1 for better performance.
    Apart from above, Use local admin account to log on to the virtual machine and set the DNS to point to your DC. Alternatively, assign the IP address of the DC/DNS under DNS servers of virtual network.
    Also when trying to remote desktop check the option “Allow connection from computers running any version of Remote desktop (less secure)” under system properties.
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • Event code: 4005 Event message: Forms authentication failed for the request. Reason: The ticket supplied was invalid.

    When i was run my web application in everyday morning(after that issue was not reproduced), it was immediatly redirected to logout page
     while i perform any task after login.Session_end function was called unfortunately.
    Event log as follows 
    Event code: 4005 
    Event message: Forms authentication failed for the request. Reason: The ticket supplied was invalid. 
    Event time: 10/10/2014 10:36:33 AM 
    Event time (UTC): 10/10/2014 5:06:33 AM 
    Event ID: a268f3dd45da406dadd78773a858067f 
    Event sequence: 4 
    Event occurrence: 1 
    Event detail code: 50201 
    Application information: 
        Application domain: 463c736b-2-130573911817035712 
        Trust level: Full
    The output while session_end() was called is as follows
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_32\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\Program Files\Common Files\Microsoft Shared\DevServer\11.0\WebDev.WebServer40.exe'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_32\WebDev.WebHost40\v4.0_11.0.0.0__b03f5f7f11d50a3a\WebDev.WebHost40.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_32\System.Web\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Caching\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Runtime.Caching.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Build.Utilities.v4.0\v4.0_4.0.0.0__b03f5f7f11d50a3a\Microsoft.Build.Utilities.v4.0.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.JScript\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.JScript.dll'
    A first chance exception of type 'System.ArgumentNullException' occurred in System.Core.dll
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.CSharp\v4.0_4.0.0.0__b03f5f7f11d50a3a\Microsoft.CSharp.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_32\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Services\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_32\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.IdentityModel\v4.0_4.0.0.0__b77a5c561934e089\System.IdentityModel.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel\v4.0_4.0.0.0__b77a5c561934e089\System.ServiceModel.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Activation\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Activation.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Web\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Web.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Activities\v4.0_4.0.0.0__31bf3856ad364e35\System.Activities.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Activities\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Activities.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.WorkflowServices\v4.0_4.0.0.0__31bf3856ad364e35\System.WorkflowServices.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Extensions\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.Extensions.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Data.DataSetExtensions\v4.0_4.0.0.0__b77a5c561934e089\System.Data.DataSetExtensions.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml.Linq\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.Linq.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.ComponentModel.DataAnnotations\v4.0_4.0.0.0__31bf3856ad364e35\System.ComponentModel.DataAnnotations.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.DynamicData\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.DynamicData.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.ApplicationServices\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.ApplicationServices.dll'
    WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\myapp\8b99fcaa\690ad76d\assembly\dl3\d2ac696f\807ca1a9_01cccf01\AjaxControlToolkit.dll'
    WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\myapp\8b99fcaa\690ad76d\assembly\dl3\0ff769a3\738a1ab9_47e4cf01\myapp.dll', Symbols loaded.
    WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\myapp\8b99fcaa\690ad76d\assembly\dl3\48c5da56\c38dd5b4_47e4cf01\WPCSCore.dll', Symbols loaded.
    WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\myapp\8b99fcaa\690ad76d\assembly\dl3\1c6f45a6\dd41c2e2_8ed8cf01\wpcsLibrary.dll', Symbols loaded.
    WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\myapp\8b99fcaa\690ad76d\assembly\dl3\6a813290\35d3aedf_8ed8cf01\WPWebControls.dll', Symbols loaded.
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Web.PageInspector.Loader\v4.0_1.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Web.PageInspector.Loader.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.WebPages.Deployment\v4.0_1.0.0.0__31bf3856ad364e35\System.Web.WebPages.Deployment.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.WebPages.Deployment\v4.0_2.0.0.0__31bf3856ad364e35\System.Web.WebPages.Deployment.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Xaml\v4.0_4.0.0.0__b77a5c561934e089\System.Xaml.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Web.PageInspector.Runtime\v4.0_1.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Web.PageInspector.Runtime.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Web.Infrastructure\v4.0_1.0.0.0__31bf3856ad364e35\Microsoft.Web.Infrastructure.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.RegularExpressions\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.RegularExpressions.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_32\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.Wrapper.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Data.Services.Design\v4.0_4.0.0.0__b77a5c561934e089\System.Data.Services.Design.dll'
    WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\myapp\8b99fcaa\690ad76d\App_global.asax.3ly5lssc.dll', Symbols loaded.
    A first chance exception of type 'System.Threading.ThreadAbortException' occurred in mscorlib.dll
    A first chance exception of type 'System.Threading.ThreadAbortException' occurred in mscorlib.dll
    A first chance exception of type 'System.Threading.ThreadAbortException' occurred in System.Web.dll
    A first chance exception of type 'System.Threading.ThreadAbortException' occurred in mscorlib.dll
    'iexplore.exe' (Script): Loaded 'Script Code (Windows Internet Explorer)'.
    The thread '<No Name>' (0x2178) has exited with code 0 (0x0).
    The thread '<No Name>' (0x22c0) has exited with code 0 (0x0).
    The thread '<No Name>' (0x3c4) has exited with code 0 (0x0).
    The thread '<No Name>' (0x2198) has exited with code 0 (0x0).
    The thread '<No Name>' (0x19e0) has exited with code 0 (0x0).
    The thread '<No Name>' (0x21c8) has exited with code 0 (0x0).
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.JScript\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.JScript.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Web.PageInspector.Loader\v4.0_1.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Web.PageInspector.Loader.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.WebPages.Deployment\v4.0_1.0.0.0__31bf3856ad364e35\System.Web.WebPages.Deployment.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.WebPages.Deployment\v4.0_2.0.0.0__31bf3856ad364e35\System.Web.WebPages.Deployment.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Web.PageInspector.Runtime\v4.0_1.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Web.PageInspector.Runtime.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Web.Infrastructure\v4.0_1.0.0.0__31bf3856ad364e35\Microsoft.Web.Infrastructure.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.CSharp\v4.0_4.0.0.0__b03f5f7f11d50a3a\Microsoft.CSharp.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_32\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Services\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_32\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.IdentityModel\v4.0_4.0.0.0__b77a5c561934e089\System.IdentityModel.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel\v4.0_4.0.0.0__b77a5c561934e089\System.ServiceModel.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Activation\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Activation.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Web\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Web.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Activities\v4.0_4.0.0.0__31bf3856ad364e35\System.Activities.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Activities\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Activities.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.WorkflowServices\v4.0_4.0.0.0__31bf3856ad364e35\System.WorkflowServices.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Extensions\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.Extensions.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Data.DataSetExtensions\v4.0_4.0.0.0__b77a5c561934e089\System.Data.DataSetExtensions.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml.Linq\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.Linq.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.ComponentModel.DataAnnotations\v4.0_4.0.0.0__31bf3856ad364e35\System.ComponentModel.DataAnnotations.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.DynamicData\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.DynamicData.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.ApplicationServices\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.ApplicationServices.dll'
    WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\myapp\8b99fcaa\690ad76d\assembly\dl3\d2ac696f\807ca1a9_01cccf01\AjaxControlToolkit.dll'
    WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\myapp\8b99fcaa\690ad76d\assembly\dl3\0ff769a3\738a1ab9_47e4cf01\myapp.dll', Symbols loaded.
    WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\myapp\8b99fcaa\690ad76d\assembly\dl3\48c5da56\c38dd5b4_47e4cf01\WPCSCore.dll', Symbols loaded.
    WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\myapp\8b99fcaa\690ad76d\assembly\dl3\1c6f45a6\dd41c2e2_8ed8cf01\wpcsLibrary.dll', Symbols loaded.
    WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\myapp\8b99fcaa\690ad76d\assembly\dl3\6a813290\35d3aedf_8ed8cf01\WPWebControls.dll', Symbols loaded.
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Data.Services.Design\v4.0_4.0.0.0__b77a5c561934e089\System.Data.Services.Design.dll'
    WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\myapp\8b99fcaa\690ad76d\App_global.asax.yz9nltrj.dll', Symbols loaded.
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualBasic\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualBasic.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Deployment\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Deployment.dll'
    A first chance exception of type 'System.Deployment.Application.InvalidDeploymentException' occurred in System.Deployment.dll
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_32\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_32\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.Wrapper.dll'
    WebDev.WebServer40.exe Information: 0 : [Source : ASP.global_asax ] - <No Message>
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Mobile\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.Mobile.dll'
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Internals\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Internals.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\SMDiagnostics\v4.0_4.0.0.0__b77a5c561934e089\SMDiagnostics.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Xaml.Hosting\v4.0_4.0.0.0__31bf3856ad364e35\System.Xaml.Hosting.dll'
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Entity\v4.0_4.0.0.0__b77a5c561934e089\System.Web.Entity.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Design\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Design.dll'
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'A_7ac34899_0878_4547_ab89_13333f2a2da8'
    WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\myapp\8b99fcaa\690ad76d\App_Web_2vnmaiqi.dll', Symbols loaded.
    WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\myapp\8b99fcaa\690ad76d\App_Web_axfwmnjt.dll', Symbols loaded.
    WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\myapp\8b99fcaa\690ad76d\assembly\dl3\a9a217f9\93d383b9_47e4cf01\myapp.resources.dll'
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    The thread '<No Name>' (0x230c) has exited with code 0 (0x0).
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    Exception was thrown at line 3, column 25599 in http://localhost:51399/myapp/public/jquery-1.7.2.min.js
    0x800a139e - JavaScript runtime error: SyntaxError
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    A first chance exception of type 'System.Web.HttpException' occurred in System.Web.dll
    The thread '<No Name>' (0x258c) has exited with code 0 (0x0).
    WebDev.WebServer40.exe Information: 0 : [Source : ASP.login_aspx ] - <No Message>
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Diagnostics.ServiceModelSink\v4.0_4.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Diagnostics.ServiceModelSink.dll'
    WebDev.WebServer40.exe Information: 0 : [Source : wpcsLibrary.wpcsUserManager.UserAuthenticate ] - <No Message>
    A first chance exception of type 'System.IO.IOException' occurred in mscorlib.dll
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Net.Http\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Net.Http.dll'
    WebDev.WebServer40.exe Information: 0 : [Source : ] - <No Message>
    A first chance exception of type 'System.Threading.ThreadAbortException' occurred in mscorlib.dll
    WebDev.WebServer40.exe Information: 0 : Entering method call dbUtilities
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Numerics\v4.0_4.0.0.0__b77a5c561934e089\System.Numerics.dll'
    WebDev.WebServer40.exe Information: 0 : [Source :dbUtilities ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : Exiting method call dbUtilities
    WebDev.WebServer40.exe Information: 0 : [Source : ASP.accountselector_aspx ] - <No Message>
    The thread '<No Name>' (0x24dc) has exited with code 0 (0x0).
    WebDev.WebServer40.exe Information: 0 : [Source : ASP.accountselector_aspx ] - <No Message>
    A first chance exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.dll
    A first chance exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.dll
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'Microsoft.GeneratedCode'
    A first chance exception of type 'System.Threading.ThreadAbortException' occurred in mscorlib.dll
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Xaml\v4.0_4.0.0.0__b77a5c561934e089\System.Xaml.dll'
    WebDev.WebServer40.exe Information: 0 : Entering method call myweb.CentralStation.Apps.AppManager
    WebDev.WebServer40.exe Information: 0 : [Source : myweb.CentralStation.Apps.AppManager ] - <No Message>
    The thread '<No Name>' (0x2590) has exited with code 0 (0x0).
    WebDev.WebServer40.exe Information: 0 : Entering method call myweb.CentralStation.Apps.AppManager
    WebDev.WebServer40.exe Information: 0 : [Source : myweb.CentralStation.Apps.AppManager ] - <No Message>
    WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'C:\Users\E849324\myweb\Finalview\NCI\Source\WIN-PAK 2.0 R5\SourceCode\WPCSWEB\myapp\bin\DoorApp.app', Symbols loaded.
    WebDev.WebServer40.exe Information: 0 : Entering method call myweb.CentralStation.Apps.AppManager
    WebDev.WebServer40.exe Information: 0 : [Source : myweb.CentralStation.Apps.AppManager ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : Exiting method call myweb.CentralStation.Apps.AppManager
    WebDev.WebServer40.exe Information: 0 : Exiting method call myweb.CentralStation.Apps.AppManager
    WebDev.WebServer40.exe Information: 0 : Exiting method call myweb.CentralStation.Apps.AppManager
    The thread '<No Name>' (0x1f04) has exited with code 0 (0x0).
    Step into: Stepping over method without symbols 'System.Threading.ExecutionContext.Reader.IllogicalCallContext.get'
    Step into: Stepping over method without symbols 'System.Runtime.Remoting.Messaging.CallContext.HostContext.get'
    Step into: Stepping over method without symbols 'System.Web.HttpContext.Application.get'
    Step into: Stepping over method without symbols 'System.Web.HttpApplicationState.this[string].get'
    Step into: Stepping over method without symbols 'System.Threading.ExecutionContext.Reader.IllogicalCallContext.get'
    Step into: Stepping over method without symbols 'System.Runtime.Remoting.Messaging.CallContext.HostContext.get'
    Step into: Stepping over method without symbols 'System.Web.HttpContext.Application.get'
    Step into: Stepping over method without symbols 'System.Web.HttpApplicationState.this[string].get'
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : Entering method call wpcsLibrary.wpcsDataManager.dbUtilities
    WebDev.WebServer40.exe Information: 0 : Exiting method call wpcsLibrary.wpcsDataManager.dbUtilities
    Step into: Stepping over property 'myweb.CentralStation.Apps.AppManager.Instance.get'. To step into properties, go to Tools->Options->Debugging and uncheck 'Step over properties and operators (Managed only)'.
    Step into: Stepping over method without symbols 'System.Threading.ExecutionContext.Reader.IllogicalCallContext.get'
    Step into: Stepping over method without symbols 'System.Runtime.Remoting.Messaging.CallContext.HostContext.get'
    Step into: Stepping over method without symbols 'System.Web.HttpContext.Application.get'
    Step into: Stepping over method without symbols 'System.Web.HttpApplicationState.this[string].get'
    Step into: Stepping over method without symbols 'System.Threading.ExecutionContext.Reader.IllogicalCallContext.get'
    Step into: Stepping over method without symbols 'System.Runtime.Remoting.Messaging.CallContext.HostContext.get'
    Step into: Stepping over method without symbols 'System.Web.HttpContext.Application.get'
    Step into: Stepping over method without symbols 'System.Web.HttpApplicationState.this[string].get'
    Step into: Stepping over property 'myweb.CentralStation.Apps.AppManager.Canvas.set'. To step into properties, go to Tools->Options->Debugging and uncheck 'Step over properties and operators (Managed only)'.
    The thread '<No Name>' (0x26c0) has exited with code 0 (0x0).
    Step into: Stepping over method without symbols 'string.Concat'
    Step into: Stepping over method without symbols 'System.Diagnostics.Trace.TraceInformation'
    WebDev.WebServer40.exe Information: 0 : Entering method call myweb.CentralStation.Apps.AppManager
    Step into: Stepping over property 'myweb.CentralStation.Apps.AppManager.Canvas.get'. To step into properties, go to Tools->Options->Debugging and uncheck 'Step over properties and operators (Managed only)'.
    Step into: Stepping over method without symbols 'System.Web.UI.Control.Controls.get'
    Step into: Stepping over method without symbols 'System.Web.UI.ControlCollection.Clear'
    Step into: Stepping over method without symbols 'System.Threading.ExecutionContext.Reader.IllogicalCallContext.get'
    Step into: Stepping over method without symbols 'System.Runtime.Remoting.Messaging.CallContext.HostContext.get'
    Step into: Stepping over method without symbols 'System.Web.HttpContext.Application.get'
    Step into: Stepping over method without symbols 'System.Web.HttpApplicationState.this[string].get'
    Step into: Stepping over method without symbols 'System.Collections.Generic.List<System.Web.UI.WebControls.Panel>.List'
    Step into: Stepping over property 'myweb.CentralStation.Apps.AppManager.InstalledApps.get'. To step into properties, go to Tools->Options->Debugging and uncheck 'Step over properties and operators (Managed only)'.
    Step into: Stepping over method without symbols 'System.Threading.ExecutionContext.Reader.IllogicalCallContext.get'
    Step into: Stepping over method without symbols 'System.Runtime.Remoting.Messaging.CallContext.HostContext.get'
    Step into: Stepping over method without symbols 'System.Web.HttpContext.Application.get'
    Step into: Stepping over method without symbols 'System.Web.HttpApplicationState.this[string].get'
    Step into: Stepping over method without symbols 'System.Threading.ExecutionContext.Reader.IllogicalCallContext.get'
    Step into: Stepping over method without symbols 'System.Runtime.Remoting.Messaging.CallContext.HostContext.get'
    Step into: Stepping over method without symbols 'System.Web.HttpContext.Application.get'
    Step into: Stepping over method without symbols 'System.Web.HttpApplicationState.this[string].get'
    Step into: Stepping over method without symbols 'string.Concat'
    Step into: Stepping over method without symbols 'System.Diagnostics.Trace.TraceInformation'
    WebDev.WebServer40.exe Information: 0 : Entering method call myweb.CentralStation.Apps.AppManager
    Step into: Stepping over method without symbols 'System.Web.UI.WebControls.Panel.Panel'
    Step into: Stepping over method without symbols 'System.Web.UI.WebControls.WebControl.CssClass.set'
    Step into: Stepping over method without symbols 'System.Web.UI.WebControls.Panel.Panel'
    Step into: Stepping over method without symbols 'System.Web.UI.WebControls.WebControl.CssClass.set'
    Step into: Stepping over method without symbols 'System.Web.UI.WebControls.Panel.Panel'
    Step into: Stepping over method without symbols 'System.Web.UI.WebControls.WebControl.CssClass.set'
    Step into: Stepping over method without symbols 'System.Web.UI.Control.Controls.get'
    Step into: Stepping over method without symbols 'System.Web.UI.ControlCollection.Add'
    Step into: Stepping over method without symbols 'myweb.CentralStation.Apps.App.AppInfo.get'
    Step into: Stepping over method without symbols 'myweb.CentralStation.Apps.AppAttribute.IconImage.get'
    Step into: Stepping over method without symbols 'string.IsNullOrEmpty'
    Step into: Stepping over method without symbols 'System.Web.UI.WebControls.Label.Label'
    Step into: Stepping over method without symbols 'myweb.CentralStation.Apps.App.AppInfo.get'
    Step into: Stepping over method without symbols 'myweb.CentralStation.Apps.AppAttribute.Name.get'
    Step into: Stepping over method without symbols 'System.Web.UI.WebControls.Label.Text.set'
    Step into: Stepping over method without symbols 'myweb.CentralStation.Apps.App.AppInfo.get'
    Step into: Stepping over method without symbols 'myweb.CentralStation.Apps.AppAttribute.Description.get'
    Step into: Stepping over method without symbols 'System.Web.UI.WebControls.WebControl.ToolTip.set'
    Step into: Stepping over method without symbols 'System.Web.UI.Control.Controls.get'
    Step into: Stepping over method without symbols 'System.Web.UI.ControlCollection.Add'
    Step into: Stepping over method without symbols 'System.Web.UI.Control.Controls.get'
    Step into: Stepping over method without symbols 'System.Web.UI.ControlCollection.Add'
    Step into: Stepping over method without symbols 'System.Web.UI.Control.Controls.get'
    Step into: Stepping over method without symbols 'System.Web.UI.ControlCollection.Add'
    Step into: Stepping over property 'myweb.CentralStation.Apps.AppManager.Canvas.get'. To step into properties, go to Tools->Options->Debugging and uncheck 'Step over properties and operators (Managed only)'.
    Step into: Stepping over method without symbols 'System.Web.UI.Control.Controls.get'
    Step into: Stepping over method without symbols 'System.Web.UI.ControlCollection.Add'
    Step into: Stepping over method without symbols 'string.Concat'
    Step into: Stepping over method without symbols 'System.Diagnostics.Trace.TraceInformation'
    WebDev.WebServer40.exe Information: 0 : Exiting method call myweb.CentralStation.Apps.AppManager
    Step into: Stepping over method without symbols 'System.Collections.Generic.List<System.Web.UI.WebControls.Panel>.Add'
    Step into: Stepping over method without symbols 'System.Threading.ExecutionContext.Reader.IllogicalCallContext.get'
    Step into: Stepping over method without symbols 'System.Runtime.Remoting.Messaging.CallContext.HostContext.get'
    Step into: Stepping over method without symbols 'System.Web.HttpContext.Application.get'
    Step into: Stepping over method without symbols 'System.Collections.Generic.List<System.Web.UI.WebControls.Panel>.ToArray'
    Step into: Stepping over method without symbols 'System.Web.HttpApplicationState.this[string].set'
    Step into: Stepping over method without symbols 'System.Threading.ExecutionContext.Reader.IllogicalCallContext.get'
    Step into: Stepping over method without symbols 'System.Runtime.Remoting.Messaging.CallContext.HostContext.get'
    Step into: Stepping over method without symbols 'System.Web.HttpContext.Application.get'
    Step into: Stepping over method without symbols 'System.Web.HttpApplicationState.this[string].get'
    Step into: Stepping over property 'myweb.CentralStation.Apps.AppManager.Canvas.get'. To step into properties, go to Tools->Options->Debugging and uncheck 'Step over properties and operators (Managed only)'.
    Step into: Stepping over method without symbols 'System.Web.UI.Control.Controls.get'
    Step into: Stepping over method without symbols 'System.Web.UI.ControlCollection.Add'
    Step into: Stepping over method without symbols 'string.Concat'
    Step into: Stepping over method without symbols 'System.Diagnostics.Trace.TraceInformation'
    WebDev.WebServer40.exe Information: 0 : Exiting method call myweb.CentralStation.Apps.AppManager
    Step into: Stepping over property 'myweb.CentralStation.Apps.AppManager.InstalledApps.get'. To step into properties, go to Tools->Options->Debugging and uncheck 'Step over properties and operators (Managed only)'.
    Step into: Stepping over method without symbols 'System.Threading.ExecutionContext.Reader.IllogicalCallContext.get'
    Step into: Stepping over method without symbols 'System.Runtime.Remoting.Messaging.CallContext.HostContext.get'
    Step into: Stepping over method without symbols 'System.Web.HttpContext.Application.get'
    Step into: Stepping over method without symbols 'System.Web.HttpApplicationState.this[string].get'
    Step into: Stepping over method without symbols 'System.Threading.ExecutionContext.Reader.IllogicalCallContext.get'
    Step into: Stepping over method without symbols 'System.Runtime.Remoting.Messaging.CallContext.HostContext.get'
    Step into: Stepping over method without symbols 'System.Web.HttpContext.Application.get'
    Step into: Stepping over method without symbols 'System.Web.HttpApplicationState.this[string].get'
    Step into: Stepping over property 'myweb.CentralStation.Apps.AppManager.InstalledApps.get'. To step into properties, go to Tools->Options->Debugging and uncheck 'Step over properties and operators (Managed only)'.
    Step into: Stepping over method without symbols 'System.Threading.ExecutionContext.Reader.IllogicalCallContext.get'
    Step into: Stepping over method without symbols 'System.Runtime.Remoting.Messaging.CallContext.HostContext.get'
    Step into: Stepping over method without symbols 'System.Web.HttpContext.Application.get'
    Step into: Stepping over method without symbols 'System.Web.HttpApplicationState.this[string].get'
    Step into: Stepping over method without symbols 'System.Threading.ExecutionContext.Reader.IllogicalCallContext.get'
    Step into: Stepping over method without symbols 'System.Runtime.Remoting.Messaging.CallContext.HostContext.get'
    Step into: Stepping over method without symbols 'System.Web.HttpContext.Application.get'
    Step into: Stepping over method without symbols 'System.Web.HttpApplicationState.this[string].get'
    Step into: Stepping over method without symbols 'System.Web.UI.HtmlControls.HtmlControl.Style.get'
    Step into: Stepping over method without symbols 'System.AppDomain.Flags.get'
    Step into: Stepping over method without symbols 'string.Concat'
    Step into: Stepping over method without symbols 'System.Web.UI.CssStyleCollection.Add'
    The thread '<No Name>' (0x1b04) has exited with code 0 (0x0).
    WebDev.WebServer40.exe Information: 0 : Entering method call ASP.site_master
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : [Source : System.Byte[] ] - <No Message>
    WebDev.WebServer40.exe Information: 0 : Entering method call wpcsLibrary.wpcsDataManager.dbUtilities
    WebDev.WebServer40.exe Information: 0 : Exiting method call wpcsLibrary.wpcsDataManager.dbUtilities
    WebDev.WebServer40.exe Information: 0 : Exiting method call ASP.site_master
    A first chance exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.dll
    A first chance exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.dll
    'WebDev.WebServer40.EXE' (Managed (v4.0.30319)): Loaded 'Microsoft.GeneratedCode'

    Please post this question to the forums at http://www.asp.net.
    Matt Small - Microsoft Escalation Engineer - Forum Moderator
    If my reply answers your question, please mark this post as answered.
    NOTE: If I ask for code, please provide something that I can drop directly into a project and run (including XAML), or an actual application project. I'm trying to help a lot of people, so I don't have time to figure out weird snippets with undefined
    objects and unknown namespaces.

  • WebServices and message level security

    Hello,
    I am investigating about the use of XI web services using message level security (encrypted xml), is it possible to achieve this between an SAP provider and a third party consumer, without using a PCK or developing a specific adapter? (most solutions I see always point to this).
    If anyone could shed some light into this matter i would be thankful.
    Regards,
    Leandro Fonseca

    Hello,
    I am investigating about the use of XI web services using message level security (encrypted xml), is it possible to achieve this between an SAP provider and a third party consumer, without using a PCK or developing a specific adapter? (most solutions I see always point to this).
    If anyone could shed some light into this matter i would be thankful.
    Regards,
    Leandro Fonseca

  • Message Level Security in FTPS

    Hi ,
       Did File Adapter with FTPS will provide the Message Level Security ?
    And What is the Exact  Difference Between FTPS for Control Connection and FTPS for Control and Data Connection .
    What is the Significance of Use X.509 Certificate for Client Authentication check box. If we check it what will happen r if we dont what will happen ?
    Thanks.
    Anitha.

    >
    Anitha SAP wrote:
    > Hi Rajesh,
    >
    >       I have to use only FTPS. Because my client is suggesting that only. Isn't possible using FTPS ?
    > And Tell me The Difference Between FTPS for Control Connection and FTPS and Control and Data Connection .
    > Neccesity of Public key certificate from FTP Sever?
    >
    > Thanks.
    > Anitha.
    PI supports FTPS. you can use the File adapter for the same.
    The basic difference when we talk about FTPS for Control Connection* and FTPS and Control and Data Connection is that in case of FTPS and Control and Data Connection, you data is also encrypted. Else the connection is secure but the data level encryption will not be active
    FTPS works with Certificates and hence the need for the same

  • Regarding Messages to Job Log

    Hi,
    What is a Job Log.
    i have to write messages to job log.
    how to do this.
    how can i see that messages whether it is written or not.
    how it can be seen to the client/user.
    regards,
    kiran

    Hi Kiran
    Use 'write' to display the message in the job log.
    write : / log_message.
    Place this statement after the block of statements in your program where you want the message to be displayed in the log.
    You can see the job log in SM37 transaction.
    hope this helps you.
    regards
    Message was edited by:
            Sarah Bollavaram
    Message was edited by:
            Sarah Bollavaram

Maybe you are looking for