This error may be due to problems connecting to the ASM database.
Typical scenarios:
-
The error occurs at the end of the installation. This happens if the setup configured the database access by a wrong network library, e.g. the Named Pipe library. TCP/IP network library is required by ASM.
-
ASM has been installed with MSDE and the error occurs after a period where the application worked correctly. This error occurs if the database size has reached the intrinsic size limitation of MSDE (2GB).
-
The error occurs after a machine reboot with ISAPI installations (default installation using IIS and SQL Server or MSDE). The error occurs if the achml.dll (which stores database connection data) is loaded into the memory before the ASM database is effectively available.
- The error occurs while the application is working without a machine reboot. This error may occur on ISAPI installations when the database connectivity is lost, also for a short period. GCI installations (default installation using Xitami or MySQL) works again immediately when the connectivity is restored while ISAPI installations not (only when the achml.dll is reloaded into the memory).
-
ASM database could not be online.
Troubleshooting:
-
The ODBC DNS used by ASM must be configured again:
– go to Administration Tools > Data Sources (ODBC) on the machine where ASM is installed
– select the "System DNS" tab
– edit the source created by the ASM setup (it should named like ASM__ASM_DB)
– click Next
– click Client Configuration
– select the TCP/IP library option
– click OK
– click Next
– select the SQL authentication and insert into the ID and password fields the credentials chosen during the installation for the ASM user (default ASM_USER)
– select the ASM database (default ASM_DB)
– click Next
– click end
– click Check the source data and verify if the test is successfully completed
– click OK
– restart the Web server -
Migration to SQL Server or MySQL is recommended since MSDE database seems to be not appropriate to your data volume.
-
Proceed in this way:
– try to restart the Web server
– try to restart the database server and when this is completely available try to restart the Web server
– check the ASM database connection (view the “Check database connection” section more down) - Proceed as point 3.
- Please, look at this article.
If your scenario is different, please try to:
– check if into ASM engine logs (core.log files into
– check if there are errors into database logs.
Check database connection
The ASM Web interface uses OLE DB technology to connect to the ASM database: login credentials, chosen during the installation are written into the
SQL serverMSDE:
To check database connection you can use:
-
the
toolsConfigTool.exe utility, following the wizard till the test -
the SQL Query Analyzer checking the database connection and if it’s possibile to execute a query without errors, e.g.:
SELECT cfg_value FROM sys_config WHERE cfg_id = 27
-
-
open the Windows command prompt
-
execute this command:
osql -U-P -S
where
is the ASM user username chosen during the installation
is the ASM user password
is the hostname or IP address plus the optional instance name -
digit
1> use(where is the ASM database name)
2> go
1> SELECT cfg_value FROM sys_config WHERE cfg_id = 27
2> go
MySQL:
-
-
open the Windows command prompt
-
change the folder to
bin folder (where there is the mysql.exe file) -
execute mysql -u
-p
where
è the ASM user username chosen during the installation
is the ASM user password -
digit USE
; (where is the ASM database name) -
digit SELECT cfg_value FROM sys_config WHERE cfg_id = 27;
-
digit SELECT cfg_value FROM sys_config WHERE cfg_id = 27;
-
digit USE
-
execute mysql -u
-
change the folder to
-
open the Windows command prompt
-
digit
-
execute this command:
-
open the Windows command prompt