Service Manager new submitted incidents doesn't produce report
-
2 mai 2012 12:14We are having hard times troubleshooting this issue. When we submit incidents, it doesn't produce reports. We check for new entries in the data warehouse server but its not there. We can only produce reports with the past 3 months only. Is it a bug or is there any way to sync it up?
Toate mesajele
-
2 mai 2012 18:49Moderator
Hi,
The ETL jobs copies the data from the Service Manager database to the Data Warehouse databases continuously, but it might take up to two hours until the data is available in a report. So if you are unable to see your new incidents after some hours, you need to troubleshoot your ETL jobs.
Start with:
1. Take a look at the Data Warehous jobs inside Service Manager. What's the status of these?
2. Look for any errors in the Operations Manager event log on both the Service Manager Management Server and the Data Warehouse Management Server.The third step would be to run some powershell commands. Try 1 and 2 first and post here if you need the commands.
Regards
//AndersAnders Asp | Lumagate | www.lumagate.com | Sweden | My blog: www.scsm.se
-
3 mai 2012 06:00
Hi,
As per AnderAsp,
you can get the information through Powershell as well.
Get-scdwjob -computername <nameofdwserver>
and for more details
get-scdwjobmodule -computername <nameofdwserver>
As long as you learn something new every day, the day is not wasted.
-
3 mai 2012 06:34
Hi Fletcher,
I can't execute the your commands in powershell. I already run it as administrator and imported smlets before executing it but it can't recognize Ge-scdwjob. Thanks by the way.
Hi AndersAsp
We already can't view two months old of ticket reports.
-
3 mai 2012 07:07
Hi,
If this is SCSM 2012, you can open the Service Manager Shell on your client machine.
If this is SCSM 2010, then run this in powershell
Add-PSSnapin SMCmdletSnapIn
Then run the get-scdwjob and get-scdwjobmodule
these are native to SCSM.
Hope this help,
F.
As long as you learn something new every day, the day is not wasted.
-
3 mai 2012 07:16
Here are the error logs.
-
4 mai 2012 07:30Moderator
You need to check the logs on the Data warehouse server. And while you're at it, run the powershell commands on the Data warehouse server.
Add-PSSnapin smcmdletsnapin Get-SCDWJobModule
This should give you a long list of jobs and modules. The last column will display any errors.
I do not have any errors in my environment, but let's pretend that the first row had an error message. Unfortunately the column that is displaying the error message is way to small to display the whole error message, so in order to get the whole message, you will have to run this command:
Get-SCDWJobModule -JobName Transform.common -ModuleID 2622 | fl
Replace the jobname and the moduleid with the erroneous module that you discovered in the previous step.
Regards
//AndersAnders Asp | Lumagate | www.lumagate.com | Sweden | My blog: www.scsm.se
-
4 mai 2012 08:12
The jobs are already already running but I noticed one module not started yet
We also noticed this under mpsyncjob. Its still waiting since yesterday
And this.
-
4 mai 2012 08:13
.png)
