Re: SBS 2003 SP1 installation seems to be stuck in loop

Tech-Archive recommends: Fix windows errors by optimizing your registry


"Mariette Knap [SBS MVP]" <mariette@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23q3X3cHZFHA.228@xxxxxxxxxxxxxxxxxxxxxxx
> In news:4299f1ad$0$54469$ed2619ec@xxxxxxxxxxxxxxxxxxxxxxxxxx,
>
> All those errors are related to the fact that you unplugged the network
> cable. What you see in the log is that it could not contact a domain
> controller. SBS acts really weird when the Lan nic does not have a device
> connected to it like a hub, switch or router. I would just run it again
> because parts of it were not installed. I do not expect problems.
>
> What you should do is check the event logs for errors after a clean boot.
> I assume the last boot went without problems?
>
> BTW, I have removed the line in our document where you were told to unplug
> the network cable. I am very sorry about this. I will contact the person
> who wrote this part.
>
> --
Hi Mariëtte

No need to apologise. It's very good of you to make the information
available in the first place, and I am more than happy to forgive the
occasional part of it that may have been less than 100% clear. No, the
person who really needs to apologise is whichever idiot at Microsoft wrote
software that would break so easily in the face of something as simple as an
unplugged network cable and then somehow thought it acceptable not to put in
a couple of extra lines of code at the start of the setup program to check
to see whether the network cable was in fact plugged in. Do they employ
trained programmers to write these service packs or do they try to save
money by getting people on some kind of young offender rehabilitation scheme
to do the programming?

Anyway, enough ranting.

I ran the setup again, and this time it gave me a rather pleasing message at
the end telling me that it had completed successfully. (I don't know how
long it took this time as I just left it to do its stuff last night and went
home, and came back to check on it this morning.) But being the suspicious
soul that I am, I checked the error log again (errorlog.txt in the same
location as last time), and there were rather a lot of entries there,
reproduced below:

