Problem: After deploying an Agentry App from SAP Control Center, its Agentry Server instance does not start, and errors appear.
2013-01-25 12:03:39.644 CONSOLE MMS Thread-4275 [com.sybase.sup.server.Console] [] [] 12:03:39 01/25/2013 16 SQLBEException 101 SAInvalidLogin 3: SA_DBMS_API_Error, DB Code: 0, DB Text:IM002 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified, sqlBE.cpp#1357:DbConnectionPoolMgr::create 2013-01-25 12:03:40.651 CONSOLE MMS Thread-4275 [com.sybase.sup.server.Console] [] [] 12:03:40 01/25/2013 16 SQLBEException 101 SAInvalidLogin 3: SA_DBMS_API_Error, DB Code: 0, DB Text:IM002 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified,
Explanation: This can happen when an Agentry App uses a Microsoft SQL Server as its enterprise information system (EIS), and the ODBC entry is created for a user DSN instead of a system DSN. Since the Agentry server is run as a "service" user, the ODBC entry must be created for a system DSN. A user DSN entry causes the log in to SQL Server to fail.
Solution: Create a system DSN entry for the ODBC connection.