Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1151
  • Last Modified:

WinRM error message on SBS 2003 server

Hi There,

I am prepping for an SBS 2003 -> SBS 2011 migration. The initial work is fixing problems identified in Event Viewer / System and also by the SBS Server 2003 Best Practices Analyzer.

Here's one I'm having trouble with:

Event Type:      Error
Event Source:      WinRM
Event Category:      None
Event ID:      10119
Date:            1/30/2014
Time:            9:38:57 AM
User:            N/A
Computer:      ROLLINS
Description:
The WinRM service is unable to start because of a failure during initialization.

 Additional Data
 The error code is 1300.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Your help is appreciated!

thanks, Kristin
0
forcedexposure
Asked:
forcedexposure
  • 2
  • 2
1 Solution
 
ktaczalaCommented:
here's an excerpt of a possible fix.
Microsoft released a "Update for Windows Server 2003 (ME968930)" at the end of October 2009 that includes the Windows Remote Management (WinRM) 2.0. If you get this event, then the installation may be corrupt and/or permissions on your server are incorrect. To fix this you have two options:

1. Remove > Goto Control Panel > Add/Remove Programs (tick)"Show Updates" >  "Windows Management Framework Core" = Remove.  May require a reboot.  If using WSUS you may need to unapprove otherwise it will re-detect & reinstall.

2. = Correct the permissions as per "IIS and Built-in Accounts (IIS 6.0)" - see the link below. A bit more involved but it corrects the problem. You'll need to either open either the GP Mgmt console (gpmc.msc) or the local Policy editor (gpedit.msc).  Navigate to the policy in which the server is located and delve into Computer Configuration > Windows Settings > Security Settings > User Rights Assignment and define &/or add the NETWORK SERVICE account to the aforementioned policies.  If you are on a Domain Controller you the NETWORK SERVICE account is not part of the IIS_WPG group so you have to add it manually to the polices that the article mentions.
0
 
forcedexposureAuthor Commented:
Hi! thanks for the response.

I'd like to try solution #2 since removing the Windows Management Framework Core update might cause too many other things to fail.

so, regarding this instruction:
"add the NETWORK SERVICE account to the aforementioned policies. "

what are the aforementioned policies?

thanks! Kristin
0
 
ktaczalaCommented:
domain controller policy > Computer Configuration > Windows Settings > Security Settings > User Rights Assignment
go to this link scroll to 'Network Service' and make sure all those policies listed have Network Service in them.
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/3648346f-e4f5-474b-86c7-5a86e85fa1ff.mspx?mfr=true
0
 
forcedexposureAuthor Commented:
Hi There!

I ended up removing the Windows Remote Management (WinRM) 2.0 application and it seems to have worked.

thanks!!!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now