WSUS 3 upgrade failing

Discussion:

(too old to reply)

Bill

2007-07-17 21:50:02 UTC

Hello,

I've tried numerous tries to upgrade a WSUS 2 server to v3. Below is text
from the log file that seem to indicate the problem. I can't find any
information on these error codes or any resolution. Anybody know what the
fix is for this problem??

MSI (s) (3C:B0) [16:15:46:375]: Executing op:
ChangeMedia(MediaVolumeLabel=SELFCAB,MediaPrompt=Please insert the disk:
,MediaCabinet=SELFCAB,BytesPerTick=32768,CopierType=2,ModuleFileName=C:\WINDOWS\Installer\fc5cc.msi,,,,,IsFirstPhysicalMedia=0)
MSI (s) (3C:B0) [16:15:46:375]: Executing op: CacheSizeFlush(,)
MSI (s) (3C:B0) [16:15:46:375]: Executing op: InstallProtectedFiles(AllowUI=0)
MSI (s) (3C:B0) [16:15:46:375]: Executing op: ActionStart(Name=COPYWUAU,,)
MSI (s) (3C:B0) [16:15:46:421]: Executing op:
CustomActionSchedule(Action=COPYWUAU,ActionType=1025,Source=BinaryData,Target=CopyADMFile,CustomActionData=C:\WINDOWS\temp\WSUSSetup.log;C:\Program
Files\Update Services\adm)
MSI (s) (3C:68) [16:15:46:437]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSIAB.tmp, Entrypoint: CopyADMFile
MSI (s) (3C:B0) [16:15:46:656]: Executing op:
ActionStart(Name=CreateSmbRollback,,)
MSI (s) (3C:B0) [16:15:46:671]: Executing op:
CustomActionSchedule(Action=CreateSmbRollback,ActionType=3393,Source=BinaryData,Target=DropSmb,CustomActionData=WSUSTemp)
MSI (s) (3C:B0) [16:15:46:671]: Executing op: ActionStart(Name=CreateSmb,,)
MSI (s) (3C:B0) [16:15:46:671]: Executing op:
CustomActionSchedule(Action=CreateSmb,ActionType=3073,Source=BinaryData,Target=CreateSmb,CustomActionData=WSUSTempA
network share used by Local Publishing from a Remote WSUS Console
InstC:\Program Files\Update
Services\LogFiles\WSUSTemp02Administrators268435456WSUS
Administrators268435456)
MSI (s) (3C:EC) [16:15:46:687]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSIAC.tmp, Entrypoint: CreateSmb
MSI (s) (3C:8C) [16:15:46:687]: Generating random cookie.
MSI (s) (3C:8C) [16:15:46:734]: Created Custom Action Server with PID 3388
(0xD3C).
MSI (s) (3C:EC) [16:15:46:906]: Running as a service.
MSI (s) (3C:EC) [16:15:46:906]: Hello, I'm your 32bit Elevated custom action
server.
CreateSmb: Error 0x842: FShareExists return value unexpected.
CreateSmb: Error 0x80004005: Failed to create/modify file share: Err: 2114
CreateSmb: Error 0x80004005: failed to create to share: 'WSUSTemp'
MSI (s) (3C!F0) [16:16:44:640]: Product: Microsoft Windows Server Update
Services 3.0 -- Error 26301. Failed to create network share. (-2147467259
WSUSTemp )

Error 26301. Failed to create network share. (-2147467259 WSUSTemp )
MSI (s) (3C:B0) [16:16:44:765]: User policy value 'DisableRollback' is 0
MSI (s) (3C:B0) [16:16:44:765]: Machine policy value 'DisableRollback' is 0
Action ended 16:16:44: InstallFinalize. Return value 3.
MSI (s) (3C:B0) [16:16:44:765]: Executing op:
Header(Signature=1397708873,Version=301,Timestamp=921797097,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (3C:B0) [16:16:44:765]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (3C:B0) [16:16:44:781]: Executing op:
DialogInfo(Type=1,Argument=Microsoft Windows Server Update Services 3.0)
MSI (s) (3C:B0) [16:16:44:781]: Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])

