Attix5 Pro FAQ
Search:     Advanced search

SQL Errors after starting the AS service

Article ID: 80
Last updated: 13 Jul, 2012
Problem Description
1.     After starting the AS service the following errors are seen in the ASLOG:
 
07:52:28.763 (06) Error: SqlException: A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
Possible cause: Your database migration script gave an SQL error.
Try the following: Contact your account manager with this error information......   

    
16:49:29.220 (05) Error: Unable to start server: Database server not available or database migration script error. Attix5.StoragePlatform.Common.Exceptions.StartupException: Database server not available or database migration script error
   at Attix5.StoragePlatform.Common.SPService.OnStart(String[] args)
16:52:26.817 (0a) Error: Error while processing XML-RPC call from BUDView@78.86.194.235: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.....
 
2.     The SP Console is not able to connect to the AS or no Group/User info and activity is displayed.
 
Cause
The amount of connections made to the SQL server (AS Database) exceeds the default pool size. As there are no connections available the database cannot be queried to populate the SP Console.
 
Solution
Add  ‘;Max Pool Size=xxx’ into the ConnectionStrings.config to both the BackupServer and ReportServer string.
 
Eg:
<add name="BackupServer" connectionString=";Integrated Security=SSPI;Persist Security Info=True;Data Source=(local)\SQLEXPRESS;Initial Catalog=StoragePlatform;MultipleActiveResultSets=True;Connect Timeout=30;Max Pool Size=200 " />
 
<add name="ReportServer" connectionString=";Integrated Security=SSPI;Persist Security Info=True;Data Source=(local)\SQLEXPRESS;Initial Catalog=StoragePlatformReports;MultipleActiveResultSets=True;Connect Timeout=30;Max Pool Size=200 " />
 
Keep the following in mind
  •  For every 100 access users created in the SP or accessing the SP simultaneously (SP Console), you should increase the Max Pool Users in the connection string with the same amount (default is 100).
  • If you are running the SQL server on the same box as the AS, use the SharedMem protocol by using (local) as the server name in the connection string.
               Eg: Data Source=(local)\SQLExpress;
  • If you experience query timeouts on you SQL server under heavy loads consider using Full SQL server, running on a dedicated Server.
Article ID: 80
Last updated: 13 Jul, 2012
Revision: 1
Views: 4353
Comments: 0
Posted: 18 Nov, 2011 by Van Rensburg J.
Updated: 13 Jul, 2012 by Van Rensburg J.
This article was:  
Prev   Next
Article 146 - Changing memory in the Windows Backup Client (DL and SE)     Article 81 - Installing an Attix5 Pro AccountServer using a separate SQL...