Screencasts - Hilfsvideos

Report Recovery in SMP v7.1

Created: 08 Okt. 2012 • Aktualisiert: 08 Okt. 2012 | 6 Kommentare
Dieses Problem wurde gelöst. Siehe Lösung.

Well, I finally did it. Not that I was trying to, it's just that the SMP doesn't/can't recover from my mistake. Hours of work down the drain, unless someone can help.

I created a report and thought I'd done everything right. Saved it and of course it began to run, and run, and run, and run. 10-15 minutes later, I get a message that the report timed out and to contact my administrator. Well, I'm the administrator and I don't have a clue.

The console doesn't lock. I can select another report or menu item and navigate away from this report. But because reports autorun, I can't get back to this report to edit it. If I click the browser's stop button, the report/query stops running, but the screen is still dimmed with the "Please wait" bar in the middle.

I can right-click the report and "view XML", but what a pain to decipher all that crud to find all my parameters and SQL statements.

Kommentare KommentareZum neuesten Kommentar

das Bild der andykn101s

Normally, if you wait for it to time out you can then edit it. Not necessarily if you use the browser "cancel" feature. Try opening in new window.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

das Bild der dsmith1954s

Waiting for a timeout doesn't give me the option to edit. It only says to click refresh or contact the administrator.

das Bild der andykn101s

Try a longer command timeout here:

Settings > Notification Server > Database Settings

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

das Bild der dsmith1954s

Already set to 800 seconds. That's why it takes so long to get the timeout. Not sure if that would help get the edit button back since it's already timing out. Don't really want to wait even longer for my report to appear or timeout...

I went ahead and re-created the report from scratch. I viewed the XML, and was able to retrieve my SQL query and parameters. Not exactly an ideal solution, but it worked. Had to start over two more times before getting it right.

Whatever you do, don't ever make a mistake with your SQL and parameters. It's terrible.

LÖSUNG
das Bild der andykn101s

You can test the resolved query in SQL Server Management Studio, that will tell you how long the query takes to run and can be killed there.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

das Bild der dsmith1954s

Did that, and it worked. The part that caused the issue was when I added parameters.