Invalid User Name and/or Password
Hello After upgrading to 3.47 I was receiving an authorization error message, so I uninstalled 3.47 and went back to 3.44. Now 3.44 is receiving the same error message. So I upgraded to 3.49 and...
Forum Discussion
Hello
The project is saved locally and is not shared. I am connecting with my internal help desk as well.
Question: If the project is saved on a google drive could that be causing the issue?
Hey Annie_Murphy,
Rao was saying this just as a general rule. It's advisable to wait and not grab the latest version as soon as it's available unless it includes a fix you need, cos new versions can have regressions. I tend to sit a couple of releases behind the most recent version because of this reason (in fact the release before the latest people found regressions that were breaking their tests....someone posted about this a number of weeks ago)
Anyway. Ok, so it's a local project.xml file. Don't see how saving to cloud based storage would make any difference.
So! You mention that your colleagues are running the same tests successfully on their ReadyAPI instances without getting the invalid creds soap fault, right?
If they're running the same tests from their local copy of the project (i'm ignoring the question of "why?" at this point), have you tried grabbing a copy of their project.xml file (with working tests) and running those tests in your ReadyAPI instance and seeing what happens?
Assuming those identical tests work successfully (and i've no reason to think otherwise...the ReadyAPI version shouldn't make any difference), you could open both your existing project and your colleagues in ReadyAPI and clone the working tests into your existing project.
We have a number of options to try to sort your problem, i'm suggesting the easiest/quickest option for now.
Cheers!
Rich
Rao was saying this just as a general rule. It's advisable to wait and not grab the latest version as soon as it's available unless it includes a fix you need, cos new versions can have regressions. I tend to sit a couple of releases behind the most recent version because of this reason (in fact the release before the latest people found regressions that were breaking their tests....someone posted about this a number of weeks ago)
Anyway. Ok, so it's a local project.xml file. Don't see how saving to cloud based storage would make any difference.
So! You mention that your colleagues are running the same tests successfully on their ReadyAPI instances without getting the invalid creds soap fault, right?
If they're running the same tests from their local copy of the project (i'm ignoring the question of "why?" at this point), have you tried grabbing a copy of their project.xml file (with working tests) and running those tests in your ReadyAPI instance and seeing what happens?
Assuming those identical tests work successfully (and i've no reason to think otherwise...the ReadyAPI version shouldn't make any difference), you could open both your existing project and your colleagues in ReadyAPI and clone the working tests into your existing project.
We have a number of options to try to sort your problem, i'm suggesting the easiest/quickest option for now.
Cheers!
Rich
