RE: SBS 2003 SP1 Update Issue
- From: Stripes <Stripes@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 14 Mar 2006 12:11:28 -0800
Hi Crina,
You will find the answers to your questions below. As for the log files, I
am happy to send them but I cannot find a way to attach them to a post.
Please provide these instructions or provide an e-mail address that I can use.
I have reviewed the error log and find the error: Component error string
not specified in ISetupManager::AddToActionResultCollection(). As I know,
the issue may be caused by the Client Deployment components of Server Tools
were not installed in the original installation of SBS. Please try to
install it and then complete the installation of SBS SP1.
I installed the Client Tools and then ran SP1 again with same result.
If the issue still occurs, please see the following: Before we install the
SBS 2003 SP1 onto the server, we need to make sure that the required
components such as Windows server 2003 SP1, Exchange 2003 SP1, WSS SP1 have
been installed. Please refer to the release note and double check the
install procedure:
http://www.microsoft.com/downloads/details.aspx?FamilyId=022677CC-F5AC-4BFB-
9AD0-454E89CB98BB&displaylang=en
Would you please help me confirm if you have strictly followed the document
to install SBS SP1?
Yes I was following it when performing the update.
For SBS 2003 Standard:
http://download.microsoft.com/download/2/e/9/2e902d14-da2e-43ba-8bd6-6d258f5
356b6/SP1Setup_std.htm
For SBS 2003 Premium:
http://download.microsoft.com/download/2/e/9/2e902d14-da2e-43ba-8bd6-6d258f5
356b6/SP1Setup_prem.htm
Getting Started: Windows Small Business Server 2003 with SP1
http://download.microsoft.com/download/9/a/3/9a306a75-e7da-461f-996d-7b93e09
948ee/GettingStarted_Combined.doc
More reference:
http://www.smallbizserver.net/Default.aspx?tabid=236
I reviewed the above before hand as well.
If you have followed the steps, please help me to gather the following
information to isolate the problem:
1. Do you have received the prompt box which indicated the operation has
been finished successfully? What are the error messages you receive when
you install SP1?
'Windows Small Business Server Service Pack 1 Setup has encountered an
error. For more information, review the most recent entry in the Setup error
log in C:\Program Files\Microsoft Integration\Windows Small Business Server
2003\Logs\setup.log. Then correct the error and re run Service Pack 1 Setup
again.'
2. You can check if SBS 2003 SP1 is installed through taking a look at this
registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\ServicePackNumber
It should be set to "1" if the server is at SP1.
There is no entry.
In addition, you may check what SP level the following
components are at by using the steps respectively:
- Windows Server 2003: Right-click on My Computer and
choose Properties; or run "winver".
It indicates SP1
- Exchange Server 2003: Click Start -> All Programs ->
Microsoft Exchange -> System Manager, expand Servers, right-click on
servername and choose Properties.
Inidcates SP2
- SQL Server 2000: Click Start -> All Programs -> Microsoft
SQL Server -> Enterprise Manager, right-click servername under SQL Server
group and choose Properties.
I have no Enterprise Manager. I tried to install SQL2kSP4 and it tells me I
do not have SQL2k. I tried an SQL7SP and I get the same. The SQL Server
Service Monitor is V8.0
3. Do you see "Microsoft Windows Server 2003 for Small Business Server
Service Pack 1" when you view properties of My Computer?
Yes
I should also note that my update attempts are in response to the problems
recently encountered when adding a new user. It seems that Exchange never
properly adds the user to the Exchange Address List. When attempting to
connect via Ouylook 2003 on the LAN, Outlook or the Mail CP reports that the
name col dnot be resolved. I am hopeful that once the update issues are
resolved so will the new user one.
I do sincerely appreeciate your time and effort in assisting me with this
issue.
Stripes
""Crina Li"" wrote:
Hi Stripes,
Thank you for posting in SBS newsgroup.
From the description, I understand you have received error when you install
SBS service pack 1 package. If I have misunderstood your concerns, please
do not hesitate to let me know.
I have reviewed the error log and find the error: Component error string
not specified in ISetupManager::AddToActionResultCollection(). As I know,
the issue may be caused by the Client Deployment components of Server Tools
were not installed in the original installation of SBS. Please try to
install it and then complete the installation of SBS SP1.
If the issue still occurs, please see the following: Before we install the
SBS 2003 SP1 onto the server, we need to make sure that the required
components such as Windows server 2003 SP1, Exchange 2003 SP1, WSS SP1 have
been installed. Please refer to the release note and double check the
install procedure:
http://www.microsoft.com/downloads/details.aspx?FamilyId=022677CC-F5AC-4BFB-
9AD0-454E89CB98BB&displaylang=en
Would you please help me confirm if you have strictly followed the document
to install SBS SP1?
For SBS 2003 Standard:
http://download.microsoft.com/download/2/e/9/2e902d14-da2e-43ba-8bd6-6d258f5
356b6/SP1Setup_std.htm
For SBS 2003 Premium:
http://download.microsoft.com/download/2/e/9/2e902d14-da2e-43ba-8bd6-6d258f5
356b6/SP1Setup_prem.htm
Getting Started: Windows Small Business Server 2003 with SP1
http://download.microsoft.com/download/9/a/3/9a306a75-e7da-461f-996d-7b93e09
948ee/GettingStarted_Combined.doc
More reference:
http://www.smallbizserver.net/Default.aspx?tabid=236
If you have followed the steps, please help me to gather the following
information to isolate the problem:
1. Do you have received the prompt box which indicated the operation has
been finished successfully? What are the error messages you receive when
you install SP1?
2. You can check if SBS 2003 SP1 is installed through taking a look at this
registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\ServicePackNumber
It should be set to "1" if the server is at SP1.
In addition, you may check what SP level the following
components are at by using the steps respectively:
- Windows Server 2003: Right-click on My Computer and
choose Properties; or run "winver".
- Exchange Server 2003: Click Start -> All Programs ->
Microsoft Exchange -> System Manager, expand Servers, right-click on
servername and choose Properties.
- SQL Server 2000: Click Start -> All Programs -> Microsoft
SQL Server -> Enterprise Manager, right-click servername under SQL Server
group and choose Properties.
3. Do you see "Microsoft Windows Server 2003 for Small Business Server
Service Pack 1" when you view properties of My Computer?
4. Also, please post all the logs in the following folders to newsgroup. If
the file is too large, you can zip it. I need the whole content in the
folders for research.
Windows Small Business Server 2003 SP1 (Q885918):
C:\Windows\KB885918.log
Remainder of the Small Business Server Setup Logs: C:\Program
Files\Microsoft Integration\Windows Small Business Server 2003\Logs
I appreciate your time and cooperation. If anything is unclear, please feel
free to let me know. I am looking forward to hearing from you!
Best regards,
Crina Li (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: SBS 2003 SP1 Update Issue
|| From: =?Utf-8?B?U3RyaXBlcw==?= <Stripes@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: SBS 2003 SP1 Update Issue
| Date: Sun, 12 Mar 2006 19:21:26 -0800
| | Newsgroups: microsoft.public.windows.server.sbs
| |
| WHen applying SP1 to SBS 2003, I receive an error mnessage during the
| install. Entries from the log are shown below. How do I resolve and get
SP1
| to completely install/update?
|
|
| [03/12/06,22:13:29] Microsoft Integration: [2]
| ISetupDataFile::GetPropertyValue() failed for account information in
| ISetupManager::LoadPersistantComponentData(): filename =
| d:\478fd2643f7812d46a94b0fae1503573\CD1\Setup\I386\unattend.ini,
component ID
| =
|
{829300FF-C155-11D2-92EF-00C04F79F1A8}\{DC3074B0-7DE8-43C5-B907-E9100CB5FFF2
}, property name = (null)
| [03/12/06,22:13:29] Microsoft Integration: [2]
| ISetupDataFile::GetPropertyValue() failed for account information in
| ISetupManager::LoadPersistantComponentData(): filename =
| d:\478fd2643f7812d46a94b0fae1503573\CD1\Setup\I386\unattend.ini,
component ID
| =
|
{829300FF-C155-11D2-92EF-00C04F79F1A8}\{F333D98A-C152-11D2-92EF-00C04F79F1A8
}, property name = (null)
| [03/12/06,22:13:30] Microsoft Integration: [2]
| ISetupComponent::SetInstallActionByUniqueID() failed in
| ISetupManager::LoadPersistantComponentData(): component name =
| {D6F52195-649D-4FAD-B43D-F4618503CFB2}, action id = 4
| [03/12/06,22:13:30] Microsoft Integration: [2]
| ISetupComponent::SetInstallActionByUniqueID() failed in
| ISetupManager::LoadPersistantComponentData(): component name =
|
{D6F52195-649D-4FAD-B43D-F4618503CFB2}\{EC4C6AFB-8B58-47AB-9CF0-6B18DD37872C
}, action id = 4
| [03/12/06,22:13:30] Microsoft Integration: [2]
| ISetupComponent::SetInstallActionByUniqueID() failed in
| ISetupManager::LoadPersistantComponentData(): component name =
|
{D6F52195-649D-4FAD-B43D-F4618503CFB2}\{3340494C-2141-4DF3-9041-7504795CDF9D
}, action id = 4
| [03/12/06,22:13:30] Microsoft Integration: [2]
| ISetupComponent::SetInstallActionByUniqueID() failed in
| ISetupManager::LoadPersistantComponentData(): component name =
|
{D6F52195-649D-4FAD-B43D-F4618503CFB2}\{3585A6C7-38E7-4B4E-93A6-851C83F51B49
}, action id = 4
| [03/12/06,22:13:30] Microsoft Integration: [2]
| ISetupComponent::SetInstallActionByUniqueID() failed in
| ISetupManager::LoadPersistantComponentData(): component name =
|
{D6F52195-649D-4FAD-B43D-F4618503CFB2}\{54AB0622-F0EC-4E5E-AD73-22A7606EC8E7
}, action id = 4
| [03/12/06,22:13:30] Microsoft Integration: [2]
| ISetupComponent::SetInstallActionByUniqueID() failed in
| ISetupManager::LoadPersistantComponentData(): component name =
|
{D6F52195-649D-4FAD-B43D-F4618503CFB2}\{0842297C-8833-450E-9385-08F822AC872E
}, action id = 4
| [03/12/06,22:13:31] setup.exe: [2] ISetupManager::AddGlobalCustomProperty
| failed in ISetupManager::LoadPersistantData()
| ({c248d3e3-632d-4435-888a-83035c144737})
| [03/12/06,22:13:35] Licensing: [2] Copying pidgen2.dll failed (error =
2).
| Check your %system32% directory.
| Paths=(src="D:\Temp\SIT37160.tmp\pidgen2.dll",
| dest="C:\WINDOWS\system32\pidgen2.dll")
| [03/12/06,22:13:38] Licensing: [2] FindLinkByTarget failed to find the
| licensing link with error [-2147024894].
| [03/12/06,22:13:38] Licensing: [2] UpdateLinkPath failed to update the
| licensing link with error [-2147024893].
| [03/12/06,22:13:54] Server Configuration: [2] Admin: Couldn't get group
| container for [LDAP://CN=Internet Users,OU=Security
| Groups,OU=MyBusiness,DC=smallbusiness,DC=local]
| [03/12/06,22:13:54] Server Configuration: [2] Admin: Couldn't get group
| container for [LDAP://CN=Internet Users,OU=Security
| Groups,OU=MyBusiness,DC=smallbusiness,DC=local]
| [03/12/06,22:13:55] Server Configuration: [2] Admin: Couldn't get group
| container for [LDAP://CN=Internet Users,OU=Security
| Groups,OU=MyBusiness,DC=smallbusiness,DC=local]
| [03/12/06,22:13:55] Server Configuration: [2] Admin: Couldn't get group
| container for [LDAP://CN=Internet Users,OU=Security
| Groups,OU=MyBusiness,DC=smallbusiness,DC=local]
| [03/12/06,22:13:56] Administration: [2] switch on iAction got bogus value
| CAdmin::Install()
| [03/12/06,22:13:56] Microsoft Integration: [2]
| ISetupComponent::Pre/Post/Install() failed in
| ISetupManager::InstallManagerHelper(), id ==
| [{EC4C6AFB-8B58-47AB-9CF0-6B18DD37872C}]
| [03/12/06,22:13:56] Microsoft Integration: [2] Component error string not
| specified in ISetupManager::AddToActionResultCollection(), id ==
| [{EC4C6AFB-8B58-47AB-9CF0-6B18DD37872C}]
| [03/12/06,22:13:56] Monitoring: [2] switch on iAction got bogus value
| CMonitoring::Install()
| [03/12/06,22:13:56] Microsoft Integration: [2]
| ISetupComponent::Pre/Post/Install() failed in
| ISetupManager::InstallManagerHelper(), id ==
| [{3340494C-2141-4DF3-9041-7504795CDF9D}]
| [03/12/06,22:13:56] Microsoft Integration: [2] Component error string not
| specified in ISetupManager::AddToActionResultCollection(), id ==
| [{3340494C-2141-4DF3-9041-7504795CDF9D}]
| [03/12/06,22:13:56] Networking: [2] switch on iAction got bogus value
| CConnectivity::Install()
| [03/12/06,22:13:56] Microsoft Integration: [2]
| ISetupComponent::Pre/Post/Install() failed in
| ISetupManager::InstallManagerHelper(), id ==
| [{3585A6C7-38E7-4B4E-93A6-851C83F51B49}]
| [03/12/06,22:13:56] Microsoft Integration: [2] Component error string not
| specified in ISetupManager::AddToActionResultCollection(), id ==
| [{3585A6C7-38E7-4B4E-93A6-851C83F51B49}]
| [03/12/06,22:13:57] Intranet: [2] switch on iAction got bogus value
| CClientX::Install()
| [03/12/06,22:13:57] Microsoft Integration: [2]
| ISetupComponent::Pre/Post/Install() failed in
| ISetupManager::InstallManagerHelper(), id ==
| [{54AB0622-F0EC-4E5E-AD73-22A7606EC8E7}]
| [03/12/06,22:13:57] Microsoft Integration: [2] Component error string not
| specified in ISetupManager::AddToActionResultCollection(), id ==
| [{54AB0622-F0EC-4E5E-AD73-22A7606EC8E7}]
| [03/12/06,22:13:57] Client Deployment: [2] switch on iAction got bogus
value
| CClientSetup::Install()
| [03/12/06,22:13:57] Microsoft Integration: [2]
| ISetupComponent::Pre/Post/Install() failed in
| ISetupManager::InstallManagerHelper(), id ==
| [{0842297C-8833-450E-9385-08F822AC872E}]
| [03/12/06,22:13:57] Microsoft Integration: [2] Component error string not
| specified in ISetupManager::AddToActionResultCollection(), id ==
| [{0842297C-8833-450E-9385-08F822AC872E}]
| [03/12/06,22:14:05] Server Tools: [2] BCreateProcess of DUpdate.exe
failed
| with error [3]!.
| [03/12/06,22:14:05] Server Tools: [2] RunOMADUpdate() failed with error
| [80070003]
| [03/12/06,22:14:16] Microsoft Office Outlook 2003 (Service Pack 1): [2]
| Error applying Outlook SP1 MSP file to AIP
|
(C:\ClientApps\Office2003_SP1\OFFICE2003_SP1.MSP/C:\CLIENT~1\outlook2003\OUT
LS11.msi), (2)
Log Files:
.
- References:
- SBS 2003 SP1 Update Issue
- From: Stripes
- RE: SBS 2003 SP1 Update Issue
- From: "Crina Li"
- SBS 2003 SP1 Update Issue
- Prev by Date: Re: SBS 2k3 reboots every week same day, same time
- Next by Date: RE: Post SP1 SBS2003 CEICW Fails
- Previous by thread: RE: SBS 2003 SP1 Update Issue
- Next by thread: Re: Windows Mobile device connecting to SBS2003
- Index(es):
Relevant Pages
|
