markclark1
asked on
Unable to install role on SBS2008
I have a Windows SBS2008 server at a clients and am due to roll out a few new PC's so decided to install WDS. It fails at the end with the following errors:
<Error>: Attempt to install Transport Server failed with error code 0x80070643. Fatal error occurred during installation.
<Error>: Attempt to install Deployment Server failed with error code 0x80070643. Fatal error occurred during installation.
In the System Log I get thousands of Info Event ID 4371 followed by thousands of errors, all event ID 4375 and following the format of Windows Servicing failed to complete the process of setting package ### into #### state and relates to what looks like windows updates.
Installing a feature produced thousands of the 4371 Event ID's but no errors followed and the install completed successfully.
Steps I have taken to try and resolve this:
Ran SFC /scannow
Installed KB947821 System Update Readiness Tool, logs show no errors
Run Server Manager as admin
Tried command line install in elevated command prompt: "ServerManagerCmd -install WDS"
Restarted the server (can you tell I am running out of ideas)
The command line install failed with the error "ServerManagerCommand.exe has stopped working" at stage 90/100 with the error below. Again accompanied with thousands of Error 4375's.
I would really like to find a solution to this which doesn't involve rebuilding the server!
<Error>: Attempt to install Transport Server failed with error code 0x80070643. Fatal error occurred during installation.
<Error>: Attempt to install Deployment Server failed with error code 0x80070643. Fatal error occurred during installation.
In the System Log I get thousands of Info Event ID 4371 followed by thousands of errors, all event ID 4375 and following the format of Windows Servicing failed to complete the process of setting package ### into #### state and relates to what looks like windows updates.
Installing a feature produced thousands of the 4371 Event ID's but no errors followed and the install completed successfully.
Steps I have taken to try and resolve this:
Ran SFC /scannow
Installed KB947821 System Update Readiness Tool, logs show no errors
Run Server Manager as admin
Tried command line install in elevated command prompt: "ServerManagerCmd -install WDS"
Restarted the server (can you tell I am running out of ideas)
The command line install failed with the error "ServerManagerCommand.exe has stopped working" at stage 90/100 with the error below. Again accompanied with thousands of Error 4375's.
Unhandled Exception: System.NotSupportedException: Culture 'en' is a neutral cul
ture. It cannot be used in formatting and parsing and therefore cannot be set as
the thread's current culture.
at System.Globalization.CultureInfo.CheckNeutral(CultureInfo culture)
at System.Globalization.CultureInfo.get_NumberFormat()
at System.Int32.ToString(String format, IFormatProvider provider)
at System.Text.StringBuilder.AppendFormat(IFormatProvider provider, String fo
rmat, Object[] args)
at System.String.Format(IFormatProvider provider, String format, Object[] arg
s)
at Microsoft.Windows.ServerManager.Common.ResourceManagerCache.GetFormattedSt
ring(String baseName, String resourceId, Object[] args)
at Microsoft.Windows.ServerManager.Common.Provider.GetSyncMessageHelper(XDocu
ment guest, SyncOperationKind syncOperationKind, SyncMessageType messageType, In
t32 errorCode, Boolean haveErrorCode, Boolean expandErrorCode, String additional
Message)
at Microsoft.Windows.ServerManager.Common.Provider.GetSyncMessage(XDocument g
uest, SyncOperationKind syncOperationKind, SyncMessageType messageType, Int32 er
rorCode)
at Microsoft.Windows.ServerManager.Common.Provider.FlushSync(SyncProgressHand
ler progressCallback)
at Microsoft.Windows.ServerManager.Common.Provider.FinalFlush(SyncProgressHan
dler progressCallback)
at Microsoft.SystemDefinitionModel.Transformation.Imperative.SyncEngine.Sync(
String rootIdentity, String[] eventClassIdentities)
at Microsoft.Windows.ServerManager.Utilities.ImperativeTransformationEngine.S
ync(ClientContext clientContext, ClassValue rootInstance, SyncProgressEventHandl
er progressHandler, String[] progressItems)
at Microsoft.Windows.ServerManager.ModelResult.CommitUpdates(ProgressUpdateCa
llback progressUpdateDelegate, String[] eventClassIdentities)
at Microsoft.Windows.ServerManager.ServerManagerCmd.ServerManagerCmd.SyncSyst
em()
at Microsoft.Windows.ServerManager.ServerManagerCmd.ServerManagerCmd.Process(
)
at Microsoft.Windows.ServerManager.ServerManagerCmd.Application.Main(String[]
args)
I would really like to find a solution to this which doesn't involve rebuilding the server!
First try to remove the Windows Process Activation Service, and then verify.
ASKER
Do you mean remove the service or just stop it? I was going to try and stop it previously but if I do it will stop the WWW Publishing Service which webmail is reliant on.
remove service from add remove feature.
ASKER
So just to confirm.
Remove Windows Process Activation Service
Try and install WDS
Reinstall Windows Process Activation Service
I presume IIS will stop working while Windows Process Activation Service is uninstalled. Are there any other potential issues?
Remove Windows Process Activation Service
Try and install WDS
Reinstall Windows Process Activation Service
I presume IIS will stop working while Windows Process Activation Service is uninstalled. Are there any other potential issues?
yes, Windows Process Activation service will cause IIS.
Okay before removing that service, please try to install other role and see that get install successfully
Okay before removing that service, please try to install other role and see that get install successfully
I hope you have already disabled UAC ( user Account control)
ASKER
As long as when I reinstall the Windows Process Activation Service IIS continues to work as it did that is no problem. I can arrange with the client for webmail to be down for a bit.
I did look at trying another role but I was reluctant to install any of the ones which aren't already installed. All I have uninstalled are AD Federation Services, AD Lightweight Directory Services, AD Rights Management, Application Server, UDDI and WDS.
UAC was turned off but was accidentally turned on again by the client. It didn't work when it was turned off though.
I did look at trying another role but I was reluctant to install any of the ones which aren't already installed. All I have uninstalled are AD Federation Services, AD Lightweight Directory Services, AD Rights Management, Application Server, UDDI and WDS.
UAC was turned off but was accidentally turned on again by the client. It didn't work when it was turned off though.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I have search lot, and most of the article is saying repair OS , if you can not repair or reinstall OS then go for it.
Just my two cents worth but why WDS at all. Does this customer have Volume Licensing for their desktops? I can't imagine any company running SBS needing to roll out but one or two PC's every year, if that. WDS seems like overkill!
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.