Cannot use VeeamPSSnapIn

[riahc3]

Im trying to use Veeam's Powershell functions but since I have updated to Update 3, I get this:

Code: Select all

PS C:\Windows\system32> Add-PsSnapIn VeeamPSSnapIn
Add-PsSnapIn : No snap-ins have been registered for Windows PowerShell version 4.
At line:1 char:1
+ Add-PsSnapIn VeeamPSSnapIn
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (VeeamPSSnapIn:String) [Add-PSSnapin], PSArgumentException
    + FullyQualifiedErrorId : AddPSSnapInRead,Microsoft.PowerShell.Commands.AddPSSnapinCommand

PS C:\Windows\system32>

This used to work as I was running a script that gave "License is not installed."; This was fixed in U2 It seems and I updated it for that reason alone. But now I cannot add it period.

[PTide]

Hi,

Please try to reinstall Veeam Update and PS snap-in.

Thank you.

[riahc3]

Hi,

Please try to reinstall Veeam Update and PS snap-in.

Thank you.

I tried to reinstall the Veeam Update and nothing.


How do I reinstall the PS snap-in?

[PTide]

Just start the .msi and follow the wizard.

[veremin]

Are you running a free version, by any chance?

[riahc3]

Just start the .msi and follow the wizard.

I already did this. Before installing U3 and then after again U3 just in case. Still nothing.

Are you running a free version, by any chance?

Yes. AFAIK, I should be able to access it regardless.

[veremin]

Yes, you should be able to access PS snap-in regardless of edition. I was just wondering whether the re-installation from scratch could help in your case. Thanks.

[riahc3]

Yes, you should be able to access PS snap-in regardless of edition. I was just wondering whether the re-installation from scratch could help in your case. Thanks.

1: Uninstalled
2: Reinstalled, INCLUDING THE POWERSHELL SDK
3: Updated to U3
4: Tried the same command and nothing. Same error. "No snap-ins have been registered for Windows PowerShell versión 4"

[veremin]

What about either manually inputting this registry key or opening VB&R snap-in via corresponding option in GUI?

[Zholaman]

I have the same issue!

[Vitaliy S.]

If none of the suggestions above help, please open a support case. Thanks!

[riahc3]

If none of the suggestions above help, please open a support case. Thanks!

The issue is that this is on SEVERAL threads; Veeam needs to test a fix.

[veremin]

Generally speaking, the issue itself is not Veeam specific. If you google it, you’ll see the exact same issue reported for different snap-ins.

The typical reason is that in 64-bit operating systems there are two instances of PowerShell: 32-bit and 64-bit, and they are present in different directories inside the operating system.

Even though, the factors leading to the said issue (“no snap-ins have been registered”) are caused by co-existence of two instances of PowerShell, they still differ from one another.

For example,

- Snap-in has been incorrectly registered (or has not been registered at all) for the improper PS instance either automatically or by user via instautil
- User tries to add 64-bit snap-in from 32-bit PowerShell instance
- 64-bit PowerShell shortcut is wrongly pointed to SysWOW64
- Usage of Windows 2008 (R2) with default Powershell 2.0 (there are a lot of strange issues related to it)
- etc.

Thus, there is no universal solution. The typical troubleshooting steps include:

- Opening VB&R snap-in via icon in VB&R GUI (Menu -> PowerShell)
- Manually registering snap-in
- Checking corresponding registry hive and manually re-creating missing entities
- Updating default Powershell 2.0 in case of Windows Server 2008 (R2)
- Reinstalling the latest Update, along with PS snap-in
- Reinstalling everything from scratch (mostly applicable for those who are on free product version, as there is no configured backup infrastructure, historical data etc. ; might be a tough call for those who are not paid product versions, however)

It seems that neither of proposed solutions has done the trick for you. So, please feel free to open a ticket with our support team and post its number here, so that, we can follow the case.

Also, I’m about to create a sticky post and describe the problem and required troubleshooting steps in more details there.

Thanks.

[Gostev]

Opening VB&R snap-in via icon in VB&R GUI (Menu -> PowerShell)

From what I know from his post on Reddit, this actually did work for him

[riahc3]

Generally speaking, the issue itself is not Veeam specific. If you google it, you’ll see the exact same issue reported for different snap-ins.

Thanks for the general ovewview of the situation. I think too that it is a 32 bit vs 64 bit issue. Also, Im using Windows Server 2012 R2. I apoligize for not mentioning that important detail.

Im working with your (extremely fast BTW) support team and see if I can get a solution.

v.Eremin, from your point of view, would a tool from Veeam that does all the points you mentioned automatically be nice for the user? Instead of mixing, matching and trying everything out in a random order? Personally, a tool that applies thoses "fixes" correctly, opens a Powershell session, and tries to load the module would be nice. If it loads, problem solved. If it doesnt, it can generate a zip full of all the logs and files Veeam needs to analize the case so the user can send it to Veeam.

I think it would help all parties involved (in my opinión of course)

[veremin]

For now I think the sticky forum post (that I'm about create) describing the possible causes and solutions would be enough.

After that, when workload on QA team decreases, we can try to get back to that issue , dig deeper into that and find an universal solution helping users in overwhelming majority of cases.

The said tool would be nice, of course, but I don't believe we can justify investing dev.time and resources in creation of utility that takes care about non Veeam specific issue.

However, thank you for drawing our attention to the existing problem; we'll think for sure about best way of dealing with it.

[veremin]

And here goes sticky topic.

[riahc3]

Fair enough. I think a sticky with general "tips" is nice.

Now dealing with a "License not found" issue...but this problably has nothing to do with the registring of the snapin.