Re: After reinstallation

no, it should work.. provided all the pcs required to make it work are working...

In my opinion it is to dependent on the client being in a "just so" condition before it will work.
"Ruben @ DK" <not@xxxxxxxx> wrote in message news:D01A7C3B-A31B-4E9C-9167-AA3D4A99AA0A@xxxxxxxxxxxxxxxx
Hi Todd
Thanks, for you help! I guess what you say is that my server is running
fine, but I should not expect client push to work.
Regards
Ruben

"Todd Hemsell" <hemsell@xxxxxxxxx> wrote in message
news:%23p8AVaC1GHA.4392@xxxxxxxxxxxxxxxxxxxxxxx
Looks like you got everything working well. FOr the push go look in
%windir%\System32\ccmsetup and you should see some logs. not reall sure how
to assist you in troubleshooting that. Personally I found the push to be
very unreliable. We only had about 70% coverage with the client using push.
We went to a GPO startup script to install the client and got up to about
99.5% coverage.

CAS.log:
GetLogonUserSid failed at GetTokenSids 0x800704dd ContentAccess 08-09-2006
22:51:27 1644 (0x066C)

Common - Ignore

mtrmgr.log:
GetFileVersionInfoSize failed for file \SystemRoot\System32\smss.exe, error
2
Program might not match metering rules, as version header was not read.
Failed to get file path for process 4, will retry later

Not sure, would not worry.

PatchUIMonitor.log:
Unable to VP cache path, Error return (2) PatchUIMonitor
WARNING: Failed to load software updates schedule list -- PatchUIMonitor
LoadQueue function failed with hRes = 0x80004005

Have you scanned your machines wiht ITMU or MBSA? VP Cache is where it
stores the results so no scan no vpcache path - no big deal until you begin
patching

>
> RE the MP cert -> look in Mpcontrol.log on the site server and
> PolicyAgent.log on the client. I cannot remember the cases but MP
> Trobleshooter does not always work, local or remote, one of them bombs on
> some items. Those logs I mentioned will tell you for sue

MPControl.log, looks all fine:
Http verification .sms_aut (port 80) succeeded with status code 200, OK

If this is OK all is well.

PolicyAgent.log, is this okay?
Requesting Machine policy
assignments PolicyAgent_RequestAssignments 08-09-2006 23:25:28 2696 (0x0A88)
Requesting policy from authority 'SMS:001'
Raising event:

instance of CCM_PolicyAgent_AssignmentsRequested
{
AuthorityName = "SMS:001";
ClientID = "GUID:53BD0B71-5F58-4052-B9D8-0C04258A2500";
DateTime = "20060908212528.641000+000";
ProcessID = 1432;
ResourceName = "SRV1";
ResourceType = "Machine";
ThreadID = 2696;
};

Got its policy, all is well

THE SITE STATUS ERROR AND WARNING MESSAGES
I hope you can translate some of them.

---
SMS Active Directory System Group Discovery Agent reported errors for 3
objects. DDR's were generated for 3 objects that had errors while reading
non-critical properties. DDR's were not generated for 0 objects that had
errors while reading critical properties.

Fairly common


Component name: SMS_COMPONENT_STATUS_SUMMARIZER
Executable: C:\SMS\bin\i386\smsexec.exe
Process ID: 1340
Thread ID: 2172
Instruction address: 7768F202
Exception code: C0000005 (EXCEPTION_ACCESS_VIOLATION)
Additional information: The thread tried to read from the virtual address
00000060 for which it does not have the appropriate access.
---

The one above is just scary. Might be a hotfix or something. I would look
into that one if you see it more often. If just once just write it off


The program for advertisement "00120000" failed ("00100001" - "STD"). A
failure exit code of 1 was returned.
User context: SUB\rs


Why are you running as a user? Are you in advanced security mode

---
SMS Inventory Data Loader failed to process the delta MIF file
"Xwg3iu3x6.MIF" and has moved it to
"C:\SMS\inboxes\auth\dataldr.box\BADMIFS\1jn1ym1j.MIF."

As part of regular maintenance you need to keep track of how many items are
in this folder C:\SMS\inboxes\auth\dataldr.box\BADMIFS\
very many indicates an issue.

---
SMS Software Inventory Processor failed to process software inventory file
"C:\SMS\inboxes\auth\sinv.box\2ej81j9k.SID," and has moved it to
"C:\SMS\inboxes\sinv.box\BADSinv\y3i8a2p7.SID."


