Having problems with Historical Reports

Unanswered Question
Feb 18th, 2009

For some reason one of the PC running Windows XP Pro SP2 can't login to historical report with any user. It used to work fine. But now its not working, looking at the logs I'm seeing the below errors, any idea? I know no any other user is running the report.

1: 2/18/2009 2:47:34 PM %CHC-LOG_SUBFAC-3-UNK:The following SQL Command failed due to (Object variable or With block variable not set)SQL Command=[*****]

2: 2/18/2009 2:47:35 PM %CHC-LOG_SUBFAC-3-UNK:SQL Command Failed | Could not obtain information from database: The SQL command failed to execute. Check the log file for error 5049.

3: 2/18/2009 2:47:45 PM %CHC-LOG_SUBFAC-3-UNK:Failed to obtain from server the number of current DB Client/Scheduler Connections to 'CRA_DATABASE'

4: 2/18/2009 2:47:45 PM %CHC-LOG_SUBFAC-3-UNK:Database connection to 'CRA_DATABASE' failed due to (All available connections to database server are in use by other client machines. Please try again later and check the log file for error 5054.)

5: 2/18/2009 2:47:45 PM %CHC-LOG_SUBFAC-3-UNK:Database Connection Error | All available connections to database server are in use by other client machines. Please try again later and check the log file for error 5054.

6: 2/18/2009 2:47:57 PM %CHC-LOG_SUBFAC-3-UNK:CRA_DATABASE Connection String: Provider=MSDASQL;APP=Cisco CRA Historical Reports2980;Persist Security Info=False;Trusted_Connection=No;DRIVER=SQL Server;UID=db_cra;PWD=*****;SERVER=x.x.x.x\CRSSQL,4433;DATABASE=db_cra;NETWORK=dbmssocn;

7: 2/18/2009 2:47:57 PM %CHC-LOG_SUBFAC-3-UNK:Failed to login user to the apps server since we failed to initialize database connections

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Hythim Ali El Hadad Sat, 02/21/2009 - 07:22

Hi,

It is related to the number of DB connections you can have with your IPCC

This is to limit the performance impact of historical reporting on a particular CRS server,

you can configure a maximum number of client/scheduler database connections

per server.

From

Tools > Historical Reporting

You can modify this value

wish this be helpful

Best Regards

shamugalu1 Mon, 02/23/2009 - 06:52

Thanks for the info. That part I have verified and increased from 5 to 6 before I posted this issue. I'm sure at a time no one else is running the reports but still get the same problem from this particular PC, all other users it works just fine again it used to work fine on this PC it just doesn't work now. Thanks

Actions

This Discussion