Mombu the Microsoft Forum sponsored links

Go Back   Mombu the Microsoft Forum > Microsoft > SMS 2003 Executive Errors
User Name
Password
REGISTER NOW! Mark Forums Read

sponsored links


Reply
 
1 17th April 16:44
dfcrj
External User
 
Posts: 1
Default SMS 2003 Executive Errors



I'm trying to upgrade to SMS 2003. Once I start the installation and
SMS begins the initial tests, I receive 1 failure, the "SMS Executive
is running". Once I open up the details it gives me this

"Test Result: Error
Error - Could not execute the test".

I've read the white papers on this particular test and followed the
instructions to verify the registry entrys. I've tried a site reset,
reapplying SP's. I only have one CAP, which is also the site server
itself. Is there anyway around this issue? I have no clue what to do
next beside trying to completely uninstall SMS
  Reply With Quote


  sponsored links


2 17th April 16:44
evan [msft]
External User
 
Posts: 1
Default SMS 2003 Executive Errors



Is there any more detail in smsdrw.log, or is that the error from
smsdrw.log? It can't be a sql problem since that test doesn't access sql.
What is the value of State (in the registry key specified in the white
paper)? If you don't have the rights to read the value, then drw won't
(since it runs under the logged-on user account) either and would probably
give that error.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
  Reply With Quote
3 17th April 16:44
dfcrj
External User
 
Posts: 1
Default SMS 2003 Executive Errors


Here is a section of the log file. The actual error I was viewing was
from the SMS 2003 console when it tried to perform the test. The white
papers say that the registry state needs to be 3, which it is. This
confirms that executive is runnning. However, it never makes it that
far, the test is never being performed.
<01-07-2004 11:43:32> Executing C function rule [18]: Verifies that
SMS EXECUTIVE service is running on the site server, and all site systems.
<01-07-2004 11:43:32> get registry info for SMS_EXECUTIVE
[Components\SMS_SITE_COMPONENT_MANAGER\Component
Servers\DFCDOT6\Components\SMS_EXECUTIVE] on site server [DFCDOT6],
site code [DOT]
\Components\SMS_EXECUTIVE] on site server [DFCDOT6], site code [DOT]
\Components\SMS_EXECUTIVE] on site server [DFCDOT6], site code [DOT]
<01-07-2004 11:43:32> Could not get registry info for SMS_EXECUTIVE
[Components\SMS_SITE_COMPONENT_MANAGER\Multisite Component
Servers\DFCDOT4\Components\SMS_EXECUTIVE] on site server [DFCDOT6], site code [DOT]
<01-07-2004 11:43:32> Rule failed
<01-07-2004 11:43:32> No rule event is generated
  Reply With Quote
4 23rd April 02:41
evan [msft]
External User
 
Posts: 1
Default SMS 2003 Executive Errors


Comparing your log with the code, drw interprets your
"Components\SMS_SITE_COMPONENT_MANAGER\Compone nt
Servers\DFCDOT6\Components\SMS_EXECUTIVE" State value to mean sm***ec is
running since it doesn't follow with an error message for that section.

The following part of the log shouldn't be like this (are you sure you
copied it right?):
\Components\SMS_EXECUTIVE] on site server [DFCDOT6], site code [DOT]
\Components\SMS_EXECUTIVE] on site server [DFCDOT6], site code [DOT]

The part that causes it to fail the test is
"Components\SMS_SITE_COMPONENT_MANAGER\Multisi te Component
Servers\DFCDOT4\Components\SMS_EXECUTIVE", as it can't read the registry.
When logged on using the same account with which you run drw, are you able
to read this registry key? There should be at least
"Components\SMS_SITE_COMPONENT_MANAGER\Multisi te Component
Servers" although there doesn't necessarily need to be any keys under it.
Are there any registry keys under yours, and if so what are they?

--
This posting is provided "AS IS" with no warranties, and confers no rights.

news:<Ou8stXt1DHA.2336@TK2MSFTNGP09.phx.gbl>...
  Reply With Quote
Reply


Thread Tools
Display Modes




Copyright © 2006 SmartyDevil.com - Dies Mies Jeschet Boenedoesef Douvema Enitemaus -
666