Application server is valid, but elligence libraries cannot be accessed.

Since all users are having the same problem, it is most likely a problem with the server.

I'm going to have you go to the server and run a command that will re-configure the elligence libraries. (Normally I'd have you get everyone out of elligence first, but clearly that's not necessary right now.)

In order to do this, you'll have to be able to log onto the server directly, as an administrative user. If you don't know an administrative username and password to log onto the server directly, then please contact your local system administrator or support technician.

You may wish to print this page by pressing [Ctrl] P or by clicking the Print link above, so that you will have these instructions on hand at the server.

Before you start, make sure that you have the latest license information documentation that you received from your elligence dealer. If you do not have this information available, you may contact support and get it.

On the server:

• Double-click on My Computer, and navigate to your elligence installation path. By default, elligence is installed at

  C:\Program Files\DSI\elligence Application Server\

  If you installed elligence in the default location, then double-click on the C: drive, then on Program Files, then on DSI, and then on elligence Application Server.

• Double click on Website, and then on bin.

• Find the file called AppServerShell.exe. Double-click on this file.

• When you are asked for the name of your SQL database server, enter the computer's name where Microsoft SQL Server is running - not a user's name. If the server you are at is also your SQL Server, you may use the default value of (local).

• Enter a username and password with administrative access to the SQL Server. (This could be the SA Account .)

• AppServerShell will automatically update the IIS settings, as well as go through each database and make sure that it is properly configured.

  Important: If you see any error messages during this process, it is highly important that you make a note of them and report them to your elligence support technicians.

• When asked if you would like to change your license information, click Yes.

• You will be prompted for your license information. Make sure to enter everything exactly as it appears in your license documentation.

  Important: Do not alter your address, practice name, or serial number in any way. If the address is not correct, then you must still enter it exactly as it appears - you may however let us know that it is incorrect, and we will supply you with an updated license.

• The installer will ask if you plan on billing electronically to some specific EDI Destinations. Please see the elligence Dial-Up Networking Setup Guide for more information if you use any of these destinations.

• If you have multiple Application Servers , you may be asked which of them you would like to use as your Transmission Server. If you do not want to change your Transmission Server, then you may simply accept the default here.

  Please see the elligence Deployment Scenarios document for more information.

Try to log in again. Did that solve your problem?

• Thanks, that fixed it. I'd like to leave feedback on this process.
• It still doesn't work. I'd like to contact support.
• That fixed the problem, but I have to do this often. I'd like a support tech to figure out the source of the problem.

Since other users can log in without problems, I'd like you to confer with a user who can log in. Make sure that you and that other user are typing exactly the same thing into the Application Server field when you're logging in. If that doesn't match, please type that in now.

Once you're 100% sure that you and the other users are logging into the same Application Server, please choose the most appropriate option below:

• I was using the wrong Application Server name. When I use the same name as them, I can log in just fine.
• I was mistaken. Other users cannot log in, and are getting the same error message that I am.
• Other users cannot log in, but they are getting a different error message than I am.

• Thanks for solving the problem. I'd like to leave feedback on this process.
• This happens repeatedly. I'd like to have a Support Technician investigate the problem.

Please restart this troubleshooter, using the error messages that the other users are seeing.