Re: SMS Reports missed

Thnaks Torsten!

Yes, it is a new install of SMS on the server, and I installed SMS with a
media that already included SP2.

I found _SMSRprt.mof file on \SMS\bin\I386, then I copy this file to another
location, and then replaced "REPLACESITECODE" with my sitecode on the MOF
file located at \SMS\bin\I386. After that, I removed RP from server, checked
that it was removed, and then rebooted the server. After this, reinstalled
RP but there are the same reports that I had before.

I also noticed that there is another reporting file related, _SMSRPTCOL.mof,
that I don't know if it is used by SMS to create report collections.

This is the list of reports that I have right now.

Name
Category Report ID
Advertisement status messages for a particular client and advertisement
Software Distribution - Advertisement Status 0000000014
All computers with a specific software update distribution status Software
Update - Distribution Status 0000000007
All computers with a specific update advertisement state Software Update -
Distribution Status 0000000015
Compliance by Bulletin-ID and Qnumber Software Update -
Compliance 0000000013
Compliance by product Software Update -
Compliance 0000000004
Compliance by Software ID Software Update -
Compliance 0000000011
Computer information for a specific computer Hardware -
General 0000000001
Computers where a specific software update is applicable Software Update -
Compliance 0000000002
Distribution status summary of software updates Software Update -
Distribution Status 0000000009
List of computers that have not scanned with the latest synchronized
catalog. Software Update - Compliance 0000000012
Software update advertisement Status by software update ID Software Update -
Distribution Status 0000000016
Software update distribution status by software update ID Software Update -
Distribution Status 0000000008
Software updates for a specific computer Software Update -
Compliance 0000000005
Software updates not yet authorized Software Update -
Compliance 0000000006
Software updates with count of applicable and installed computers Software
Update - Compliance 0000000003
Summary of software updates that failed to deploy Software Update -
Distribution Status 0000000010





"Torsten [MVP]" <torsten.meringer@xxxxxxxxxxxxx> wrote in message
news:1olmew8ss13yl$.19u73opzcxl23$.dlg@xxxxxxxxxxxxx
Hi German,

is it a new sms install on the server? I've seen that once. You could try
mofcomp'ing the _SMSRprt.mof (search your SP2 directory) on your
siteserver
again (copy the file to a different location and replace "REPLACESITECODE"
with your actual SMS sitecode).

Torsten
Microsoft MVP - SMS

Am Wed, 15 Nov 2006 14:26:50 -0600 schrieb German Suazo:

Hello! We have some problems with SMS Reports. The problem is that there
are
a lot of reports missed, we only have like 15, and they are Software
Update
ITMU reports. We have tried uninstalling the Reporting Point, and
installing
again, but the problem still. There are no errors on Reporting Point
components on System Status. We have checked with SMS Trace Rsetup.log
and
SMSReportingInstall.log files but we did not find any errors.

This is what we have:
- SMS Site Server based on SMS 2003 SP2, configured with Advanced
Security.
SMS is installed on a Windows Server 2003 SP1, and I already configured
DCOM
permissions, as says on this URL on Windows Server 2003 SP1 section
(http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/tfaq02.mspx#EMHAC).
This server has MP, RP, CAP, SLP and DP site system. We already did SMS
Server account, member of Domain Admins, and also gave Full Control over
AD
System Container.
- SMS Site Database is located on another server. Database is on a SQL
Server 2000 SP4, and the OS is Windows Server 2003 SP1. We already put
SMS
Site server account as a local administrator on SMS Database Server.


What could we do to solve this problem.

Thanks!


.

Relevant Pages

  • Re: Failed upgrade to SCCM
    ... but I've done an SMS restore to new ... I had during the upgrade would prevent the new install / site repair from ... I recently started the upgrade our SMS 2003 SP3 Server to SCCM. ...
    (microsoft.public.sms.setup)
  • SMS INSTALL ERROR 4909 help
    ... Name of Product: SMS Version 2003. ... Windows Server 2003 with all available server updates. ... I notice that I can install client from the server also I ... Nor could it create a default container. ...
    (microsoft.public.sms.setup)
  • Re: Installation of Client
    ... SmsDetectDowngrade_ErrorMessage = A newer version of the SMS ... Advanced Client is already installed ... I also manually added the WINS information into the WINS server that both ... cannot get the client to properly install. ...
    (microsoft.public.sms.setup)
  • Re: Unable to Install SMS 2003 R2
    ... Since SP3 is greater than SMS 2003 R2, this would make sense that you can't install it over top of SP3. ... Tool installer is asking for the SQL server information. ...
    (microsoft.public.sms.admin)
  • Re: Quick Poll to help the SMS product group
    ... get scanned for updates instead of just the test computer which usually is ... too many people who would purposely make their sms server stay logged in. ... > When you install the scan tools, you get up to three collections based on ... > Distribute Software Update Wizard.) ...
    (microsoft.public.sms.misc)
Loading