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

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off

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.   DETECTION status messages take 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 m