Home » blog » Neil's blog

iMIS15 client login

Posted March 8th, 2009 by Neil

I've run into an issue with an initial iMIS15 install. I have the client installed on a PC, attempt to login, get the message that there is an attempt to create ODBC connection but the process appears to hang. Eventually, the iMIS15 client is "Not Responding".

I can verify that the login authentication takes place by attempting to login with an invalid account. I see that the ODBC connection is created in ODBC admin on the PC.

I've attempted to manually create an MS SQL Server ODBC connection but the test connection fails.

I'm able to login via the Web Admin and Public interfaces.

I've verified that web.config in Net and iMIS15 folders and asi.workflow.services.exe.config have the appropriate sa password as suggested in a posting on a changed sa password.

Searching on MS SQL Server 2005 ODBC connections, I've verified that the server allows Remote connections and the MS SQL Server Browser Service is running. The Firewall is not enabled on the server.

I've checked with ASI Support and worked through their proposed solution of running the DB Repair and "Prepare Database" and "Reset Passwords".

Still have the issue with a hanging client login. Any Suggestions.

Neil's blog | login or register to post comments | printer friendly version

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Some things to check

On March 9th, 2009 Eric Means says:

What server name is the web.config connection using? (You can check on the System Setup page.) That name needs to be resolvable and usable from the client (for instance, using "localhost" or any of its synonyms would cause this behavior), because the server basically passes the web.config connection string as-is to the client (it doesn't rebuild it or replace things like "localhost"). Try pinging that name from the client to ensure you can get to it.

The fact that the test connection you've created is failing means it's not anything specific to iMIS, it's something wrong between the client and server machines; maybe a firewall (not on the server, but still between the two) or other connectivity issue.

You could also check that the SQL Server is set to allow Mixed Authentication (although I think that would cause a different error).

login or register to post comments

The values

On March 9th, 2009 Neil says:

Server name: IMIS\SQLEXPRESS
from web.config:
connectionStringName="DataSource.iMIS.Connection"

Also:
"sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;user id=sa;password=" cookieless="false" timeout="20" "

We were able to ping the server. As I mentioned, the login validation appears to work since it gives the "invalid username/password" message unless a valid username/password is provided.

Thanks
Neil

login or register to post comments

The login validation doesn't

On March 9th, 2009 Eric Means says:

The login validation doesn't go through ODBC or use the connection string from the client, it hits the web service.

You might check to see if the SQL Server is configured to allow both named pipes and tcp/ip connections; it's possible it's only allowing one of the two and the client isn't configured to use that type.

login or register to post comments

SQL Server config

On March 9th, 2009 Neil says:

It was set up to accept both TCPIP and Named pipes. I changed it to just TCPIP to see if that made a difference.

login or register to post comments

Can you connect to it from

On March 9th, 2009 Eric Means says:

Can you connect to it from other workstations?

If so, check the HOSTS file to see if there's a setting in there (or ensure that ping is hitting the right IP address).

If not, double check that the SQL Express instance is set to allow remote connections and that it's listening on all network connections (if the server has multiple).

login or register to post comments

SQL Instance

On March 9th, 2009 Neil says:

Yes, that was the trick. By default, the SQL instance was set up just for Shared Memory, as soon as I enabled the TCPIP setting within the instance properties, I was able to make the connection from the desktop.

Thanks for the input.

login or register to post comments

More things to check

On March 9th, 2009 Henry Huey says:

You note that iMIS is creating the ODBC DSN successfully (iMIS___servername_iMIS15). In ODBC Admin, can you test the data source in that DSN successfully? If you delete the DSN in ODBC Admin, is it re-created the next time you login to iMIS?

If this is Vista, are you running iMIS as administrator (shortcut properties / Compatibility / Privilege Level)?

Check the registry value in HKEY_CURRENT_USER\Software\Advanced Solutions International for ServerURL; earlier versions of iMIS 15 use this, and there might be an invalid value lingering there from a failed connection.

Along those lines, make sure the server URL set in the desktop is accurate.

Do you see a process message that says "Logging on to server (server info)..." ?

login or register to post comments

DSN

On March 9th, 2009 Neil says:

No, the test was unsuccessful. When I deleted the DSN, it was successfully re-created on next login attempt.

This is an XP desktop.

For the registry value, if there is one, do I just delete any value there? Will this registry value get reset?

I do see the message: "Logging on to server: iMIS__iMIS_iMIS15:070DBC..."

login or register to post comments

DSN problems

On March 9th, 2009 Henry Huey says:

Since the DSN is created, the URL is valid, and the connection to the authentication web service is working. The message indicates the login via ODBC is failing, so I'd suggest you focus on why you can't test the DSN from ODBC Manager. Take a look at the netlib setup in ODBC Manager (the Client Configuration button), and compare it with your SQL Server setup (SQL Configuration Manager / Network Configuration / Protocols) to see if there's a mismatch.

login or register to post comments