[05/29/05,19:04:44] Intranet: [2] CClientX::InitializeModule found STS not
installed by SBS.
[05/29/05,19:04:46] Microsoft Integration: [2]
ISetupDataFile::GetPropertyValue() failed for account information in
ISetupManager::LoadPersistantComponentData(): filename =
d:\909b8b3939548439c7\CD1\Setup\I386\unattend.ini, component ID =
{829300FF-C155-11D2-92EF-00C04F79F1A8}\{DC3074B0-7DE8-43C5-B907-E9100CB5FFF2},
property name = (null)
[05/29/05,19:04:46] Microsoft Integration: [2]
ISetupDataFile::GetPropertyValue() failed for account information in
ISetupManager::LoadPersistantComponentData(): filename =
d:\909b8b3939548439c7\CD1\Setup\I386\unattend.ini, component ID =
{829300FF-C155-11D2-92EF-00C04F79F1A8}\{F333D98A-C152-11D2-92EF-00C04F79F1A8},
property name = (null)
[05/29/05,19:04:46] Microsoft Integration: [2]
ISetupComponent::SetInstallActionByUniqueID() failed in
ISetupManager::LoadPersistantComponentData(): component name =
{D6F52195-649D-4FAD-B43D-F4618503CFB2}\{EC4C6AFB-8B58-47AB-9CF0-6B18DD37872C},
action id = 4
[05/29/05,19:04:46] Microsoft Integration: [2]
ISetupComponent::SetInstallActionByUniqueID() failed in
ISetupManager::LoadPersistantComponentData(): component name =
{D6F52195-649D-4FAD-B43D-F4618503CFB2}\{54AB0622-F0EC-4E5E-AD73-22A7606EC8E7},
action id = 4
[05/29/05,19:04:47] setup.exe: [2] ISetupManager::AddGlobalCustomProperty
failed in ISetupManager::LoadPersistantData()
({c248d3e3-632d-4435-888a-83035c144737})
[05/29/05,19:04:49] Licensing: [2] Copying pidgen2.dll failed (error = 2).
Check your %system32% directory. Paths=(src="C:\Documents and
Settings\Administrator\Local Settings\Temp\SIT21794.tmp\pidgen2.dll",
dest="C:\WINDOWS\system32\pidgen2.dll")
[05/29/05,19:04:53] Licensing: [2] FindLinkByTarget failed to find the
licensing link with error [-2147024894].
[05/29/05,19:04:54] Licensing: [2] UpdateLinkPath failed to update the
licensing link with error [-2147024893].
[05/29/05,19:05:04] Server Configuration: [2] Admin: Couldn't get group
container for [LDAP://CN=Internet Users,OU=Security
Groups,OU=MyBusiness,DC=dianthus,DC=local]
[05/29/05,19:05:05] Server Configuration: [2] Admin: Couldn't get group
container for [LDAP://CN=Internet Users,OU=Security
Groups,OU=MyBusiness,DC=dianthus,DC=local]
[05/29/05,19:05:05] Server Configuration: [2] Admin: Couldn't get group
container for [LDAP://CN=Internet Users,OU=Security
Groups,OU=MyBusiness,DC=dianthus,DC=local]
[05/29/05,19:05:05] Server Configuration: [2] Admin: Couldn't get group
container for [LDAP://CN=Internet Users,OU=Security
Groups,OU=MyBusiness,DC=dianthus,DC=local]
[05/29/05,19:05:24] Administration: [2] switch on iAction got bogus value
CAdmin::Install()
[05/29/05,19:05:24] Microsoft Integration: [2]
ISetupComponent::Pre/Post/Install() failed in
ISetupManager::InstallManagerHelper(), id ==
[{EC4C6AFB-8B58-47AB-9CF0-6B18DD37872C}]
[05/29/05,19:05:24] Microsoft Integration: [2] Component error string not
specified in ISetupManager::AddToActionResultCollection(), id ==
[{EC4C6AFB-8B58-47AB-9CF0-6B18DD37872C}]
[05/29/05,19:05:29] Intranet: [2] switch on iAction got bogus value
CClientX::Install()
[05/29/05,19:05:29] Microsoft Integration: [2]
ISetupComponent::Pre/Post/Install() failed in
ISetupManager::InstallManagerHelper(), id ==
[{54AB0622-F0EC-4E5E-AD73-22A7606EC8E7}]
[05/29/05,19:05:30] Microsoft Integration: [2] Component error string not
specified in ISetupManager::AddToActionResultCollection(), id ==
[{54AB0622-F0EC-4E5E-AD73-22A7606EC8E7}]
[05/29/05,19:05:34] Client Deployment: [2] Failed to set DACL to C:\Program
Files\Microsoft Windows Small Business Server\ClientSetup\Clients [1]
[05/29/05,19:05:34] Client Deployment: [2] Failed to set DACL to
C:\ClientApps [1]
[05/29/05,19:06:03] Server Tools: [2] BCreateProcess of DUpdate.exe failed
with error [3]!.
[05/29/05,19:06:03] Server Tools: [2] RunOMADUpdate() failed with error
[80070003]
[05/29/05,19:06:22] Monitoring: [2] Probably mcw.exe was never run on this
computer, skipping upgrade...
[05/29/05,19:06:22] Monitoring: [2]
******* Error occured in Executing the following: *******
Provider=SQLOLEDB;Data Source=SERVER\SBSMonitoring;Initial
Catalog=SBSMonitoring;Trusted_Connection=Yes
Error Description: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does
not exist or access denied.
Error Number: -2147467259
Native Error Number: 17
Source: Microsoft OLE DB Provider for SQL Server
SQL State: 08001

