Windows PowerShell - VisualCron - Forum

Community forum

rhu@service3.dk
2012-09-14T13:16:07Z
I have a job running for some times I VisualCron 6.1.2 but now it fails all the time.

It get this error:

Cannot load Windows PowerShell snap-in Microsoft.Exchange.Management.PowerShell.E2010 because of the following error: The type initializer for 'Microsoft.Exchange.Data.Directory.Globals' threw an exception.

Can anyone tell me why it stop working?

Regards
René
Support
2012-09-18T11:46:26Z
Discussion continue on chat. Waiting further feedback.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Support
2013-01-04T11:17:20Z
Hi,

was this resolved and how?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
rhu@service3.dk
2013-01-04T11:30:42Z
Yes, I can't remember how I did.
I told you that long time ago. :-)

Anyway thanks for the help.
Support
2013-01-04T11:34:40Z
Another user is having the same problem. Do you still have this Task running?

I have vague memories of;

1. Powershell version
2. .NET version
3. Credentials

Any ideas?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Support
2013-01-04T11:47:13Z
I foudn this response on email:

Quote:

I made an work around, by adding ! Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010” in the begins og my *ps1 file and them move them to Exchange and on Exchange I run them as a schedule job.


Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
rhu@service3.dk
2013-01-04T13:13:54Z
It is what I did, I never got Visualcron to do it again.
bbusse
2013-01-04T14:40:39Z
That just sounds like you need to have the Exchange 2010 Admin Tools installed on whatever system VisualCron is on. There might be an optional component (we're not on 2010 yet... can't validate) to install, though i'm pretty sure Exchange 2010 cmdlets are installed along with that.

Obviously, the exchange cmdlets are not native, so i'd lean towards an Exchange admin tools install corruption on the system running VC. VisualCron wouldn't (at least I can't think how) be at fault or even involved here. The scripts and/or code should work outside of VC. I assume thats been tried, manually running the scripts and excluding VC from the issue?

Scroll to Top