As part of regular maintenance you need to keep track of how many items are
in this folder "C:\SMS\inboxes\sinv.box\BADSinv
very many indicates an issue.



---
SMS Active Directory System Group Discovery Agent reported errors for 1
objects. DDR's were generated for 1 objects that had errors while reading
non-critical properties. DDR's were not generated for 0 objects that had
errors while reading critical properties.

Just one? Excellent :-)


---


>
> RE wbemwrap.log:
> Warning - could not find C:\SMS\core\bin\smsclreg.dll. Defaulting to
> English.
> I use only english SW, can I ignore this?
>
> Yes, pretty sure you can ignore,
>
> Also, open site status on the site server and go have a look at anything
> red. Expand it until you see the component then right click and show all
> messages.
> quite a few of them include the solution. That is one of my fav places to
> check status and track down errors. It is a good place to look to find
> errors you might be haivng that have not "surfaced" in other places yet
> (read user complaints)
>
> Hope that helps some.
> I am a poor typist so if I need to clarify something let me know. I often
> do not type all I think :-)
>
> Regards,
>
> Todd
> "RUBEN @ DK" <RUBENDK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:2DC51F46-D9F3-45EB-8290-3E2ADB0D7988@xxxxxxxxxxxxxxxx
> Hi Todd
>
> After reinstallation:
>
> I can now deploy SW, if the client is manualy installed.
> I can assign the client, but it dosent install.
> I can not deploy the Client with client push.
>
> The MP installation was succesful, YES!
> The amount of error messages is reduced, so I am getting closer.
> But I must have forgotten some setting, etc. Hope you can help.
>
> I tryed the MP Trobleshooter, it returns only one error:
> Testing MPCERT HTTP request functionality
> - Failed - The server is not operational
>
> Error messages:
> SLPsetup.log
> ERROR: Cannot read reg value of Software\Microsoft\SMS\IIS\SMSPortList
> (0)
> ERROR: Cannot read reg value of
> Software\Microsoft\SMS\IIS\SMSPortUsageCount
> (0)
>
> wbemwrap.log:
> Warning - could not find C:\SMS\core\bin\smsclreg.dll. Defaulting to
> English.
> I use only english SW, can I ignore this?
>
> Below is described how I did the installation
>
> I reinstalled the server, like this:
> Win2003SP1
> ASP, COM+, DTC,
> IIS inkl.:
> - BITS
> - active server pages
> - IDC
> - Server side includes
> - WebDav
> - WWW
> Without Remote admin (HTML)
>
> SQL2000SP2
> - upgraded to SQL SP4
>
> SMS 2003 SP1, advanced security.
> - Upgraded to SMS 2003 SP2
>
> Upgraded SQL 2000 to SQL 2005
>
> Did I do this corectly?
>
> Thanks in advance
>
> Best regards
> Ruben
>
>
>
>
>
> "Todd Hemsell" wrote:
>
> > do oyu have an account at licensing.microsoft.com ? it is for software
> assurance customers. you can download an integrated CD from there.
> >
> > I have heard, though do not have firsthand experience.. you cannot
> integrate one yourself.
> >
> > Todd
> > "RUBEN @ DK" <RUBENDK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:3B5332EE-A33D-46FD-96D6-E2A9C3C55B78@xxxxxxxxxxxxxxxx
> > Hi Todd
> >
> > I tried to find a ISO image, SMS 2003 with SP2 integrated, on MSDN
> without
> > success. Now I try to integrate SP2 in the installationfiles SMS2003
> with SP1
> >
> > I recive error as below no matter what path I write.
> >
> > Path to the installation files: E:\SMS2003
> > ex.:
> > en_SMS_2003_sp2.exe /integrate:E:\SMS2003\SMSsetup\bin\i386
> > en_SMS_2003_sp2.exe /integrate:E:\SMS2003\SMSsetup\bin
> > en_SMS_2003_sp2.exe /integrate:E:\SMS2003\SMSsetup
> > en_SMS_2003_sp2.exe /integrate:E:\SMS2003
> >
> > [smssp2.log]
> > 0.032:
> >
> ================================================================================
> > 0.047: 2006/09/05 14:17:52.843 (local)
> > 0.047: e:\f0f5290f74c7f75931\update\update.exe (version 6.1.22.0)
> > 0.047: Slipstream mode
> > 0.047: Service Pack started with following command line:
> > /integrate:E:\SMS2003\smssetup\bin\i386 /log:e:\smssp2.log
> > 0.125: Package Type: CLASSIC
> > 0.125: GetBuildInformation: Error 0x3 while trying to retrieve
> target OS
> > version information from E:\SMS2003\smssetup\bin\i386.
> > 0.125: GetTargetOSInformation: Error retrieving build information:
> GLE = 0x3
> > 0.125: IntegrateHotfix: Error 0x3 while gathering information about
> target
> > E:\SMS2003\smssetup\bin\i386.
> > 0.125: Hotfix Integration failed with error 0x3
> > 4.047: Message displayed to the user: An error occurred while
> attempting to
> > integrate this software update package. Verify that the
> architecture,
> > language, and service pack level of this software update are valid
> for the
> > target distribution folder.
> > 4.047: User Input: OK
> > 4.047: An error occurred while attempting to integrate this software
> update
> > package. Verify that the architecture, language, and service pack
> level of
> > this software update are valid for the target distribution folder.
> >
> > How to do?
> >
> > Regards
> >
> > Ruben
> >
> >
> > "Todd Hemsell" wrote:
> >
> > > Only SMS 2003 SP2 will work with SQL 2005.
> > > Unless you have a SP2 CD you will have to go SQL 2000 then install
> SMS SP2, then upgrade SQL to 2005
> > >
> > > Sorry you could not get it resolved.
> > >
> > > Regards,
> > >
> > >
> > > Todd
> > > "RUBEN @ DK" <RUBENDK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> message news:0D66CBFE-473E-473C-9CAA-DCBB249509D0@xxxxxxxxxxxxxxxx
> > > HI Todd
> > >
> > > Well, I gave up. I am now reinstalling the server. Can SMS 2003
> run on a
> > > Win2003R2 with SQL 2005? that is my plan anyways.
> > >
> > > "Todd Hemsell" wrote:
> > >
> > > > Not sure where to go next with this. I did find a KB article
> on your issue, I hope it helps you
> > > >
> > > > http://support.microsoft.com/kb/917675
> > > > "RUBEN @ DK" <RUBENDK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> message news:9FA94B54-2EEA-4E0C-88B5-9C8E1118DB56@xxxxxxxxxxxxxxxx
> > > > IIS, BITS, webdav is installed. Webdav is set to Allowed, In
> the Web Services
> > > > Extensions. On default website, I have set Allowed clients
> to transfer data
> > > > to this virtuel directory. Is that the corect settings?
> > > >
> > > > Under default website I have:
> > > > aspnet_client
> > > > BITS-Sessions
> > > > SMSComponent
> > > > SMSReporting_001
> > > >
> > > > What rights do I need to set?
> > > >
> > > >
> > > > "Todd Hemsell" wrote:
> > > >
> > > > > check permissions and ensure you have bits server
> extensions installed and webdav enabled..
> > > > > Also ensure iis is installed etc...
> > > > >
> > > > > ccm incoming is a bits enabled virtual directory in iis
> where the clients communicate with the server (upload events ect)
> > > > >
> > > > >
> > > > > "RUBEN @ DK" <RUBENDK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
> in message news:7DB5617F-B34C-457A-93FF-884878855ABD@xxxxxxxxxxxxxxxx
> > > > > From MPSetup.log:
> > > > >
> > > > > Setup was unable to create the Internet virtual
> directory CCM_Incoming
> > > > > The error code is 80020009
> > > > >
> > > > > What does this meen, and how do I solve it?

Relevant Pages

  • Re: After reinstallation
    ... If you manually install the client and open the system manager in control ... See Ccm.log on site server ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... The MP installation was succesful, ...
    (microsoft.public.sms.setup)
  • Re: Adv Client with Workgroup Computers
    ... I was trying to use the SMS tools from the SMS server to initiate harware ... Inv for example the account is a domain account but the Client PC is in a ... Is there a procedure for installing the ADV client localy on a workgroup ... I have manually added to the WINS server. ...
    (microsoft.public.sms.admin)
  • Re: After reinstallation
    ... I guess what you say is that my server is running fine, but I should not expect client push to work. ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... "Todd Hemsell" wrote: ...
    (microsoft.public.sms.setup)
  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
  • Re: 4912: Cannot update the already existing object. Need some he
    ... Also, as far as the client pointing to the wrong server, you should use SMS ... SP3 client through a logon batch file. ...
    (microsoft.public.sms.admin)
Loading