Skip to main content

"get computer/ip status" activity throws raw socket error

recently ran across this quirk trying to test a runbook in orchestrator...

PROBLEM SUMMARY

imagewhile in the runbook designer, whenever the "get computer/ip status" activity is called, it fails with the following error:

 

image

 

the error summary text in its entirety:

Raw socket error. Error: 10013 An attempt was made to access a socket in a way forbidden by its access permissions.

 

according to this microsoft article (thanks richard catley), the error translates to this:

WSAEACCES (10013)
Translation: Permission denied.
Description: An attempt was made to access a socket in a way that is forbidden by its access permissions. For example, this error occurs when a broadcast address is used for sendto but the broadcast permission is not set by using setsockopt(SO_BROADCAST). Another possible reason for the WSAEACCES error is that when the bind (Wsapiref_6vzm.asp) function is called (in Microsoft Windows NT 4 .0 Service Pack 4 [SP4] or later), another program, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4.0 SP4 and later, and it is implemented by using the SO_EXCLUSIVEADDRUSE option.

 

which means absolutely nothing to me -- except there is a possible permission issue somewhere. :) after posting to the technet forum, i decided to file a bug. as any decent human being does, i searched to see if the bug had already been filed. sure enough it had. it's right here if you want to read the details.

 

SOLUTION

anyway, i verified i was in local admin, etc. turns out you have to launch the console with run as administrator permissions to elevate it properly in order for the activity to have the required access. jeff fanjoy describes it in the bug.

image

 

OTHER STUFF

you may have read robert hearn's post about running the runbook tester as another user. so... what do you do in the scenario where you must run the runbook tester as a different user since there's no perceivable way to perform a runas a different user and run as administrator?

well, i couldn't find a way in the windows UI... but if you know of one, please comment up. you can do it, but it's convoluted. here you go:

  1. log in as the user.
  2. open up a cmd prompt with run as administrator.
  3. execute the following:

"C:\Program Files (x86)\Microsoft System Center 2012\Orchestrator\Runbook Designer\RunbookDesigner.exe"


what if you don't want to log on as the user? i dunno how to do that one. go figure it out, and let me know. :)

Comments

  1. Wonder if this would work for you so you don't have to jump through hoops each time you need to start SCORCH:

    http://www.sevenforums.com/tutorials/11949-elevated-program-shortcut-without-uac-prompt-create.html

    ReplyDelete
    Replies
    1. i looked at that. it seemed so clunky to get that to work. i'm really surprised there's no other option that's natively available.

      Delete
  2. Got to Properties, select compatibility down there is a checkbox for "Run as Admin" check that and "change for all Users". Then you can use "Execute as" und it's elevated!

    ReplyDelete
    Replies
    1. that is definitely an option, oliver. thanks for pointing that out!

      Delete

Post a Comment

Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here.(get-netadapter | get-netipaddress | ? addressfamily -eq'IPv4').ipaddress update: this is by far the easiest.PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress
192.168.1.101
are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does.done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it.i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point. even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch.I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.DETECTIONstatus messagestake a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough material to …