Running the client w/o beeing logged in

Beth · Post by **Beth** » Fri May 16, 2008 3:50 pm

Do you have other scheduled things running fine? If so, then maybe we can compare what's different about them on your machine.

thomas woelfer · Post by **thomas woelfer** » Sat May 17, 2008 3:01 am

yes, i have other jobs running scheduled on that machine. they are all running under the same account. they are all running fine w/o anyone beeing logged in. one of the other jobs is running a .net 2.0 application w/o any problems.

isn't the crypto exception giving you any clues ?

-thomas

Beth · Post by **Beth** » Mon May 19, 2008 12:12 pm

The suggestion I had to add the runtime portion came from looking at that.

I'm going to take this offline so I can have you show me more. I'll reply to your email.

Beth · Post by **Beth** » Mon Sep 15, 2008 12:46 pm

As a follow up to this thread, the solution was the user needed to give administrator and system rights to C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys.
HS: 197063

SourceGear Support

Running the client w/o beeing logged in

Re: Running the client w/o beeing logged in