Re: win32::taskscheduler - failure from New()?

For the second time today, this looks like a permissions thing.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Comment on Re: win32::taskscheduler - failure from New()?

Replies are listed 'Best First'.
Re^2: win32::taskscheduler - failure from New()? by ethrbunny (Monk) on Oct 19, 2007 at 05:10 UTC
Both the functional and non-functional tests are run as the same user... in the same cygwin window in fact. One after the other.	[reply]
Re^3: win32::taskscheduler - failure from New()? by BrowserUk (Patriarch) on Oct 19, 2007 at 10:16 UTC
You are running the soap daemon in a cygwin window? From where are you making the connection to it? Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]
Re^4: win32::taskscheduler - failure from New()? by ethrbunny (Monk) on Oct 19, 2007 at 13:25 UTC
Another cygwin window. Same machine. Same login. FWIW -in the same soap package I am able to call functions in Win32::Service and Win32::Process.	[reply]
Re^5: win32::taskscheduler - failure from New()? by BrowserUk (Patriarch) on Oct 19, 2007 at 13:30 UTC