Comments
Sort by recent activity
Hi Daniel,
After a very quick test, it does seem that it's just the wizard that's affected. Create the project on another machine with all the correct options set in the wizard, save the project. Then open it on the Vista machine, and cancel the wizard immediately. You should then be able to just choose "start profiling" from the toolbar or menu, and it should work.
Note that I've only tested this on a tiny service that happened to be sitting on my Vista machine, so I don't promise it will work for you, but it should do!
Version 3 is currently planned for Q2 2007, though we don't have a more specific date at this stage.
Thanks,
Robert / comments
Hi Daniel,
After a very quick test, it does seem that it's just the wizard that's affected. Create the project on another machine with all the correct options set in the wizard, save the project. T...
Note: there's a slight bug in that workaround. About 5 minutes after you start profiling, ANTS will pop up a message box stating "Object reference not set to instance of object" or similar.
This didn't affect my profiling, so hopefully it should just be an irritation.
Rob / comments
Note: there's a slight bug in that workaround. About 5 minutes after you start profiling, ANTS will pop up a message box stating "Object reference not set to instance of object" or similar.
This di...
Hi,
Thanks for the report - I can confirm that I see the same thing here, even with all the usual access controls set as lenient as possible.
Because we released ANTS 2.7.1 before Vista was finalized, we weren't able to test all features at that point.
We're aiming for full Vista support in ANTS Profiler 3, at which point obviously that problem will be resolved.
Many thanks,
Robert / comments
Hi,
Thanks for the report - I can confirm that I see the same thing here, even with all the usual access controls set as lenient as possible.
Because we released ANTS 2.7.1 before Vista was finaliz...
Hi Joe,
When you start profiling in IIS5, we attempt to set two environment variables (COR_PROFILER and COR_PROFILING_ENABLED) in the profile of the user that ASP.NET runs as. This is done whilst logged on as a batch job. After profiling is complete, we remove these again.
Hope that helps,
Rob / comments
Hi Joe,
When you start profiling in IIS5, we attempt to set two environment variables (COR_PROFILER and COR_PROFILING_ENABLED) in the profile of the user that ASP.NET runs as. This is done whilst l...
Hi,
Thanks for running through that. The message in step 5 needs a bit of elaboration - firstly, there's a slight typo in the code, and it really means "as the ASP.NET process user" rather than ASPNET explicitly. Secondly, error code 1385 means TestUser doesn't have permissions to log on as a batch job.
You can grant batch privileges as follows:
- Control panel
- Administrative tools
- Local security policy
- Local policies
- User rights assignment
- Log on as a batch job
- Add TestUser to that set
- (You may also want to add your domain user that you ultimately want to profile as here as well)
Finally, when you were running ASP.NET as the domain user, was this the same user as you logged on as, or a different one?
Thanks,
Rob / comments
Hi,
Thanks for running through that. The message in step 5 needs a bit of elaboration - firstly, there's a slight typo in the code, and it really means "as the ASP.NET process user" rather than ASP...
That's good news at least - it suggests that we're picking up the username and password correctly.
The configurations where the ASP.NET user is the same as the logged on user are expected to fail - we don't want to modify the profile that's currently active.
This now just brings it down to the difference between the domain user and TestUser. Here my knowledge of the intricacies of Active Directory and GPOs is a bit lacking, so this may or may not be a sensible suggestion, but is it possible that some domain security policy is preventing you from modifying the TERRA\JICSvcAdmin profile?
As a potentially useful (if slightly bizarre) test, if you log on as TERRA\JICSvcAdmin, change the wallpaper, then log off and log back on, is that change retained?
Rob / comments
That's good news at least - it suggests that we're picking up the username and password correctly.
The configurations where the ASP.NET user is the same as the logged on user are expected to fail -...
Hi,
Bother, that would've been an easy solution :-). You're right in saying that enable="true" is default (in .NET 2.0's machine.config at least), but the ANTS code didn't make that assumption, I think.
Am I right in thinking (with the machine.config like that) that you still aren't getting any error messages until you come to finish profiling, at which point it tells you that the .NET framework was not loaded?
Another thing that could be worth trying is running it as a local system user that isn't ASPNET - this would maybe isolate whether it's the fact it's a domain user causing a problem, or just the fact that it isn't ASPNET.
The setup I tested this on most recently was a clean install of WinXP SP2, IIS, ASP.NET 2.0 / .NET 2.0, and the domain user added to a member of the local Administrators group. I also added the domain user to the "log on as a batch job" set in the local security policy.
Rob / comments
Hi,
Bother, that would've been an easy solution :-). You're right in saying that enable="true" is default (in .NET 2.0's machine.config at least), but the ANTS code didn't make that assumption, I t...
Hi Joe,
If you're still watching this thread, could you quickly try this for me?
In your machine.config file (in the .NET framework directory -> config directory), could you see whether the "processModel" element (which should have details of your username and password for the ASP.NET worker process) has an "enable" attribute set on it?
If not, could you try adding enable="true", and try profiling again? That means it will look something like: <processModel userName="DOMAIN\User.Name" password="P@ssw0rd" enable="true" />
I'd be interested to know if that helps...
Rob / comments
Hi Joe,
If you're still watching this thread, could you quickly try this for me?
In your machine.config file (in the .NET framework directory -> config directory), could you see whether the "proces...
Hi Nick,
If you haven't already, could you create a directory called "logs" in the ANTS Profiler installation directory? Having done that, restart the ANTS Profiler Service and ANTS Profiler itself and try profiling your website again. That should cause two or three log files to be created in the logs directory. I'll PM you my email address - if you could send them over, I'll take a look at them.
Thanks,
Rob / comments
Hi Nick,
If you haven't already, could you create a directory called "logs" in the ANTS Profiler installation directory? Having done that, restart the ANTS Profiler Service and ANTS Profiler itself...
Hi Nick,
If you go to the IIS manager in Control Panel, then navigate to the website you're trying to profile, right click and go to properties, then go to the home directory tab, you should see an "Application Protection" drop-down box at the bottom.
I've got mine set to "Medium (Pooled)", which I believe is the default, though quickly changing it to low, I still got the ASP.NET worker process to show up.
Maybe you can confirm that you're still able to debug ASP.NET applications by attaching to the ASP.NET process?
Rob / comments
Hi Nick,
If you go to the IIS manager in Control Panel, then navigate to the website you're trying to profile, right click and go to properties, then go to the home directory tab, you should see an...