on 05-16-2016 3:48 PM
We have Crystal Reports Server 2008. This is the second time I have dealt with this issue and I have no idea how to resolve this or what causes it. Over time, logging into the CMC web console gets slower and slower. Same thing when opening the crystal reports 2008 client tool, logging into the "enterprise" server (our server), then once I expand the enterprise tree, it take almost ten minutes for our reports to show up. Same thing with the CMC log in, it takes that long to log into the console. Once open clicking on various things is a little slow too. Even worse, if I go into the Infoview page, log in, once in I try to navigate publications, it's super slow. Once a reports is open, the report runs fine. Any scheduled reports seem to run just fine in the background however it's almost unusably slow when we try to log into the CMC over web UI or through the crystal client by logging into enterprise or using infoview looking for reports or publications. The server operating system is windows 2008 and the default install was chosen with MySQL. The server OS performance is fine, all resources are showing a low utilization percentage.
In the past, I fixed this simply by reinstalling the whole server, manually re-uploading reports and recreating publications and schedules. I really don't want to do this again. There must be an explanation to this behavior and a way to resolve.
Any help is greatly appreciated.
How many XI3.1 objects are there in your CMS repository? If it is > 100,000 objects, try add the following to the end of the command line for each CMS you have in the XI3.1 cluster to see if this improve the CMS query performance.
-maxobjectsincache 100000 -threads 150 -nbqthreads 10
2nd, a CMS can manage no more than 400 concurrent login sessions as sizing guide mandates. Thus, add one more CMS node if you have a large XI3.1 environment.
Also, check the release notes for XI3.1 Service Pack7 and before your current XI3.1 version for the fixes on CMS query performance.
Regards,
Jin-Chong
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is a LOT of failed jobs. I would go to the Instance Manager in the CMC, filter to failed jobs, and start deleting failed jobs. The problem is that you have over 12 million of them, so it's going to take forever to do them manually with up to 500 at a time (depending on how you've set your CMC preferences...)
You could also write either Java or .NET code using the SDK to automate the process of doing this - it wouldn't be too difficult to write.
-Dell
Ok, the programmer will have to install the .NET SDK from the Client Tools install for CRS in order to start. He'll need to use Visual Studio 2010 or newer. I have some sample code on my website for the basics of using the .NET SDK: http://www.dellstinnett.com/sample_code.html. Specifically look for "BI 4.0 fp3, Visual Studio 2010" under ".NET SDK Tutorials". This will provide the basics for logging in to the system and querying the CMS.
You will need to decide on a date for the earliest instance that will be kept in the system.
The basic flow for the program will be this:
1. Log in to the CMS.
2. Start Loop
3. Run the following query:
Select top 10000 SI_ID from CI_INFOOBJECTS where SI_INSTANCE = 1 and SI_SCHEDULE_STATUS <> 9 and SI_CREATION_TIME < [earliest date to keep]
This will get the first 10000 instances that are not schedules. (Default without "top 10000" is only 1,000 objects.)
4. For each InfoObject in the result set, call .DeleteNow().
5. End loop. Break out of loop when there is nothing returned from the query.
6. Log out of the CMS
-Dell
On top of what Dell recommendation to remove the existing failures from CMS repository, couple things need to consider when all errors are cleared.
1. You are using MySQL on localhost:3306 for CMS repository. Consider to setup an Oracle database for your CMS repository on another DB server to offload the database load from your BOXI3.1 server host,
2. there must be some recurring jobs that keeping failing, and you'd want pause or delete those trouble maker from clocking your CMS again later.
Regards,
Jin-Chong
Ok the issue has been resolved, thanks to all of you actually. I had to change the limits on everything uploaded to the server. This slowly started to remove the failed jobs. Then once enough were removed the timeouts were not as bad. This in turn allowed the .net application to run successfully and delete failed jobs without timeout errors. I now have 0 failed jobs out of over 12 million and the cmc and infoview web gui is now moving swiftly. I think you all for your help, I gave you all a helpful answer mark. There is no actual "Correct Answer" here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are having a hard time with the delete commands. A slew of errors come up, the most common is command timeout. We think we identified the problematic report or publication with all the failures however every time we try something it times out, from any method. We used the .NET program to send the commands. Any other ideas?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can set the Instance Limits on the folder in which the problematic report is present to say around 10. Then to activate the limit, just scheduled the report just once(Recurrence -> now). This will activate the instance limit and BO will start deleting all the old instances. Of course that will also take time.
In your code, how many InfoObjects are you querying for in the same batch? Thinking about it, in this case I might cut down the number of instances to a couple hundred at a time instead of the 10,000 I posted above to see whether that will speed up the query so that it doesn't time out.
-Dell
Great, thank you all, I will give this a try and report back or with questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Moved to Bi Platform forum
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.