You are currently offline, waiting for your internet to reconnect

Users Do Not Return to Your Site After They Sign In or a 'Page Not Found' Error Results

This article was previously published under Q302661
This article has been archived. It is offered "as is" and will no longer be updated.
Users do not return to your site after they sign in, or they receive a "Page Not Found" error message.
The Passport Login server URL and image link is generated by either the LogoTag2 or AuthURL2 method of the Passport Manager object. Your code must pass a return URL to the LogoTag2 or AuthURL2 method, and this return URL specifies where the user is redirected when authentication is complete.

To resolve this problem, check the following items:
  • Did you pass a return URL as the first parameter of the LogoTag2 or AuthURL2 method?

    If a return URL is not provided to the method, the default return URL that is specified using the Passport Manager Administration utility is used. If there is no default there, the DefaultReturnURL attribute that is specified in your site's registration information is used. If there is no default at all, the user is returned to Passport Member Services.
  • Did you include a fully qualified domain plus a file location for the return URL, rather than just a virtual directory root or an incomplete path?

    For example, works, whereas "../default.asp" as a return URL does not. Also, directory-only URLs such as, assuming a default exists at that root, can fail in some browsers after a redirect from Internet Information Server (IIS) version 4.0 servers.
  • Did you include the port number, if required, that you want users to return to after signing in as part of the return URL?

    The default port is 80.
  • Are you including no more than one query string variable on the return URL?

    Also, verify that the query string variable you are using is not one of the Passport reserved variables: "t", "p", and "f".
  • Did you remember to URL-encode the return URL correctly before passing it to the LogoTag2 or AuthURL2 method?

    The necessary encoding can be accomplished using the Server.URLEncode method on an ASP page.
  • Did you provide a DefaultReturnURL value when you registered your Web site with Passport?

    This URL is substituted by Passport server code if a return URL is missing from a Login server redirect that came from your site. The Site ID is always included with a method call and is used to look up your default return URL. The DefaultReturnURL should contain the full file path, including a file name.
  • Is the return URL that you supplied within the domain that you specified as your RootURL at registration time?

    All return URLs that you supply must fall within this root to prevent unscrupulous sites from spoofing your Site ID. For instance, if you specify "" as your RootURL value and try to give a return URL of "", the Passport Login server prevents the redirection and informs the user that something is incorrect about the configuration of your site.

    NOTE: The string that you give as RootURL when you register should not include protocol information (that is, don't include "http://"). While you are in test mode, any supplied return URL works, but does not return valid data.
  • Use the Passport Manager Administration utility to check your currently configured Site ID.

    If your Site ID and return URL / RootURL correlation don't match, users see a Passport network page informing them that something is wrong with the Site ID. The user is not returned to your site. You can also double-check the Site ID that is being provided to the Login server by reading the actual URL output of LogoTag2 or AuthURL2 methods; look for the id= query string parameter value in those URLs.

Article ID: 302661 - Last Review: 02/27/2014 21:09:15 - Revision: 3.0

Microsoft Passport 1.3, Microsoft Passport 1.4

  • kbnosurvey kbarchive kbprb KB302661