TinyGet and stress testing - asp.net

I am trying to use TinyGet t stress test an application. I am running the following command:
"C:\Program Files\IIS Resources\TinyGet\tinyget.exe" -srv:localhost -uri:/testwebsite/default.aspx -loop:10
It appears to work as there is no error message. However, the ASP.NET process does not appear. Should the ASP.NET process appear?
Is there any documentation for TinyGet.
Update 17/07/2012
Is anyone able to confirm that the thread flag (http://code.google.com/p/toolsdotnet/wiki/TinyGet) is referring to the number of worker threads, IO threads or both?

I installed the IIS toolkit on a Windows XP PC with IIS 5.1 (development PC). I have now installed it on a Windows 2003 server and it works as expected.

Related

Cannot attach to w3wp process in VS 2022

I have web app running locally in IIS. App of Net Framework 4.7.2. When I tried "Attach to Process" for w3wp process in Visual studio I am unable to do so. Visual Studio is running under Administrator account. Things I tried:
Restart of IIS and VS in different sequence.
Setting "Enable 32-bit Applications" flag on app pool in IIS to true
Tried to run process monitor to see if there would be errors. Nope, no errors.
Tried manually set type of app in "Attach to" combobox to various types with same results. Types tried: Managed 4.x, with and without Compatibility mode, Managed(Native compilation), Native.
Tried Visual Studio repair - still having issue.
Created brand new web app .Net Framework 4.7.2, deployed it under IIS and tried to attach to the w3wp process and got same issue.
Things I noticed:
When I tried to attached to 64 version of the w3wp the type is "Managed Net 4, x64" and I am getting "Unable connect to the process" message with justification: VS must run as administrator. Funny thing: VS IS running as administrator.
When I turn 32-bit application flag on I am getting type as x86 and plain "Access denied". Even if restart IIS and try to access the app to start new w3wp process. I think it should be: "Managed Net 4, x86", but I am not 100% sure.
At this point I am out of ideas. Any help would greatly appreciated
UPDATE.
I noticed, when I turn on 32bit applications on app pool in IIS I am getting following error in Event Viewer:
"The description for Event ID 0 from source .NET Runtime cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer."
Turned out corrupted Avecto installation was the culprit. Reinstalling offending software resolved the issue. Live and learn. At least I lived.:)

Unable to attach to application [iisexpress.exe/webdev.webserver40.exe]

As of right now, I'm unable to debug any of my ASP.NET web application projects on a completely fresh machine because of the error message above. I'm trying for hours now and it's driving me completely nuts because I'm getting paid for working, not for debugging strange environment errors. :/
Installation Procedure / Environment
Installed Windows 8 Professional x64
Installed Visual Studio 2012
Installed Visual Studio 2012 Update 3
Installed IIS through Windows Programs And Features
Nothing else has been done - no addins, no further configuration etc. Administratior permissions are available...
Error message
Unable to attach to application 'webdev.webserver40.exe_00001254_
01ce76431af5c900_dc2119bc-2761-480f-b975-4fab7ad27f390'
(PID: 4692) using '*myhostname*'.
Operation not supported. Uknown error: 0x80040d10.
Do you want to continue anyway?
Same error occurres with Local IIS Web Server (IISExpress too...)
Solutions
In other forums / threads, various solutions have been mentioned, but none of them really fixed it.
Rebooting machine
Reinstalling VS
Terminating running web server instances
Has anyone else faced this annoying error?

Can't install IIS7 and ASP.NET 3.5 on Win7 64-bit

