I am getting error 58289 whenever I try to log in to a logical account using the following syntax:$cred = Get-CredentialNew-PWLogin -DatasourceName <my data source> -UserName TheUser -Password $cred.PasswordAt first, I thought that I was doing the encryption/decription incorrectly, so I demonstrated the problem using the secure string directly (as above). This code works fine on my development machine, but it gives me error 58289 when I run it from the server. I get the same results using Save-SecureStringToEncryptedFile and Get-SecureStringFromEncryptedFile . This was working at some point and I'm not sure when it stopped working. Any ideas?
SecureStrings created without a key only work on the machine and Windows account they were originally created on. If you created the encrypted file on one machine and copied it to another it would not work.
My reading on Get-Crediential is that it uses a different method of encryption and cmdlets have to support the credential object, I'm not sure new-pwlogin does.
Ah, now that I'm back at my computer I tested Get-Credential with New-PWLogin and it does work for me with a logical account.
$cred = Get-Credential
# enter logical account username/password
New-PWLogin -DatasourceName "ds_name" -UserName $cred.UserName -Password $cred.Password
So that part of your test should've worked. Get-PWError 58289 doesn't return an error message so I'm not sure what's going on. I would try making a new encrypted file on the production server instead of copying it from the dev server.
hmm, if I enter an incorrect password into Get-Credential I get an error 58064 not 58289 so I'm not sure this is a password issue.
I just started getting this error after we upgraded our server to the latest version. I was building my own web service that was utilizing PowerShell commands to do special tasks prior to the upgrade and everything was working fine. Here I am now back working on the project and it was blowing up in my face with this same error.
When I tried logging into the system with the lines of code you showed up above, I get the dialog to login as normal, but after I accept, Connection Client pops up requiring needing to be logged in. This is where I believe the error lies. Even though we are trying to access the server with a local account, the server is requiring access via an SES(?) account.
So I guess the real question is: Can a service be created on a server to auto log in with an SES account (Connection Client/IMS user) if not already logged in and when needed?
Bentley Web Services Gateway 02.06Server Version: 02.06.08.09Web API Version: v2.8
Error 58289: Failed to activate license. Please contact your system administrator.
This is what I am getting as an error for the number you provided. Are you able to login to ProjectWise Explorer application okay via Connection Client?
Well, that's just it. Connection Client has never worked on this server. This jogged my memory though about the client versions...03.434 requires the Connection Client regardless of your method to connect of your connection to the datasource.
I downgraded the client to 03.329 and it's working fine now.
My thoughts were directed towards the server since the issue seemed to happen at that time. All of the clients in the building were upgraded when we finally had the server upgraded, and that's what was causing the issue.
Answer Verified By: Madhuri Londhe
Glad we got it figured out! I have not ran into the issue of Connection Client yet but we haven't updated the software on our integration server.