[05/29/05,19:06:22] Monitoring: [2]
CMonitoring::UpdateSBSMonitoringDatabase() returned 0x80004005
[05/29/05,19:04:44] Intranet: [2] CClientX::InitializeModule found STS not
installed by SBS.
[05/29/05,19:04:46] Microsoft Integration: [2]
ISetupDataFile::GetPropertyValue() failed for account information in
ISetupManager::LoadPersistantComponentData(): filename =
d:\909b8b3939548439c7\CD1\Setup\I386\unattend.ini, component ID =
{829300FF-C155-11D2-92EF-00C04F79F1A8}\{DC3074B0-7DE8-43C5-B907-E9100CB5FFF2},
property name = (null)
[05/29/05,19:04:46] Microsoft Integration: [2]
ISetupDataFile::GetPropertyValue() failed for account information in
ISetupManager::LoadPersistantComponentData(): filename =
d:\909b8b3939548439c7\CD1\Setup\I386\unattend.ini, component ID =
{829300FF-C155-11D2-92EF-00C04F79F1A8}\{F333D98A-C152-11D2-92EF-00C04F79F1A8},
property name = (null)
[05/29/05,19:04:46] Microsoft Integration: [2]
ISetupComponent::SetInstallActionByUniqueID() failed in
ISetupManager::LoadPersistantComponentData(): component name =
{D6F52195-649D-4FAD-B43D-F4618503CFB2}\{EC4C6AFB-8B58-47AB-9CF0-6B18DD37872C},
action id = 4
[05/29/05,19:04:46] Microsoft Integration: [2]
ISetupComponent::SetInstallActionByUniqueID() failed in
ISetupManager::LoadPersistantComponentData(): component name =
{D6F52195-649D-4FAD-B43D-F4618503CFB2}\{54AB0622-F0EC-4E5E-AD73-22A7606EC8E7},
action id = 4
[05/29/05,19:04:47] setup.exe: [2] ISetupManager::AddGlobalCustomProperty
failed in ISetupManager::LoadPersistantData()
({c248d3e3-632d-4435-888a-83035c144737})
[05/29/05,19:04:49] Licensing: [2] Copying pidgen2.dll failed (error = 2).
Check your %system32% directory. Paths=(src="C:\Documents and
Settings\Administrator\Local Settings\Temp\SIT21794.tmp\pidgen2.dll",
dest="C:\WINDOWS\system32\pidgen2.dll")
[05/29/05,19:04:53] Licensing: [2] FindLinkByTarget failed to find the
licensing link with error [-2147024894].
[05/29/05,19:04:54] Licensing: [2] UpdateLinkPath failed to update the
licensing link with error [-2147024893].
[05/30/05,08:39:19] Intranet: [2] CClientX::InitializeModule found STS not
installed by SBS.
[05/30/05,08:39:21] Microsoft Integration: [2]
ISetupDataFile::GetPropertyValue() failed for account information in
ISetupManager::LoadPersistantComponentData(): filename = C:\Program
Files\Microsoft Integration\Windows Small Business Server 2003\REBOOT.INI,
component ID =
{829300FF-C155-11D2-92EF-00C04F79F1A8}\{DC3074B0-7DE8-43C5-B907-E9100CB5FFF2},
property name = (null)
[05/30/05,08:39:21] Microsoft Integration: [2]
ISetupDataFile::GetPropertyValue() failed for account information in
ISetupManager::LoadPersistantComponentData(): filename = C:\Program
Files\Microsoft Integration\Windows Small Business Server 2003\REBOOT.INI,
component ID =
{829300FF-C155-11D2-92EF-00C04F79F1A8}\{F333D98A-C152-11D2-92EF-00C04F79F1A8},
property name = (null)
[05/30/05,08:39:21] Microsoft Integration: [2]
ISetupComponent::SetInstallActionByUniqueID() failed in
ISetupManager::LoadPersistantComponentData(): component name =
{D6F52195-649D-4FAD-B43D-F4618503CFB2}, action id = 4
[05/30/05,08:39:21] Microsoft Integration: [2]
ISetupComponent::SetInstallActionByUniqueID() failed in
ISetupManager::LoadPersistantComponentData(): component name =
{D6F52195-649D-4FAD-B43D-F4618503CFB2}\{3340494C-2141-4DF3-9041-7504795CDF9D},
action id = 4
[05/30/05,08:39:21] Microsoft Integration: [2]
ISetupComponent::SetInstallActionByUniqueID() failed in
ISetupManager::LoadPersistantComponentData(): component name =
{D6F52195-649D-4FAD-B43D-F4618503CFB2}\{3585A6C7-38E7-4B4E-93A6-851C83F51B49},
action id = 4
[05/30/05,08:39:22] Microsoft Integration: [2]
ISetupComponent::SetInstallActionByUniqueID() failed in
ISetupManager::LoadPersistantComponentData(): component name =
{D6F52195-649D-4FAD-B43D-F4618503CFB2}\{0842297C-8833-450E-9385-08F822AC872E},
action id = 4
[05/30/05,08:39:22] Microsoft Integration: [2]
ISetupComponent::SetInstallActionByUniqueID() failed in
ISetupManager::LoadPersistantComponentData(): component name =
{D6F52195-649D-4FAD-B43D-F4618503CFB2}\{0842297C-8833-450E-9385-08F822AC872E}\{3E8E2F1F-C54D-4C0D-9516-1843DC5D9CB3},
action id = 4
[05/30/05,08:39:22] setup.exe: [2] ISetupManager::AddGlobalCustomProperty
failed in ISetupManager::LoadPersistantData()
({c248d3e3-632d-4435-888a-83035c144737})

I have no idea what any of that means. Should I be worried by it, or given
that everything now seems to work OK, can I just ignore it?

Many thanks
Adam



.

Quantcast