2007-07-17 16:14:14 Success MWUSSetup Validating pre-requisites...
2007-07-17 16:14:14 Error MWUSSetup Failed to determine if an
higher version of WSUS is installed. Assuming it is not... (Error 0x80070002:
The system cannot find the file specified.)
2007-07-17 16:14:29 Success MWUSSetup Initializing installation
details
2007-07-17 16:14:29 Success MWUSSetup Installing ASP.Net
2007-07-17 16:15:09 Success MWUSSetup ASP.Net is installed
successfully
2007-07-17 16:15:09 Success MWUSSetup wYukon is already
installed on this machine
2007-07-17 16:15:09 Success MWUSSetup Installing WSUS...
2007-07-17 16:15:12 Success CustomActions.Dll Successfully set propery
of WSUS admin groups' full names
2007-07-17 16:15:13 Success CustomActions.Dll .Net framework path:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
2007-07-17 16:15:15 Success CustomActions.Dll Creating user group: WSUS
Reporters with Description: WSUS Administrators who can only run reports on
the Windows Server Update Services server.
2007-07-17 16:15:15 Success CustomActions.Dll Creating WSUS Reporters
user group
2007-07-17 16:15:15 Success CustomActions.Dll WSUS Reporters user group
already exists
2007-07-17 16:15:15 Success CustomActions.Dll Successfully created WSUS
Reporters user group
2007-07-17 16:15:15 Success CustomActions.Dll Creating user group: WSUS
Administrators with Description: WSUS Administrators can administer the
Windows Server Update Services server.
2007-07-17 16:15:15 Success CustomActions.Dll Creating WSUS
Administrators user group
2007-07-17 16:15:15 Success CustomActions.Dll WSUS Administrators user
group already exists
2007-07-17 16:15:15 Success CustomActions.Dll Successfully created WSUS
Administrators user group
2007-07-17 16:15:15 Success CustomActions.Dll Successfully created WSUS
user groups
2007-07-17 16:16:52 Error MWUSSetup InstallWsus: MWUS
Installation Failed (Error 0x80070643: Fatal error during installation.)
2007-07-17 16:16:52 Error MWUSSetup
CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643:
Fatal error during installation.)
2007-07-17 16:16:52 Error MWUSSetup CSetupDriver::LaunchSetup:
Setup failed (Error 0x80070643: Fatal error during installation.)
2007-07-17 16:16:57 Error MWUSSetup DoInstall: Wsus setup
failed (Error 0x80070643: Fatal error during installation.)

Lawrence Garvin (MVP)

2007-07-18 01:53:16 UTC

Permalink

Post by Bill
I've tried numerous tries to upgrade a WSUS 2 server to v3. Below is text
from the log file that seem to indicate the problem. I can't find any
information on these error codes or any resolution. Anybody know what the
fix is for this problem??

This appears to be the key issue.

Post by Bill
CreateSmb: Error 0x80004005: failed to create to share: 'WSUSTemp'
MSI (s) (3C!F0) [16:16:44:640]: Product: Microsoft Windows Server Update
Services 3.0 -- Error 26301. Failed to create network share. (-2147467259
WSUSTemp )

Are there any reasons why the installation program would be unable to create
a fileshare on the machine?

The WSUSTemp share would be at \Program Files\Update
Services\Logfiles\WSUSTemp

Perhaps you have restricted permissions on the \Program Files folder?
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

Everything you need for WSUS is at
http://www.microsoft.com/wsus

And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
....

Bill

2007-07-18 13:14:01 UTC

Permalink

That is not the problem unless there is an account that I am not aware of
that needs additional rights to the Program File directory. I am logged in
as a domain administrator on the server and my account is in the local
administrator group with full control rights to the program file directory
and all subfolders and files. If I browse that directory before clicking on
the error messages then I can see that the Update Services program directory
has been created and there are a number of subfolders and files within it.
After I click on the error messages the install rolls back the changes and
removes that directory.

Post by Lawrence Garvin (MVP)

This appears to be the key issue.

