Error when running the WSUS- apps. « dougzuck.com

dougzuck.com - Forum » Remote Reboot X - The Ultimate WSUS Companion Tool

Error when running the WSUS- apps.

(15 posts) (4 voices)

Started 2 years ago by Enigma
Latest reply from biggers

Tags:

No tags yet.

Enigma
Member

Hi Doug
like the apps.
I get a error when running any of the 3 extra WSUS apps. Happens when I run it either on the wsus server or my workstation. I have the console installed also.
The server listens on port 8530.
The server is Win2003 SP2 and workstation is Win XP SP3

RemoteRebootX>WSUS-RetrievePendingRebootsList.exe
Enter WSUS Server Name or IP:
panakeia

Unhandled Exception: System.Net.WebException: The request failed with HTTP statu
s 404: Not Found.
at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Obje
ct[] args)
at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String
serverName, Boolean useSecureConnection)
at WSUSRetrievePendingRebootsList.Program.Main(String[] args)

Would you know what is causing this.

Posted 2 years ago #
doug
Key Master

You have to have the WSUS 3.0 Admin Console installed on the machine that you are executing those 3 scripts from otherwise they will not work.

Thanks,
Doug

Posted 2 years ago #
gramps
Member

Doug

I am having the exact same problem as Enigma. WSUS Admin Console is on the same machine as RebootX. So are the .exe files
Debug message starts with:

System.InvalidOperationException was unhandled
Message: Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.
The request failed with the error message:
--
<HTML dir="ltr">
<HEAD><meta name="GENERATOR" content="Microsoft SharePoint" /><meta name="progid" content="SharePoint.WebPartPage.Document" /><meta HTTP-EQUIV="Content-Type" content="text/html; charset=utf-8" /><meta HTTP-EQUIV="Expires" content="0" /><meta name="ROBOTS" content="NOHTMLINDEX" /><title>

Is there a clue in the fact that this server is also running Sharepoint?

Thanks

Posted 2 years ago #
doug
Key Master

Hey gramps, are you having trouble launching RemoteRebootX or are you having trouble launching the 3 other executables that I included in the download? In order to run the 3 executables you need to have both the .NET framework and the WSUS 3.0 Admin Console installed on the machine you're running them from. In order to run RemoteRebooX, you only need to have the .NET framework. Hope this helps.

-Doug

Posted 2 years ago #
gramps
Member

Hi Doug
Thank you very much for sharing your work.
RemoteBootX itself works absolutely tickety-boo; does everything you describe exactly as I would expect. Net Framework 2 SP2 and the WSUS 3.0 Admin Console are installed on this same server, but the 3 apps give similar error messages. Starting the Visual Studio 2005 debugger reveals "An unhandled exception ('System.InvalidException') occurred in WSUS_GetListOfServersThatHaveNotCheckedIn.exe [6296]." Digging a bit further finds
"Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'."
Thanks again

Posted 2 years ago #
doug
Key Master

Do you get the error as soon as you launch the apps or when you actually try to enter a server name and click enter?

Posted 2 years ago #
gramps
Member

Yo, Doug! The error message appears a short while after entering the server name. It happens consistently no matter whether I use a server name or IP address, and it consistently refers to getting HTML instead of text.
Cheers

Posted 2 years ago #
gramps
Member

Sorry, in my last post, I meant the error messages consistently say QUOTE 'text/html; charset=utf-8', but expected 'text/xml' UNQUOTE

Posted 2 years ago #
doug
Key Master

Gramps, I hadn't noticed the message about it being a SharePoint server, but it absolutely makes sense that therein lies the problem. If I recall there is a port issue because doesn't WSUS Server 2.0 uses port 80 by default as does SharePoint? This might be your problem.

Posted 2 years ago #
gramps
Member

Er no, Doug, I don;t think it's a clash of the ports, because Sharepoint is on port 80, and WSUS is running happily on 8530. Can you give me a clue as to how your 3 apps find the information, eg the location and name of a log file; is it an SQL query, or something much simpler?
Thanks

Posted 2 years ago #
doug
Key Master

gramps - the 3 apps use the WSUS Server API which exposes various methods and properties which can be used to get this information. In your case, it's failing when the apps try to connect to the WSUS server to retrieve the info. If it's not specifically a port problem, it is still almost definitely related to your setup. When the apps try to talk to WSUS, they're getting a response from SharePoint instead. When you launch the WSUS admin console, does it have problems connecting to the WSUS server and displaying info or does it work properly? I'm not sure that there's much I'll be able to do to fix this problem, but after the holiday I will take a closer look at the code and see if anything else can be done. However, those 3 apps are literally only a couple lines of code each. The first line of code establishes a connection with the remote WSUS server. The couple lines after that request the relevant information and display them to the console.

Posted 2 years ago #
gramps
Member

Hi Doug. I have taken this a little further by setting up a test domain to host a DC, WSUS server and a workstation. Early results are that after accepting the default installation of WSUS on a machine with nothing else installed, the RemoteRebootX Apps do not give error messages. I'll give you any further stuff that may be of help to other users separately. Thank you very much for your support.

Posted 2 years ago #
gramps
Member

Hi Doug. I have now taken the following steps to get the 3 Apps working on my production server: Migrated Sharepoint to another server; de-installed WSUS; de-installed IIS to get rid of the last traces of Sharepoint so that the WSUS installer would reinstall using the default port 80; reinstalled IIS and then WSUS (now defaulting to port 80). The 3 Apps now run as expected, with one minor issue: When terminating, they give the message “Press any key to exit…”. They seem to need a Return character to cause them to terminate.

Having gone to this much trouble, you can probably understand that I’m very anxious to use this tool. Thanks again.

Posted 2 years ago #
doug
Key Master

Gramps - that is definitely quite a bit of trouble to go through, but I'm glad you got everything straightened out! The "press any key to exit" is hardcoded into the 3 apps. When I get around to it I'll recompile them without it.

-Doug

Posted 2 years ago #
biggers
Member

Hi, i really like the remoterebootx tool nice work; i too had the same issue with the 3 extra executables not running on my WSUS server. I too had sharepoint on this box in the past which used port 80.

This server is production so i could not go for a hugh uninstall/re-install session.

The "solution" i found was to create a temporary hostheader for WSUS on port 80 in IIS, this meant that the 3 executables could communicate and generate the lists before i then removed the hostheader.. solved.

Look forward to the new release, might be good to allow for WSUS connections on ports other than 80... but certainly no complaints from me on this tool.

-Mike

Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.