Re: SMS 2.0 Component Errors - Pre Upgrade

From: Stan White [MS] (stanwh_at_microsoft.com)
Date: 05/26/04 

Date: Wed, 26 May 2004 09:00:19 -0700

It's possible that the registry is corrupt, missing or permissions are such
that the service account cannot read those keys.
The other suggestion is try an upgrade instead of site reset.
ACLRESET will fix the permissions but will not fix the keys.

If you are still having issues, one more thing to check is invalid
characters in the inbox registry definition keys.
At least once we have seen a recursive registry path in the inbox registry
keys.

We saw \Microsoft\SMS\... appended where there should have just been a
numeric value at all keys below:

\HKLM\Software\Microsoft\SMS\Inbox Source\Inbox Definitions\ 

-- 
-- 
Stan [MSFT]
--
--
This posting is provided "AS IS" with no warranties, and confers no rights.
--
--
"poolefa" <anonymous@discussions.microsoft.com> wrote in message 
news:79846D07-4B5E-41E0-8EAB-B961C904A894@microsoft.com...
>I am getting the exact same error, I have reset the site and this did not 
>help.  Is there anything else I can do? I really need to get this problem 
>resolved.
>
>     ----- Stan White [MS] wrote: -----
>
>     The second message is 'normal' and is just part of inventory trying to
>     resync a client when it gets a mismatch (delta inventory with no full, 
> etc.)
>
>     The first message is a problem - however, ignore the 997, it's 
> meaningless
>     in this situation and is just the error ID sitting on top of the error
>     stack. The real message is most likely already handled.
>
>     When you upgrade or run a site reset, or when site component manager
>     determines that a component server 'role' is not functioning, it will
>     de-install and re-install the 'component'. The registry key mentioned 
> is the
>     location where the thread state and requested stop/start operation are
>     stored for the thread(s) of SMS Executive.  If that registry entry is
>     missing/corrupted or the service account is locked out of it you may 
> see
>     this.
>
>     It would be useful to find the first time this error happened and 
> determine
>     what else changed just before that.
>
>     A site reset might fix this problem since that action will de-install 
> and
>     re-install all components.
>
>     -- 
>     -- 
>     Stan [MSFT]
>     --
>     --
>     This posting is provided "AS IS" with no warranties, and confers no 
> rights.
>     --
>     --
>
>     "JasonC" <jcecchin@hotmail.com> wrote in message
>     news:917422b8.0404182141.225ba18d@posting.google.com...
>     > I am getting the following SMS Message errors in the Component 
> Status
>     > message list.  Has anyone has had experience with these before?
>     >> This server is currently a SMS 2.0 server running on SP5.  It has
>     > around 400 clients connected to it.  It is a site server in a larger
>     > hierarchy and has no servers beneath it.
>     >> This server is to be upgraded to SMS 2003 in the next couple of 
> days.
>     > I am wondering should I worry about these errors before performing 
> an
>     > upgrade.  I prefer to upgrade a server with no errors, but realise
>     > that the upgrade may indeed fix these problems.  If the problems are
>     > easy to fix then I wouldn't hesitate to resolve them before I do the
>     > upgrade.
>     >>> SMS_INBOX_MANAGER_ASSISTANT (Occurs approximately hourly)
>     > ===========================
>     >> Milestone Information MessageID: 1018
>     > SMS Site Component Manager is reinstalling this component on this 
> site
>     > system.
>     >> Milestone Error MessageID: 578
>     > Could not read registry key
>     >
> 
> "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMS_EXECUTIVE\Threads\SMS_INBOX_M
>     ANAGER_ASSISTANT"
>     > on computer SMSSERVER. The operating system reported error 997:
>     > Overlapped I/O operation is in progress.
>     >> Milestone Error MessageID: 578
>     > Could not read registry key
>     >
> 
> "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMS_EXECUTIVE\Threads\SMS_INBOX_M
>     ANAGER_ASSISTANT"
>     > on computer SMSSERVER.
>     >> Milestone Error MessageID: 580
>     > Could not delete the registry key
>     >
> 
> "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMS_EXECUTIVE\Threads\SMS_INBOX_M
>     ANAGER_ASSISTANT"
>     > on computer SMSSERVER.
>     >> Milestone Error MessageID: 1020
>     > SMS Site Component Manager failed to reinstall this component on 
> this
>     > site system.
>     >>> SMS_INVENTORY_DATA_LOADER (Occurs approximately half hourly)
>     > =========================
>     >> Milestone Warning MessageID: 2702
>     > SMS Inventory Data Loader failed to process the delta MIF file
>     > "Xu1l0o02d.MIF" because the file does not have a corresponding
>     > discovery record. SMS Inventory Data Loader has moved this file to 
> the
>     > Orphans directory as file
>     > "F:\SMS\inboxes\dataldr.box\ORPHANS\8ov1zh23.MIF" and will retry
>     > processing it within 10 minutes.
>     > Possible cause: The delta MIF file came from an SMS 1.2 site, and
>     > these sites do not have discovery agents.
>     > Solution: Verify that the delta MIF file is from a 1.2 site. If so, 
> do
>     > nothing.
>     > Possible cause: Discovery Data Manager is not running.
>     > Solution: Stop and restart Discovery Data Manager. You can use SMS
>     > Service Manager, which is invoked from the SMS Administrator 
> console,
>     > to stop and start components.
>     >> Milestone Information MessageID: 2715
>     > SMS Inventory Data Loader has detected a resynchronization request 
> for
>     > agent SMS Inventory Agent. When an agent is specified, the
>     > resynchronization is planned only for items reported by that agent. 
> A
>     > resynchronization indicates that the current MIF file represents all
>     > inventory for the current machine. If any inventory is present in 
> the
>     > database that does not occur in the MIF file, SMS Inventory Data
>     > Loader deletes it (unless, as with an agent resynchronization, it 
> was
>     > reported by a different agent). If many resynchronizations occur, it
>     > indicates that inventory was lost at some
>     > point.
>     >> Milestone Information MessageID: 2705
>     > SMS Inventory Data Loader has finished processing 67 MIF files and 
> is
>     > terminating the MIF file processing thread.
>     > Each time the processing cycle completes, SMS Inventory Data Loader
>     > generates this message to report the number of MIF files it has
>     > processed.
>
>
>

Relevant Pages