I've seen this error when developping with powershell.

The problem might be that the translation provider starts with "sdltm.http....", which seems not to be a supported format if using integrated windows-authentication.

As I didn't want to edit the project, I ended up defining a local user on the server and adding its credentials to the project, before starting the analysis.

It looks like this in the PS-code:

$project.Credentials.AddCredential("sdltm.https://someadress:443",$false,"someuser","somepass");

As this config is only added to the instance of the currently opened project, it wont edit anyhting inside, but will allow the process to run through.

HTH

Markus

I've seen this error when developping with powershell.

The problem might be that the translation provider starts with "sdltm.http....", which seems not to be a supported format if using integrated windows-authentication.

As I didn't want to edit the project, I ended up defining a local user on the server and adding its credentials to the project, before starting the analysis.

It looks like this in the PS-code:

$project.Credentials.AddCredential("sdltm.https://someadress:443",$false,"someuser","somepass");

As this config is only added to the instance of the currently opened project, it wont edit anyhting inside, but will allow the process to run through.

HTH

Markus

Can you please provide some details on how you are setting the credentials ? Also the StractTrace for the first exception is hidden and would be useful to see that too.