Are there any reasons why the installation program would be unable to create
a fileshare on the machine?
The WSUSTemp share would be at \Program Files\Update
Services\Logfiles\WSUSTemp
Perhaps you have restricted permissions on the \Program Files folder?
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://www.microsoft.com/wsus
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....

Bill

2007-07-18 18:38:01 UTC

Permalink

The problem was File and Print Sharing was not enabled. That was not enabled
in our WSUS 2 installation and that worked great. I also don't see the File
and Print Sharing requirement anywhere in the WSUS 3 Step by Step Guide or
Deployment Document. I guess Microsoft must assume everyone has that enabled
and failed to include it in the requirements. Now that it is at least
installed, I'll get it configured and then see if it works without it.

Post by Bill
That is not the problem unless there is an account that I am not aware of
that needs additional rights to the Program File directory. I am logged in
as a domain administrator on the server and my account is in the local
administrator group with full control rights to the program file directory
and all subfolders and files. If I browse that directory before clicking on
the error messages then I can see that the Update Services program directory
has been created and there are a number of subfolders and files within it.
After I click on the error messages the install rolls back the changes and
removes that directory.

Post by Lawrence Garvin (MVP)

This appears to be the key issue.

Are there any reasons why the installation program would be unable to create
a fileshare on the machine?
The WSUSTemp share would be at \Program Files\Update
Services\Logfiles\WSUSTemp
Perhaps you have restricted permissions on the \Program Files folder?
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://www.microsoft.com/wsus
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....

Lawrence Garvin (MVP)

2007-07-20 02:33:16 UTC

Permalink

Post by Bill
The problem was File and Print Sharing was not enabled. That was not enabled
in our WSUS 2 installation and that worked great. I also don't see the File
and Print Sharing requirement anywhere in the WSUS 3 Step by Step Guide or
Deployment Document. I guess Microsoft must assume everyone has that enabled
and failed to include it in the requirements. Now that it is at least
installed, I'll get it configured and then see if it works without it.

File and Print Sharing is enabled by default on all systems. It's absolutely
necessary to support administrative shares, which are also configured by
default on all systems.

When I pointed out an error "Failed to create network share", and asked the
question: "Are there any reasons why the installation program would be
unable to create a fileshare on the machine?", it never occurred to you that
your intentional disabling of File & Print Sharing might be related?

Heck. _I_ assumed you had it enabled! You didn't tell us you'd severely
customized the default configuration of the operating system.

I'm glad you found the reason.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

Everything you need for WSUS is at
http://www.microsoft.com/wsus

And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
....

unknown

2010-01-27 19:06:30 UTC

Permalink

The solution presented here is not accurate.

I experienced the same issue repeatedly on Windows 2003 Server SP2 while installing WSUS 3.0 SP2.

Enabling File and Printer Sharing had no affect.

The problem occurs when the "server" service is disabled or stopped.

Once I started the "Server" service the installation completed without generating the WSUSTemp create error.

File and Printer Sharing was disabled during the successful installation.

Lawrence Garvin \(MVP\) wrote:

Re: WSUS 3 upgrade failing
19-Jul-07

"Bill" <***@discussions.microsoft.com> wrote in message news:7F567CB4-DD39-42C7-BECD-***@microsoft.com..

File and Print Sharing is enabled by default on all systems. It's absolutely
necessary to support administrative shares, which are also configured by
default on all systems

When I pointed out an error "Failed to create network share", and asked the
question: "Are there any reasons why the installation program would be
unable to create a fileshare on the machine?", it never occurred to you that
your intentional disabling of File & Print Sharing might be related

Heck. _I_ assumed you had it enabled! You didn't tell us you'd severely
customized the default configuration of the operating system

I'm glad you found the reason

