Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

I have .NET Framework installed, but ASP.NET does not work.

You must have IIS (Internet Information Services) installed before you install .NET Framework. If you install IIS after you install .NET Framework, you must also register the ASP.NET extensions with IIS. You can do this by running the aspnet_regiis executable from:

...

To check the .NET Framework version that you have installed, open Internet Information Services Manager > expand Web Sites > expand Default Web Site > right-click on the TimeTrackService virtual directory > select Properties > select the ASP.NET tab. Check the ASP.NET version drop-down menu.

Invalid Credentials Warning

When installing the Excel Timetrack Server, a new ODBC connection called WSES10 is created on your IIS server. The server name in this ODBC connection must match the ODBC connection name used through the rest of your organization exactly.

More Info: When a login is made in GP, it utilizes the server name in the ODBC connection to encrypt the password (with the exception of the "sa" account). For a client to utilize that password in GP, or in Excel TimeTrack, it must have the same ODBC server name.

In the case of Excel TimeTrack, it utilizes the ODBC WSES10 connection on the IIS server, not the ODBC connection on your local client or remote desktop.

If you have confirmed that usernames and passwords you are using are correct, you repeatedly get invalid credentials on multiple logins, but can also log in as "sa", confirm your WSES10 ODBC connection matches your other GP ODBC connections in your environment. If it still will not connect, in the second screen of the ODBC setup for WSES10, enter valid credentials to get additional configuration information from the SQL Server, test the connection, and try logging into Excel Timetrack again.