Forum Discussion
Stephane
I did not get a resolution to the problem (other than start my app outside AQTime and then attach to the process).
I decided not to purchase the program, so my problem has gone away (sort of).
I hope you had greater successd than me.
Andrew
Hi Andrew,
> I did not get a resolution to the problem
Sorry to hear this...
Did they replied that they can't find the reason of the problem or cannot implement the fix or did they asked for your program that you was not able to sent them because of company policy?
In the latter case, I know that SmartBear usually agreed to sign the NDA and I know several companies that went this way and got solution for their problems.
- Geocentrix7 years agoOccasional Contributor
Alex
They didn't put much effort into helping me with the problem. It was, basically, "run the app and then attach to it - that will work" rather than how to solve the problem itself.
I also found that the free 'trial' edition that comes with RADStudion failed to work out of the box - it left a very bad impression about the quality of the program.
Consequenctly, I have not purchased.
Andrew
- AlexKaras7 years agoChampion Level 3
Hi Andrew,
> free 'trial' edition that comes with RADStudion
Just to clarify things for myself: did you have problem with free edition provided with RAD Studio or with the Pro trial from https://smartbear.com/product/aqtime-pro/free-trial/ ?
IIRC, free edition is not supported by SmartBear but rather by Embarcadero.
If the problem was with Pro trial then it's just really strange that Support stopped their efforts on the 'attach to the app' recommendation.
- arthurqv6 years agoOccasional Contributor
I posted the other day about a similar problem, but in my company, we share AQTime licenses, and some developers can run from inside AQTime, and others have to attach to the running app they are instrumenting. Since we are supposed to all work eith the same tools and permissions, this is a conundrum. When AQTime fails to run the app from inside, the app appears in task manager, but is not running. The only correlation we have found so far between the working and not working AQTimes is that AQTime seems to work for the developeres who installed it ab out a year ago, and not for the recent installations, even though it is the same version for everybody. One significant thing that happened in between is that our company installed some "privilege management software", but it was installed for everybody and with the same privileges. So currently,we are at a loss to understand the difference.
We just tried with a barebone WIn32 application (the default project in VisualStudio 2015). When AQTime fails to run, it stops loading dlls after ntdll.dll (the first dll loaded after the executable file under scrutiny) . When it runs OK, it loads about 3 dozen dlls after ntdll.dll
Related Content
- 4 years ago
Recent Discussions
- 4 months ago
- 2 years ago