Quantcast
Channel: Software Communities : Popular Discussions - ActiveRoles
Viewing all articles
Browse latest Browse all 1277

Server binding failing in PowerShell

$
0
0

Hello,

 

I'm working in an environment with two separate/non-connected installations of ARS - one v6.7, the other v6.0.4. Consequently it will be necessary for me to make sure that my code is binding to the correct instance of ARS. In my own VMWare environment, following the instructions in the SDK works just fine.

 

$BoundObject = [ADSI]"EDMS://server.domain.com/CN=Configuration"

 

When I attempt the same in the production environment, I receive the following error:

 

format-default : The following exception occurred while retrieving member "PSComputerName": "Unknown error (0x80041452)"

  + CategoryInfo          : NotSpecified: (:) [format-default], ExtendedTypeSystemException

  + FullyQualifiedErrorId : CatchFromBaseGetMember,Microsoft.PowerShell.Commands.FormatDefaultCommand

 

That happens whether executing locally on the ARS server or remotely, and on both ARS versions.

 

I experimented with the equivalent in VBS, and interestingly, that works under the right circumstances. When logged in to one of the 6.7 servers, the VBS will succeed if connecting to another 6.7 server (either local or remote) but will fail against the 6.0.4 servers. Conversely, if logged in to a 6.0.4 server, the VBS will succeed when connecting to another 6.0.4 server and fail for 6.7.

 

I can learn to deal with the fact that I may not be able to connect to an ARS server that doesn't match the vesion of my client, but that doesn't explain why the PowerShell version fails under all circumstances.

 

Any thoughts would be most appreciated!


Viewing all articles
Browse latest Browse all 1277

Trending Articles