EV 8.0 SP4 on Windows 2008 R2 PowerShell issue

[Korbyn]

I can't seem to get my prebackup.bat file to successfully run.  The powershell window that comes up states:

WARNING: The following errors occurred when loading console D:\Program Files (x86)\Enterprise Vault\EVShell.psc1:
Cannot load Windows PowerShell snap-in Symantec.EnterpriseVault.PowerShell.Snapin because of the following error:
No snap-ins have been registered for Windows PowerShell version 2.

I've loaded up the Enterprise Vault PowerShell (bootstraper.exe) and it's still not registering.  I've even specified the Powershell path in the bat file:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -psconsolefile "D:\Program Files (x86)\Enterprise Vault\EVShell.psc1"

and still get the same error, but things work if I use:

C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe   (notice the SysWOW64)

Anyone know of a better way of getting the scripts working on R2, or is this just the necessary evil?

 

[JesusWept3 · Accepted solution]

http://seer.entsupport.symantec.com/docs/318009.htm

you pretty much nailed it on the head already

[Korbyn]

Have I menitoned lately how much I loathe the "search engine" that the symantec website uses...  Nice to know I can come up with a solution that posted but few can find...

Thanks JW.

[AndrewB]

maybe it's not the greatest search engine in the world but i went to http://www.symantec.com/business/support/overview.jsp?pid=50996, searched for "powershell windows 2008", and that article was the first hit

[JesusWept3]

to be honest i googled the same term that andrew did, google is definitely the easiest way

[Korbyn]

I never had any problems with R1, hence my search was with R2, which comes with PowerShell 2.0 which seems to screw things up for PS1 stuff.  I also never installed PS2 on R1 EV servers.  Guess my searching was a little to percise.

Of course the google finds my posting, now... :)

Anyways... it's not ment to be the point of this topic.  I'll have to check EV9 on R2 and see if it's going to be an issue there.  SP4 allegedly resolved this, but apparently not as that's what I'm using at this client.