Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
The stored password for the server "MYSERVER" is invalid.
-
I have two ProGet instances, each configured exactly alike, with identical ProGet Deploy feeds with the same project, with the same Chocolatey package in it. Both ProGet instances point to the same deployment server. One ProGet instance deploys to the server without any issue. The other one fails with this message:
Starting deployment... Verifying MYSERVER... **System.InvalidOperationException: The stored password for the server "MYSERVER" is invalid.** at Inedo.ProGet.Service.DeploymentExecuter.DeployToServer(Deployments_Extended deployment, Servers server, IEnumerable`1 serverTargets) at Inedo.ProGet.Service.DeploymentExecuter.Deploy(Deployments_Extended deployment)
Both ProGet instances use the same user name/credentials on the target deployment server.
Product: ProGet
Version: 3.1.0
-
This exception is thrown if the
EncryptedPassword_Bytes
column isnull
... if you re-enter the password does it work?
-
No, I already tried that, thinking maybe I mistyped the password or something. I re-entered it and got the same error.
-
What user account is the web application running as? It may not have permission to change the password but is silently failing. The password encryption process has to occur on the server end, so the password change is actually proxied to the server first before it is saved to the database. There might be a problem with the connection from the web app to the service, and I know that can happen if the web application doesn't have privileges to connect to the named pipe opened by the service.
-
It's running as NetworkService on both instances. The user credentials on the deployment target server are also identical between both ProGet instances. The credentials are my own, the same user that installed Chocolatey, and I have admin on all servers.
-
New information: When I try to re-enter the password on the "broken" ProGet instance, I get this error message:
Unable to set service password. This probably indicates that the web application couldn't communicate with the ProGet service. The error message was: Messenger is not connected.
-
Can you try restarting the web app and/or service on the failing server?
-
I restarted the ProGet service and tried again, and it still failed. I then tried to re-enter the password and it took it!
However, now when I try to deploy, I get this:
System.Management.Automation.PSNotImplementedException: Cannot perform operation because operation "NewNotImplementedException at offset 108 in file:line:column <filename unknown>:0:0 " is not implemented. at System.Management.Automation.RemoteRunspace.GetSessionStateProxy() at Inedo.ProGet.Service.DeploymentExecuter.DeployToServer(Deployments_Extended deployment, Servers server, IEnumerable`1 serverTargets) at Inedo.ProGet.Service.DeploymentExecuter.Deploy(Deployments_Extended deployment)
-
That seems to indicate a module or cmdlet is missing. What version of PowerShell is installed on the Proget service's server, and also on the remote server?
-
Target server:
PS C:\Users\gma> $PSVersionTable.PSVersion Major Minor Build Revision ----- ----- ----- -------- 2 0 -1 -1
ProGet server that is failing to deploy:
PS C:\Users\gma> $PSVersionTable.PSVersion Major Minor Build Revision ----- ----- ----- -------- 2 0 -1 -1
ProGet server that successfully deploys:
PS H:\> $PSVersionTable.PSVersion Major Minor Build Revision ----- ----- ----- -------- 3 0 -1 -1
-
I upgraded ProGet to 3.1.1, and upgraded PowerShell on all servers to 3.0, and I still get this when trying to deploy:
System.Management.Automation.PSNotImplementedException: Cannot perform operation because operation "NewNotImplementedException at offset 108 in file:line:column <filename unknown>:0:0 " is not implemented. at System.Management.Automation.RemoteRunspace.GetSessionStateProxy() at Inedo.ProGet.Service.DeploymentExecuter.DeployToServer(Deployments_Extended deployment, Servers server, IEnumerable`1 serverTargets) at Inedo.ProGet.Service.DeploymentExecuter.Deploy(Deployments_Extended deployment)
-
Does one of your embedded scripts contain a reference to a module that doesn't exist on a remote server, e.g. Web Server Administration for IIS? Unfortunately the error returned by PowerShell is fairly useless in determining which exact module is missing :)