Author Topic: Web Application editor  (Read 593 times)

Offline force

  • Newbie
  • *
  • Posts: 1
  • Welcome dear user ,please try to comperate and keep on posting to be active
    • View Profile
Web Application editor
« on: July 18, 2010, 05:40:29 pm »


View Profile Email Personal Message (Offline)
   
   
Web Application editor
? on: July 13, 2010, 03:16:31 PM ?
   Reply with quoteQuote Modify messageModify Remove messageRemove WarnWarn Split TopicSplit Topic
I have got a intranet URL needed to be monitored and it does require NTLM, i was sucessful to create a monitor for the URL perhaps got a stop sign

a) on Ops Manager 2k7 R2 (64bit) machine i get an error when i click on "Run Test" "an illegal token, $RunAs, is contained in the task overrides"

b) on Ops Manager 2k7(32bit) machine. i get a 401 Error

in both of these cases i had NTLM with a windows account as RunAs command

any help will be appreciated

Share on Bluesky Share on Facebook


Offline lokos

  • Newbie
  • *
  • Posts: 1
  • Welcome dear user ,please try to comperate and keep on posting to be active
    • View Profile
Re: Web Application editor
« Reply #1 on: July 18, 2010, 05:43:39 pm »
    hen i click on "Run Test" "an illegal token, $RunAs, is contained in the task overrides"


The same error occurs for me  as well, however i take it with a grain of salt as the webpages are monitored correctly in my environment.

Not sure why it does it, but since it isn't stopping me from doing what i need to do I don't have the need to investigate it.

Offline rocker

  • Newbie
  • *
  • Posts: 1
  • Welcome dear user ,please try to comperate and keep on posting to be active
    • View Profile
Re: Web Application editor
« Reply #2 on: July 18, 2010, 05:45:36 pm »
Hi,

Did a popup warned you when you clicked "Run Test", something like: "Running a test of this web application may fail.." ? The run task functionality does not work for this feature when credentials are specified...

I'm not sure why there is a difference on the runtime for when its 32 bits or 64 bits (it is the same task) though.

If you save, your workflow will use the specified credential, you can't run test to verify though. I usually save with a criteria that I know will match when it works, and once I verify the criteria was triggered (the test run with right creds) I change the criteria to its negative (so when it doesnt work I get warned).

HTH,

-ROcker-



This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm