does WAPT efficiently support .NET web applications?

[Guest hasan]

Hi All,

 

Im just a beginner on WAPT. I just wanted to know that does it efficiently support .NET based web applications?

It is because while testing a web application Im getting "401 Access Denied Error" even when I have already logged in successfully (when I click on 'verify test' and see the result in summary). To elaborate my question, Im getting access denied errors for the actions for which I have the authority to perform and have performed them perfectly while recording the test scenarios but while running and verifying tests i get that error message.

 

Note: I have already made VIEWSTATE2 value as '$Hidden'.

[Guest angela]

Hi All,

 

Im just a beginner on WAPT. I just wanted to know that does it efficiently support .NET based web applications?

It is because while testing a web application Im getting "401 Access Denied Error" even when I have already logged in successfully (when I click on 'verify test' and see the result in summary). To elaborate my question, Im getting access denied errors for the actions for which I have the authority to perform and have performed them perfectly while recording the test scenarios but while running and verifying tests i get that error message.

 

Note: I have already made VIEWSTATE2 value as '$Hidden'.

 

Hi,

 

First, please check if you are running the latest build of WAPT (you can get the latest version and build directly on our site.

 

If the build of WAPT is current, most probably, the problem is in incorrect transfer of session parameters. Please send to us your scenario, profile, Full and Error logs generated by WAPT. Also, it would be of help to have a link to your application.

 

 

 

[Guest hasan]

Hi,

 

First, please check if you are running the latest build of WAPT (you can get the latest version and build directly on our site.

 

If the build of WAPT is current, most probably, the problem is in incorrect transfer of session parameters. Please send to us your scenario, profile, Full and Error logs generated by WAPT. Also, it would be of help to have a link to your application.

 

 

Im using the latest build that is 5.0 WAPT ....

 

Regarding 2nd possibility, I can just share the following information with you:

 

HTTP/1.1 401 Unauthorized

Date: Wed, 03 Dec 2008 08:20:22 GMT

Server: Microsoft-IIS/6.0

WWW-Authenticate: Negotiate

WWW-Authenticate: NTLM

X-Powered-By: ASP.NET

X-AspNet-Version: 2.0.50727

jsonerror: true

Cache-Control: private

Content-Type: application/json; charset=utf-8

Content-Length: 91

 

 

I hope this info is sufficient for you to trace the problem. :-)

[Guest angela]

Im using the latest build that is 5.0 WAPT ....

 

Regarding 2nd possibility, I can just share the following information with you:

 

HTTP/1.1 401 Unauthorized

Date: Wed, 03 Dec 2008 08:20:22 GMT

Server: Microsoft-IIS/6.0

WWW-Authenticate: Negotiate

WWW-Authenticate: NTLM

X-Powered-By: ASP.NET

X-AspNet-Version: 2.0.50727

jsonerror: true

Cache-Control: private

Content-Type: application/json; charset=utf-8

Content-Length: 91

 

 

I hope this info is sufficient for you to trace the problem. :-)

 

5.0 is the version of WAPT, and the latest build is of September 26, 2008

 

You can check the date of the latest build in your program in Help menu - > About WAPT... tab

 

 

[Guest hasan]

5.0 is the version of WAPT, and the latest build is of September 26, 2008

 

You can check the date of the latest build in your program in Help menu - > About WAPT... tab

 

thanks for the response ...

hmmmMMM ... its March 2008 ....

latest build is available at?

[Guest angela]

thanks for the response ...

hmmmMMM ... its March 2008 ....

latest build is available at?

 

You can get it on our official website http://www.loadtestingtool.com/download.shtml

[Guest angela]

You can get it on our official website http://www.loadtestingtool.com/download.shtml

 

Since you have NTLM, the first response in this case always has 401 error code. This is a standard behavior. Then the login is sent, and authorization occurs. Without logs we cannot tell whether authorization was successful or not.

 

 

 

[Guest testing]

Since you have NTLM, the first response in this case always has 401 error code. This is a standard behavior. Then the login is sent, and authorization occurs. Without logs we cannot tell whether authorization was successful or not.

 

We encounter similar problem in testing .NET application.

 

We are using IE6 with WAPT 5.0 (Jan 29 2009 version).

 

How to fix the 401 error?

 

Thanks!

 

[Guest testing]

We encounter similar 401 access problem with IE6 and WAPT 6.0

 

How can we resolve the issue?

 

 

 

[sergei 0]

Send a profile and full log to support@loadtestingtool.com, please.

[Guest testing]

Send a profile and full log to support@loadtestingtool.com, please.

 

Thanks! We have solved the case by saving a dummy user/password into the profile.