RE: Windows Server Update Services 2.0 Error
- From: Richard Johansson, Parnasso <RichardJohanssonParnasso@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 4 Feb 2008 02:09:01 -0800
Hi again Manfred!
I examined the configuration for the WSUS site and the scenario number 2
that you described below is the one that is configured on this SBS. I checked
the permissions and they were in accordance to what you said that they were
to be. Hence there were no luck on that option. I tried to paste the text
that you showed in Suggestion 4 into a command prompt but the only thing I
got was error messages as I assume that the line break in the post online
made the command prompt execute an Enter strike, hence executing the
information that had been pasted so far.
I Have not tried to run the setspn as I find it somewhat awkward to use and
I will try it as a last resort.
I wonder if the Update Services.log-files are convenient to you in this case
or not. If they still are then please let me know and I will send you the
zipped log files.
Yours thankfully.
"Manfred Zhuang [MSFT]" wrote:
Hello Richard,.
Thank you for sending me the files.
After checking them, I suggest you try following steps to see if it works:
Suggestion 1.
========
On the WSUS Server check the permissions on the following Directory:
C:\Program Files\Update Service\SelfUpdate
You should have the following permission at a bare minimum:
Administrators = Full Control
System = Full Control
Domain/Users or LocaL/Users = Read&Execute, Read, List Folders
IUSR_<MachineName> = Read&Execute, Read, List Folders
*****NOTE***** <MachineName> being the host name of the IIS Server where
WSUS is configured.
Suggestion 2. Check in IIS Management Console you will have one of these
two setups configured depending on what you have done with IIS:
========
Scenario 1: WSUS Installation is installed on the Default Website
Default Website
- Selfupdate
- Content
- ClientWebServices
- SimpleAuthWebSerives
- WSUSAdmin
- ReportingWebServices
- DssAuthWebServices
- ServerSyncWebServices
Scenario 2: WSUS is not installed on the Default WebSite
Default Website
- SelfUpdate (Listening TCP 80)
WSUS Administration (Listening TCP 8530)
- Selfupdate
- Content
- ClientWebServices
- SimpleAuthWebSerives
- WSUSAdmin
- ReportingWebServices
- DssAuthWebServices
- ServerSyncWebServices
No matter which Scenario you have setup you should at least have a
SelfUpdate Virtual Directory configured under the Default Website listening
on Port 80. That Virtual directory should be pointing to: C:\Program
Files\Update Service\SelfUpdate
Also the only directory that should require "Intergrated Authentication" is
the WSUSAdmin virtually directory. All the others should only Allow
Anonymous.
Please check these few things that I have specified and get back to me if
you had to make any changes to your configuration. If you did have to make
an changes then after those changes are made go to a client and open a
command prompt and type the
following command:
wuauclt /detectnow
Suggestion 3.
========
Try to use SetSPN utility to register the SQL instance with port number and
the account it is running under in the Active Directory
Please refer KB for setspn syntax
319723 Information about SQL Server 2000 Kerberos support, including SQL
Server
http://support.microsoft.com/?id=319723
Check the service account for the SQL server in the Backend. If it is not
local system, check whether the account has permission to register SPN in
AD ?If not register it manually
setspn -a MSSQLSvc/FQDN of Backend SQL :Portnumber (for WSUS instance of
SQL)
Account name it is running under
e.g.: setspn -a MSSQLSvc/ELBERTA.corp.ad.msais.com:1435 Admin
Suggestion 4.
========
1. Click Start, click Run, type cmd, and then click OK.
2. Type: Sc sdset wuauserv
D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSW
LOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU), and then press ENTER.
Please copy the above command, right click in the opened command window,
and then choose Paste. Press Enter and you will receive a "Success"
message.
3. Type Exit to close the command prompt.
Please try the above steps at your earliest convenience. If the issue
persists, would you please send me following information? I did not find
them in your emails.
1. Export the following registry key and rename to .txt file.
HKEY_LOCAL_MACHINE\Software\Microsoft\Update Services
2. Compress all the files in C:\Program Files\Update Services\logfiles
folder to a .ZIP file.
Thank you for your cooperation.
Best regards,
Manfred Zhuang(MSFT)
Microsoft 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: Windows Server Update Services 2.0 Error
| thread-index: AchcD+r4Fl49VnDwRuWEy42fT6eNxg==
| X-WBNR-Posting-Host: 207.46.193.207
| From: =?Utf-8?B?UmljaGFyZCBKb2hhbnNzb24sIFBhcm5hc3Nv?=
<RichardJohanssonParnasso@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <48C30BBF-139C-407F-BEC1-36FDB2FC59F7@xxxxxxxxxxxxx>
<nDJnzgAXIHA.6404@xxxxxxxxxxxxxxxxxxxxxx>
| Subject: RE: Windows Server Update Services 2.0 Error
| Date: Mon, 21 Jan 2008 01:28:01 -0800
| Lines: 145
| Message-ID: <5BA58D46-6EB7-4E38-AA06-C8B7BABBBBC2@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:87802
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| I have found the paths that you specified and I have also zipped the
| specified files. After this I ran the analysis tool that you submitted a
link
| to. The specified file has now been emailed to you.
|
| "Manfred Zhuang [MSFT]" wrote:
|
| > Hello Customer,
| >
| > Thanks for your posting here.
| >
| > From your post, I understand that an error related to the update
service is
| > encountered.
| >
| > Before we go any further, I would like to confirm the following
information
| > with you.
| >
| > 1. Could you find the SoftwareDistribution.log on C: partition?
| >
| > 2. Does the C:\Program Files\Update Services folder exist?
| >
| > 3. When did you get the error message? When you try to synchronize WSUS
| > server?
| >
| > Now please help me to collect the following information for further
| > research.
| >
| > 1. Export the following registry key and rename to .txt file.
| >
| > HKEY_LOCAL_MACHINE\Software\Microsoft\Update Services
| >
| > 2. Compress all the files in C:\Program Files\Update Services\logfiles
| > folder to a .ZIP file.
| >
| > 3. Please download the MPS Report tool from the following link and run
it
| > on the SBS server, then send the generated CAB file to my mailbox
| > v-mzhuan@xxxxxxxxxxxxx for further investigation so that we can find
what
| > the root cause is:
| >
| >
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
| > 15706/MPSRPT_SUS.EXE
| >
| > For your information:
| >
http://www.microsoft.com/downloads/details.aspx?FamilyId=CEBF3C7C-7CA5-408F-
| > 88B7-F9C79B7306C0&displaylang=en
| >
| > If you have any concern, please feel free to let me know.
| >
| > Best regards,
| >
| > Manfred Zhuang(MSFT)
| > Microsoft 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: Windows Server Update Services 2.0 Error
| > | thread-index: AchZ+bVvIevOfsM3Ry6dNxjZaJuy7A==
| > | X-WBNR-Posting-Host: 207.46.192.207
| > | From: =?Utf-8?B?UmljaGFyZCBKb2hhbnNzb24sIFBhcm5hc3Nv?=
| > <RichardJohanssonParnasso@xxxxxxxxxxxxxxxxxxxxxxxxx>
| > | Subject: Windows Server Update Services 2.0 Error
| > | Date: Fri, 18 Jan 2008 09:44:00 -0800
| > | Lines: 29
| > | Message-ID: <48C30BBF-139C-407F-BEC1-36FDB2FC59F7@xxxxxxxxxxxxx>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Utf-8"
| > | Content-Transfer-Encoding: 7bit
| > | X-Newsreader: Microsoft CDO for Windows 2000
| > | Content-Class: urn:content-classes:message
| > | Importance: normal
| > | Priority: normal
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
| > | Newsgroups: microsoft.public.windows.server.sbs
| > | Path: TK2MSFTNGHUB02.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:87478
| > | NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | Hi!
| > | I have a client running an SBS2003 R2 server with the latest updates
on
| > it.
| > | At least I think so. For some time now, there has been an
- Follow-Ups:
- RE: Windows Server Update Services 2.0 Error
- From: Manfred Zhuang [MSFT]
- RE: Windows Server Update Services 2.0 Error
- Prev by Date: Re: PPTP workaround for VPN?
- Next by Date: Re: fax alert email
- Previous by thread: RE: Not receiving Mail to second E-Mail Domain
- Next by thread: RE: Windows Server Update Services 2.0 Error
- Index(es):
Relevant Pages
|