Running LoadTest using Visual Studio 2017 Enterprise
with Test Controller 2017 and Test Agent 2017
The problem is sometime there will pop out
Result Collector Out of Memory Exception
After my research, knowing the root cause is because QTController.exe is run as 32bit
(Go Task Manager->"Details" tab -> select columns and select platform)
and its because
"Test Controller Configuration tool" set up the service"Visual Studio Test Controller"'s path to executable
to QTController.exe instead of QTController64.exe
Is there something I need to do after I change the "Test Controller" service's path to 64 bit?
Or is there a another way to set up the service to 64 bit?
I try to run command below:
sc config VSTTController binPath="C:\Program Files (x86)\Microsoft Visual Studio\2017\TestController\Common7\IDE\QTController64.exe"
the QTController64.exe can use more memory but new error come up:
1.loadtest screen freeze when warm up session ends
2."Failed to acquire a read lock" alert box pop out when loadtest finish running
Related
I suddenly can't debug anything in Visual Studio 2017 using IIS Express.
Symptoms
While debugging in VS2017, the output window shows the message below immediately.
The program '[13980] iisexpress.exe' has exited with code 0 (0x0).
Running IIS via Command Prompt:
"C:\Program Files (x86)\IIS Express\iisexpress.exe" /port:50896 /path:"C:\Users\XXXXXXX\Documents\Visual Studio 2017\Projects\BT\ManageOIC\EnterpriseMedicalReportTool\\" /trace:error
Error (rc=800703f1) in UlInitialize. Exiting
Error initializing ULATQ. hr = 800703f1
Copied template config file 'C:\Program Files (x86)\IIS Express\AppServer\applicationhost.config' to 'C:\Users\XXXXX~1\AppData\Local\Temp\iisexpress\applicationhost2018111183214194.config'
Updated configuration file 'C:\Users\XXXXX~1\AppData\Local\Temp\iisexpress\applicationhost2018111183214194.config' with given cmd line info.
Starting IIS Express ...
Initializing the W3 Server Started CTC = 3184968
W3 Server initializing WinSock. CTC = 3184968
W3 Server WinSock initialized. CTC = 3184968
W3 Server ThreadPool initialized (ipm has signalled). CTC = 3184968
Start listenerChannel http:0
Error (rc=800703f1) in UlInitialize. Exiting
Error initializing ULATQ. hr = 800703f1
Terminating W3_SERVER object
InitComplete event signalled
Process Model Shutdown called
Unable to start iisexpress.
The configuration registry database is corrupt.
For more information about the error, run iisexpress.exe with the tracing switch enabled**(/trace:error).
In the event viewer, the following error is noted:
The worker process for app pool 'IISExpressAppPool', PID='4504', failed to initialize the http.sys communication when asked to start processing http requests and therefore will be considered ill by W3SVC and terminated. The data field contains the error number.
Data field: 800703F1 - Err.exe suggests this may be a registry problem.
What I've Tried
Changing the port for IIS Express to several different open ports
Deleting the .vs folder in Visual Studio.
Running a different project.
Creating a new MVC web app and running it.
Reinstalling IIS Express via Microsoft Website. (And restarting after.)
Reinstalling IIS Express via Visual Studio Installer. (And restarting after.)
Repairing Visual Studio. (And restarting after.)
Manually running IIS from command line via command above on IIS 10.
Uninstalling IIS 10 and installing IIS 8
Manually running IIS from command line via command above on IIS 8.
Running sfc /scannow (No issues found)
Checked for recent Windows updates (none shown)
Updated visual studio
I have a SQL Server 2008 R2 CLR Database project with a table value function. The table value function runs select queries in order to preform it's logic. I want to debug this in VS 2010 so I can step through my code but for the life of me I can't figure out how to do it and I have read countless Blogs.
I have a test.sql file and I have set it as my default test script with a breakpoint in my CLR function. When I click the "Start Debugging" button from within my test script VS 2010 will go into not responding mode while it re-deploys my assembly and then after a few minutes VS 2010 will stop debugging with a message that it exited with code "0". It's like it never runs my code.
I have also tried selecting the function from the server explorer and clicking the "step into" option on the context menu but I just get an error that remote debugging is not setup on our development server. Do I need remote debugging enabled and if so how do I go about doing it the right way to get this to work. I have been at this for days and I am ready to pull my hair out. I even spent my weekend working on this. Please any help would be appreciated.
I downloaded http://www.microsoft.com/en-us/download/details.aspx?id=475 the Visaul Studio 2010 remote debugger from here. I ran the .exe to install on my local machine and the development server. After which I was able to use the "step into" feature under server explorer and step through my code.
I've created a windows service in C (using WinAPI) and I want Visual Studio to automatically attach to the process of the service when I start the service from the Services panel.
How can this be achieved.
P.S. Putting a MessageBox at the service's initialization function and than manually attaching is no the kind of solution I'm looking for.
I found the solution.Simply add the following key in the registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\THE_NAME_OF_YOUR_SERVICE_EXECUTABLE.exe]
And add the following value and data:
"Debugger"="vsjitdebugger.exe"
Note that you'll have to remove this value when you're done testing, otherwise Visual Studio will prompt a message to attach whenever the service is started.
This works under Windows XP x32. I haven't tested on anything else.
Place __asm int3; at start of your code or place where you want attach debugger.
This happens after I have run the profiler once. the profiler configuration is to watch a dll that is being executed by a separate executable.
The profiling works the first time but I then need to reboot my PC in order to run another profiling session.
What do I need to do to shut down the VS 2008 Logger Engine? What is the VS 2008 Logger Engine?
It sounds like you need to shutdown the logger. Open the Visual Studio Command Prompt (2008) from the start menu and then try:
vsperfcmd /shutdown
vsperfcmd /off
When I start my process from Visual Studio, it is always created inside a job object. I would like to know how to turn this behaviour off. Any ideas?
I expect that it is created in a job object to be debugged. I want to place my program in a different job object.
It's not the hosting process. I'm talking about a Job Object. This is an unmanaged C++ application.
This happens when devenv.exe or VSLauncher.exe run in compatibility mode. The Program Compatibility Assistant (PCA) attaches a job object to the Visual Studio process, and every child process inherits it. Check if the job name (as reported by Process Explorer) starts with PCA. If so, PCA can be disabled as described in the link.
You can globally disable PCA using Run -> gpedit.msc -> Administrative Templates\Windows Components\Application Compatibility -> Turn off Program Compatibility Assistant -> Enable.
You can disable PCA for specific executables by adding a registry entry. For Windows 7, the appropriate registry key is HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant. In regedit, right-click that key, select New -> Multi-String Value, name it ExecutablesToExclude. Set the value to the full path of denenv.exe and VSLauncher.exe, on separate lines and without quotes. For me, these were:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe
C:\Program Files (x86)\Common Files\microsoft shared\MSEnv\VSLauncher.exe
A related issue, on Windows 7, is that executables you build in Visual Studio and run from Explorer (not Visual Studio or the command line) may run in compatibility mode, and again get job objects wrapped around them. To prevent this, your executable needs a manifest that declares compatibility with Windows 7, using the new Application Manifest Compability section. The link gives an example of a Windows 7 compatible manifest. The default manifest provided by Visual Studio 2010 does not include this Compatibility section.
I'm not aware of any ways to control this aspect of processes spawned for debugging by VS.NET. But there's a workaround, which is applicable to any situation in which VS.NET can't or doesn't start your process in the exact way you want:
Start your process (possibly using a wrapper EXE that runs as part of the post-build event), then attach to the newly started process using Tools/Attach to Process. If you break into the debugger as part of your startup code, this won't even be required (and you can also debug startup issues...).
I can't reproduce what you're seeing. I've created an unmanaged C++ application in both VS 2005 and VS 2008 and I have no problems associating that process to a new job object when starting the process in VS.
Are you sure the debugger is doing this?