--
Lawrence Garvin, M.S., MCTS, MC
Independent WSUS Evangelis
MVP-Software Distribution (2005-2007
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36

Everything you need for WSUS is a
http://www.microsoft.com/wsu

And, almost everything else is a
http://wsusinfo.onsitechsolutions.co
....

Previous Posts In This Thread:

On Tuesday, July 17, 2007 5:50 PM
Bil wrote:

WSUS 3 upgrade failing
Hello

I've tried numerous tries to upgrade a WSUS 2 server to v3. Below is text
from the log file that seem to indicate the problem. I can't find any
information on these error codes or any resolution. Anybody know what the
fix is for this problem?

MSI (s) (3C:B0) [16:15:46:375]: Executing op:
ChangeMedia(MediaVolumeLabel=SELFCAB,MediaPrompt=Please insert the disk:
,MediaCabinet=SELFCAB,BytesPerTick=32768,CopierType=2,ModuleFileName=C:\WINDOWS\Installer\fc5cc.msi,,,,,IsFirstPhysicalMedia=0
MSI (s) (3C:B0) [16:15:46:375]: Executing op: CacheSizeFlush(,
MSI (s) (3C:B0) [16:15:46:375]: Executing op: InstallProtectedFiles(AllowUI=0
MSI (s) (3C:B0) [16:15:46:375]: Executing op: ActionStart(Name=COPYWUAU,,
MSI (s) (3C:B0) [16:15:46:421]: Executing op:
CustomActionSchedule(Action=COPYWUAU,ActionType=1025,Source=BinaryData,Target=CopyADMFile,CustomActionData=C:\WINDOWS\temp\WSUSSetup.log;C:\Program
Files\Update Services\adm
MSI (s) (3C:68) [16:15:46:437]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSIAB.tmp, Entrypoint: CopyADMFil
MSI (s) (3C:B0) [16:15:46:656]: Executing op:
ActionStart(Name=CreateSmbRollback,,
MSI (s) (3C:B0) [16:15:46:671]: Executing op:
CustomActionSchedule(Action=CreateSmbRollback,ActionType=3393,Source=BinaryData,Target=DropSmb,CustomActionData=WSUSTemp
MSI (s) (3C:B0) [16:15:46:671]: Executing op: ActionStart(Name=CreateSmb,,
MSI (s) (3C:B0) [16:15:46:671]: Executing op:
CustomActionSchedule(Action=CreateSmb,ActionType=3073,Source=BinaryData,Target=CreateSmb,CustomActionData=WSUSTemp??A
network share used by Local Publishing from a Remote WSUS Console
Inst??C:\Program Files\Update
Services\LogFiles\WSUSTemp??0??2??Administrators??268435456??WSUS
Administrators??268435456
MSI (s) (3C:EC) [16:15:46:687]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSIAC.tmp, Entrypoint: CreateSm
MSI (s) (3C:8C) [16:15:46:687]: Generating random cookie
MSI (s) (3C:8C) [16:15:46:734]: Created Custom Action Server with PID 3388
(0xD3C)
MSI (s) (3C:EC) [16:15:46:906]: Running as a service
MSI (s) (3C:EC) [16:15:46:906]: Hello, I'm your 32bit Elevated custom action
server
CreateSmb: Error 0x842: FShareExists return value unexpected
CreateSmb: Error 0x80004005: Failed to create/modify file share: Err: 211
CreateSmb: Error 0x80004005: failed to create to share: 'WSUSTemp
MSI (s) (3C!F0) [16:16:44:640]: Product: Microsoft Windows Server Update
Services 3.0 -- Error 26301. Failed to create network share. (-2147467259
WSUSTemp )

Error 26301. Failed to create network share. (-2147467259 WSUSTemp )
MSI (s) (3C:B0) [16:16:44:765]: User policy value 'DisableRollback' is 0
MSI (s) (3C:B0) [16:16:44:765]: Machine policy value 'DisableRollback' is 0
Action ended 16:16:44: InstallFinalize. Return value 3.
MSI (s) (3C:B0) [16:16:44:765]: Executing op:
Header(Signature=1397708873,Version=301,Timestamp=921797097,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (3C:B0) [16:16:44:765]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (3C:B0) [16:16:44:781]: Executing op:
DialogInfo(Type=1,Argument=Microsoft Windows Server Update Services 3.0)
MSI (s) (3C:B0) [16:16:44:781]: Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])

2007-07-17 16:14:14 Success MWUSSetup Validating pre-requisites...
2007-07-17 16:14:14 Error MWUSSetup Failed to determine if an
higher version of WSUS is installed. Assuming it is not... (Error 0x80070002:
The system cannot find the file specified.)
2007-07-17 16:14:29 Success MWUSSetup Initializing installation
details
2007-07-17 16:14:29 Success MWUSSetup Installing ASP.Net
2007-07-17 16:15:09 Success MWUSSetup ASP.Net is installed
successfully
2007-07-17 16:15:09 Success MWUSSetup wYukon is already
installed on this machine
2007-07-17 16:15:09 Success MWUSSetup Installing WSUS...
2007-07-17 16:15:12 Success CustomActions.Dll Successfully set propery
of WSUS admin groups' full names
2007-07-17 16:15:13 Success CustomActions.Dll .Net framework path:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
2007-07-17 16:15:15 Success CustomActions.Dll Creating user group: WSUS
Reporters with Description: WSUS Administrators who can only run reports on
the Windows Server Update Services server.
2007-07-17 16:15:15 Success CustomActions.Dll Creating WSUS Reporters
user group
2007-07-17 16:15:15 Success CustomActions.Dll WSUS Reporters user group
already exists
2007-07-17 16:15:15 Success CustomActions.Dll Successfully created WSUS
Reporters user group
2007-07-17 16:15:15 Success CustomActions.Dll Creating user group: WSUS
Administrators with Description: WSUS Administrators can administer the
Windows Server Update Services server.
2007-07-17 16:15:15 Success CustomActions.Dll Creating WSUS
Administrators user group
2007-07-17 16:15:15 Success CustomActions.Dll WSUS Administrators user
group already exists
2007-07-17 16:15:15 Success CustomActions.Dll Successfully created WSUS
Administrators user group
2007-07-17 16:15:15 Success CustomActions.Dll Successfully created WSUS
user groups
2007-07-17 16:16:52 Error MWUSSetup InstallWsus: MWUS
Installation Failed (Error 0x80070643: Fatal error during installation.)
2007-07-17 16:16:52 Error MWUSSetup
CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643:
Fatal error during installation.)
2007-07-17 16:16:52 Error MWUSSetup CSetupDriver::LaunchSetup:
Setup failed (Error 0x80070643: Fatal error during installation.)
2007-07-17 16:16:57 Error MWUSSetup DoInstall: Wsus setup
failed (Error 0x80070643: Fatal error during installation.)

On Tuesday, July 17, 2007 9:53 PM
Lawrence Garvin \(MVP\) wrote:

Re: WSUS 3 upgrade failing
"Bill" <***@discussions.microsoft.com> wrote in message news:C4D60A90-B14A-498E-9CB2-***@microsoft.com...

This appears to be the key issue.

Are there any reasons why the installation program would be unable to create
a fileshare on the machine?

The WSUSTemp share would be at \Program Files\Update
Services\Logfiles\WSUSTemp

Perhaps you have restricted permissions on the \Program Files folder?
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

Everything you need for WSUS is at
http://www.microsoft.com/wsus

And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....

On Wednesday, July 18, 2007 9:14 AM
Bil wrote:

That is not the problem unless there is an account that I am not aware of that
That is not the problem unless there is an account that I am not aware of
that needs additional rights to the Program File directory. I am logged in
as a domain administrator on the server and my account is in the local
administrator group with full control rights to the program file directory
and all subfolders and files. If I browse that directory before clicking on
the error messages then I can see that the Update Services program directory
has been created and there are a number of subfolders and files within it.
After I click on the error messages the install rolls back the changes and
removes that directory.

"Lawrence Garvin (MVP)" wrote:

On Wednesday, July 18, 2007 2:38 PM
Bil wrote:

The problem was File and Print Sharing was not enabled.
The problem was File and Print Sharing was not enabled. That was not enabled
in our WSUS 2 installation and that worked great. I also don't see the File
and Print Sharing requirement anywhere in the WSUS 3 Step by Step Guide or
Deployment Document. I guess Microsoft must assume everyone has that enabled
and failed to include it in the requirements. Now that it is at least
installed, I'll get it configured and then see if it works without it.

"Bill" wrote:

On Thursday, July 19, 2007 10:33 PM
Lawrence Garvin \(MVP\) wrote:

Re: WSUS 3 upgrade failing
"Bill" <***@discussions.microsoft.com> wrote in message news:7F567CB4-DD39-42C7-BECD-***@microsoft.com...

File and Print Sharing is enabled by default on all systems. It's absolutely
necessary to support administrative shares, which are also configured by
default on all systems.

When I pointed out an error "Failed to create network share", and asked the
question: "Are there any reasons why the installation program would be
unable to create a fileshare on the machine?", it never occurred to you that
your intentional disabling of File & Print Sharing might be related?

Heck. _I_ assumed you had it enabled! You didn't tell us you'd severely
customized the default configuration of the operating system.

I'm glad you found the reason.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

Everything you need for WSUS is at
http://www.microsoft.com/wsus

And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....

Submitted via EggHeadCafe - Software Developer Portal of Choice
Run the command or application in the Security context of specified user
http://www.eggheadcafe.com/tutorials/aspnet/67e98a96-be06-4f84-bc8c-17c9e7073bfd/run-the-command-or-applic.aspx

unknown

2010-01-27 19:18:05 UTC

Permalink

To be clear:

File and Printer sharing is an option you can enable or disable on a network interface in Windows Server 2003.

The "server" service supports File and Printer sharing and is found in the services option of Administrative Tools.

Some administrators disable the server service when Microsoft network shares are not required in order to avoid the spread of viruses like conficker.

Don Freeman wrote:

WSUS 3 upgrade failing (WSUStemp error)
27-Jan-10

The solution presented here is not accurate.

I experienced the same issue repeatedly on Windows 2003 Server SP2 while installing WSUS 3.0 SP2.

Enabling File and Printer Sharing had no affect.

The problem occurs when the "server" service is disabled or stopped.

Once I started the "Server" service the installation completed without generating the WSUSTemp create error.

File and Printer Sharing was disabled during the successful installation.

Previous Posts In This Thread:

Submitted via EggHeadCafe - Software Developer Portal of Choice
Sets of "101 Code Samples" for Visual Studio and SQL Server
http://www.eggheadcafe.com/tutorials/aspnet/1e83d270-1a5b-43ac-973b-73eaff4e5881/sets-of-101-code-samples.aspx

Lawrence Garvin [MVP]

2010-01-29 17:59:17 UTC

Permalink

Post by unknown
The solution presented here is not accurate.
I experienced the same issue repeatedly on Windows 2003 Server SP2 while
installing WSUS 3.0 SP2.
Enabling File and Printer Sharing had no affect.
The problem occurs when the "server" service is disabled or stopped.

Okay.. so my answer still doesn't change... the *SERVER* service is also
assumed to be running on a *SERVER* machine unless specified otherwise.

So in your case, *your* assumption that the answer presented for the
specific problem presented should be the absolute answer to your scenario
was probably somewhat inaccurate. I assumed, given the original scenario,
that the issue was specifically FPS, and in 99.99% of the cases that will be
the exact issue. In your scenario apparently the issue was an upstream
dependency, the SERVER service itself.

This is also why we encourage new posters to post their scenarios in a NEW
thread, with THEIR specific scenarios, because, in fact, rarely is it the
case that poster 'B' has the same exact scenario as poster 'A', and in this
case, that appears to have been the case for you.

In any event, the fundamental point here is that if a NON-standard
configuration exists on a server when trying to install a standard service
(like WSUS), the very first thing that should be considered is the potential
impact of the non-standard configuration. In fact, one of the primary steps
in any troubleshooting scenario, particularly on servers, is to identify
services that are not running that should be.

The SERVER service not running on a Windows Server operating system is a
pretty significant configuration change, and will likely cause problems with
many scenarios, except a very few in which that service will never be
required.

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2010)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin