Have you gone through the Quick Start Guide?

There appears to be an error with the administrator password too.

Yes, I did everything according to the guide - prerequisites, etc.  I have admin rights to the server where it's installed, but I didn't install it under the administrator account.  I can't ask them to change the password for their domain admin.  What next?

Dane, have you setup the database?

Try also checking either the System or Application event logs, and these may provide additional information.

Yes, I set up the database.  Everything in the Admin console appears correct.

Dane, are there any errors in the Windows Event Logs?

I found this.  I don't know how/where to fix it.

An account failed to log on.An account failed to log on.
Subject: Security ID: IIS APPPOOL\IMan Account Name: IMan Account Domain: IIS APPPOOL Logon ID: 0x870FC
Logon Type: 8
Account For Which Logon Failed: Security ID: NULL SID Account Name: administrator Account Domain: bfd
Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xC000006D Sub Status: 0xC000006A
Process Information: Caller Process ID: 0xc70 Caller Process Name: C:\Windows\SysWOW64\inetsrv\w3wp.exe
Network Information: Workstation Name: SAGETESTSERVER2 Source Network Address: - Source Port: -
Detailed Authentication Information: Logon Process: Advapi   Authentication Package: Negotiate Transited Services: - Package Name (NTLM only): - Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request. - Transited services indicate which intermediate services have participated in this logon request. - Package name indicates which sub-protocol was used among the NTLM protocols. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested

Dane, this looks to be an account issue.

The easiest way to fix this is through the IMan Permissions function (which changes all the permissions necessary to run IMan on the local server)

Thanks

Thanks!  I did that, and now I am getting this:

HTTP Error 500.19 - Internal Server

ErrorHTTP Error 500.19 - Internal Server ErrorCalling LoadLibraryEx on ISAPI filter "C:\Program Files (x86)\Common Files\Sage\Sage 300 ERP\Tomcat\Jakarta\isapi_redirect.dll" failed

Detailed Error Information:Module    CustomErrorModuleNotification    SendResponseHandler    PageHandlerFactory-IntegratedError Code    0x80070021Config Error    Lock violationConfig File    \\?\C:\inetpub\wwwroot\IMan\web.configRequested URL    http://localhost:80/IMan/Design/DesignPage.aspxPhysical Path    C:\inetpub\wwwroot\IMan\Design\DesignPage.aspxLogon Method    Not yet determinedLogon User    Not yet determined
Config Source:  180:     181:       182:       

Dane, I am not sure what's wrong...it would appear there are some environmental issues preventing the IMan IIS Application pool from running.

1. I would double/triple check that you have all the necessary windows pre-requisites.
2. Ensure the IMan IIS Application Pool is set to .net 2.0 AND that the IMan IIS Application itself is set to that pool.
3. Ensure that when you ran the Permissions function it completed successfully.

Thanks