Using Win7 32-bit for 3 months and didn't have problem with developing any .NET-based applications including ASP.NET apps.
Just upgraded my laptop's RAM 3 days ago and switched to 64-bit version of Win7.
When I'm working on installing IIS7 and .NET Framework 3.5 SP1, there's an error about not all features were installed for some unknown reason.
When I try to register ASP.NET using aspnet_regiis -ir in c:\Windows\Microsft.NET\Framework64\v2.0.50727\, a dialog box shows with this error message:
"Operation failed with 0x80070643" and after I close the dialog box, another error message on the console command shows with this message: "An error has occurred: 0x80004005 Unspecified error".
I had the same problem and I did everything found on the internet but nothing was useful
eventually I was able to solve it by using the following:
note: do it on your own risk
Add the following to you registry only if the doesn't exist (in my case they didn't exist):
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_2.0.50727]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_2.0.50727\Names]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_2.0.50727\Performance]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_64]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_64\Names]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_64\Performance]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_64_2.0.50727]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_64_2.0.50727\Names]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_64_2.0.50727\Performance]
try installing asp.net 64 bit after that
Configure IIS to run in 32 bit mode (assuming your apps are 32 bit mode, since that's what you originally developed on).
http://learn.iis.net/page.aspx/201/32-bit-mode-worker-processes/
Try running aspnet_regiis after that is done. Use the 32 bit version of aspnet_regiis.
I know this is a fairly old post, but I thought I'd share what I did to solve this problem on my machine running Windows 7 64-bit.
While IIS was installed on my computer, the ASP.NET features were not enabled.
To enable ASP.NET do the following:
Navigate to the Turn Windows features on or off dialog. It's located under
Control Panel --> Programs and Features.
Note: Typing 'features' in the Start Menu search will also get you there.
When the Turn Windows features on or off dialog appears, navigate to World Wide Web Services --> Application Development Features
and make sure ASP.NET is checked.
Once this was done the aspnet_regiis -ir command worked perfectly and I could run and debug ASP.NET apps on my machine.
Hope this helps.
set IIS to run in 32 bit mode
http://learn.iis.net/page.aspx/201/32-bit-mode-worker-processes/
Try running aspnet_regiis after that is done. Use the 32 bit version of aspnet_regiis.
بریده جراید

BadImageFormat Exception with Oracle 64 bit client running on Win 7 X64

I've run into a problem after installing the 64 bit Oracle client onto my Win 7 x64 dev box. I have installed and configured the oracle client and added a reference to it in my library project and it runs without problems when deployed to a Win 2008 R2 server; however I cannot run it in the built-in VS2010 debugger.
The code throws a BadImageFormatException when the .open() statement is called on the connection object.
I figured out that if I will run it in IIS and move the application out of the default application pool, the error goes away for some reason.
However, I can't do this when I'm running the test project (MSTest) and I the result is that I cannot run unit tests against this code. Yes, I can mock it, but I would really like to understand and eliminate this error. There are several cases where I would like to test against some test data in the database.
Any suggestions or links would be greatly appreciated.
Thanks,
Trey Carroll
Here's the answer according to senior dev in my group VS is a 32 bit application so running things in Casini is of course from a 32bit context. When the 32bit Web Appattempts to use the 64bit Oracle Client, it causes the BadImageFormatException. (Apparently deploying to IIS is allowing the Web App to run as a 64bit app and eliminating the conflict.)
So here's the question: How do I run MSTEST unit tests from VS when there are dependencies on 64bit dll's? I could obtain 32bit versions of these, but how would I tell my application to use the 32bit versions for testing/Casini debugging and the 64bit versions otherwise?

Configuring 32-Bit ASP.NET Application on a 64-Bit IIS Server

I’m trying to install a 32-bit ASP.NET application onto a 64-bit IIS server running on Windows Server 2008. This is a clean installation of the operating system with no other applications installed.
As a prerequisite for our installation, we run the 32-bit version of aspnet_regiis –i
It fails with the following message:
The error indicates that IIS is not installed on the machine. Please install IIS before using this tool.
Additionally:
IIS is definitely installed.
The 64 bit version of aspnet_regiis runs cleanly without warnings.
“Enable 32 bit applications” is set to True in the DefaultAppPool’s Advanced Settings.
The IIS Metabase and IIS 6 configuration compatibility” component is installed.
We have a test VM where this error occurs as well as test VM where both the 32 bit and 64 bit versions of aspnet_regiis run without errors. We've had no luck distinguishing the differences between the two test VMs.
We have struggled with this issue for several days to no avail. Any suggestions would be greatly appreciated!
Is it necessary to run aspnet_regiis? 32 bit asp.net should already be installed and running on iis7, all you should need to do is set the app pool to “Enable 32 bit applications” and set you web app to use that app pool. You do not say what happens when you install/setup your web app, do you get any errors when you try to access it in a browser?
Problem solved! Apparently the issue stems from Windows Server 2008 (R1). Applying the SP2 update to the operating system cures the problem. Later iterations of the OS don't seem to exhibit this behavior.

Resources