Re: Fresh Install Doesn't Work...Again!

Kim,
Local SQL 2000. I will verify the sql service account and get back.
Kevin

"Kim Oppalfens <MVP>" wrote:

If you are having similar problems, would you mind answering the questions I
posted to the previous question?

Local or remote sql?
Which user account is used to run the sql service?

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"Kevin - compuwin - oregon" <Kevincompuwinoregon@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message news:01B4D9F7-6608-4E1F-9F3B-2A7CFBFDFC4D@xxxxxxxxxxxxxxxx
Hi Kim,
I am having a similar problem. I was able to get sms 2003 sp1 to work in
lab
with no known problems. But in production only the local sms console will
work (using rdp). Administration workstations (xpsp2 and 2ksp4) will not
connect with the new sms2k3sp1 system. I can send logs if needed.
Kevin

"Kim Oppalfens <MVP>" wrote:

Is this an installation with a local or remote sql server?
If remote, does the sql server run using localsystem or a domain user?

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"Justin Harter" <jharter@xxxxxxxxxxxxxxxxx> wrote in message
news:0FFCE1F0-CA07-4CBD-A24D-482B6EFCF794@xxxxxxxxxxxxxxxx
I originally did a fresh install of SMS 2003 SP1 in a test environment
and
could not get it to work. After the install, I simply couldn't connect
to
the
administrator console. I tried everything I could find to get it to
work
to
no avail and I simply uninstalled and reinstalled and everything
magically
worked.

Now, I am attempting to install SMS 2003 SP1 in a production
environment
and
I am getting the EXACT same symptoms. I have tried uninstalling and
reinstalling, but it hasn't worked. Has anyone seen this before? I have
seen
other forum posts that elude to this exact same problem, but I don't
see
any
fixes or answers to why it happens.

I don't believe this is a windows server 2003 SP1 issue because I've
replicated the issue on a non SP1 box and an SP1 box...

I am attempting to connect from the server. I have confirmed that my
account
is a member of the SMS admins group. Also, I noticed that none of the
other
local groups created by SMS are populated (i.e.
SMS_SiteSystemToSiteServerConnection_NE1). Should they be?

I am NOT extending the schema because it already has been extended and
I've
already applied the appropriate permissions to the systems management
container.

Finally, attached is what is in the adminui.log

[1264][Tue 01/24/2006 11:13:31]:Info(ConnectServer): Connecting to
server
:
namespace \\SMSSERVER\root\sms
[1264][Tue 01/24/2006 11:13:31]:Info(ConnectServer): Connecting to
server.
Network : \\SMSSERVER\root\sms
[1264][Tue 01/24/2006 11:13:31]:Setting connection to NameSpace:
\\SMSSERVER\root\sms\site_NE1
[1264][Tue 01/24/2006 11:13:31]:Info(ConnectServer): Connecting to
server
:
namespace \\SMSSERVER\root\sms\site_NE1
[1264][Tue 01/24/2006 11:13:31]:Info(ConnectServer): Connecting to
server.
Network : \\SMSSERVER\root\sms\site_NE1
[1264][Tue 01/24/2006 11:14:11]:Wbem call failed:
T_WbemSyncEnumToContainer_Core, return code: -2147217389
[1264][Tue 01/24/2006 11:14:31]:Wbem call failed:
T_WbemSyncEnumToContainer_Core, return code: -2147217389
[1264][Tue 01/24/2006 11:14:31]:Query select SiteCode, SiteName,
ServerName,
BuildNumber from SMS_Site where ReportingSiteCode="" fails or returns
empty
resultset. Query select * from SMS_Identification also fails or returns
empty
resultset
[1264][Tue 01/24/2006 11:14:52]:Error: Possible UI connection error
code
is
-2147217389[0x80041013]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147217394 [0x8004100e]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147220997 [0x800401fb]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147217400 [0x80041008]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147217387 [0x80041015]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2146959352 [0x80080008]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147217379 [0x8004101d]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147023170 [0x800706be]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2146959355 [0x80080005]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147217396 [0x8004100c]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147217406 [0x80041002]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147023174 [0x800706ba]
[1264][Tue 01/24/2006 11:14:52]:Error: Possible UI connection error
code
is
-2147217389[0x80041013]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147217394 [0x8004100e]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147220997 [0x800401fb]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147217400 [0x80041008]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147217387 [0x80041015]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2146959352 [0x80080008]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147217379 [0x8004101d]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147023170 [0x800706be]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2146959355 [0x80080005]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147217396 [0x8004100c]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147217406 [0x80041002]
[1264][Tue 01/24/2006 11:14:52]:Info(AddToConnectionsMap): Checking
uiconnections.ini value of -2147023174 [0x800706ba]
[1264][Tue 01/24/2006 11:14:52]:Failed to execute method
GetProviderVersion!
[1264][Tue 01/24/2006 11:14:52]:Function GetProviderVersion returns
empty
string of ProviderVersion.
[1264][Tue 01/24/2006 11:15:12]:Wbem call failed:
T_WbemSyncEnumToContainer_Core, return code: -2147217389
[1264][Tue 01/24/2006 11:15:12]:We fail to get the ProviderVersion.
[1264][Tue 01/24/2006 11:15:12]:SiteCode - SiteServerName , Provider
Version
:
[1264][Tue 01/24/2006 11:15:12]:SiteBuildNumber is 1239
[1264][Tue 01/24/2006 11:15:12]:Failed to set the connection. error
code:
-2147217389



--
Justin Harter
::BLOG:: http://spaces.msn.com/members/jharter






.

Relevant Pages

  • MP Control Manager Issue
    ... Windows 2003 Standard Server ... SMS 2003 SP1 ... MP encountered an error when connecting to SQL Server. ... If using a standard SQL security account, ...
    (microsoft.public.sms.admin)
  • Re: SMS 2003 and real-time replication
    ... I am using nsi double-take to replicate the SQL ... data in real time to another server. ... recover from a failure quicker than what is outlined in the SMS Backup manual. ...
    (microsoft.public.sms.admin)
  • Re: sms2003 installation in windows2003 two cluster sql node
    ... > Systems Management Server 2003 cluster support requirements ... >> SMS Questions should be posted over in a different newsgroup in the ... >> In the case of SQL on clusters though Microsoft doesn't support it (or at ...
    (microsoft.public.sms.installer)
  • RE: Cannot isntall management point
    ... The SQL server is a member server, the SMS server is a domain controller. ... The MSSQL Service is running under a user account, ...
    (microsoft.public.sms.setup)
  • Re: sbs2003 sp1 questions
    ... well, I felt sharepoint which is heavily used should not be running the sbs box, so we moved to a server2003 box and talks to the sql server box. ... Sp1 for sbs2003 looks like a nice package but i have concerns as we already have deployed some if its components and don't have a typical bloated sbs2003 box, we have member servers take load of the sbs server etc. ...
    (microsoft.public.windows.server.sbs)
Loading