![]() |
![]() ![]() ![]() ![]() ![]() |
![]() ![]() |
![]() |
|
![]() ![]() |
Author | Message |
rima
Newbie ![]() Joined: 25Apr2007 Online Status: Offline Posts: 1 |
![]() ![]() ![]() Posted: 25Apr2007 at 10:59pm |
Scripts are not being generated for my application. I am testing on
application that uses the following to communicate with the server:
The application will use a combination of ODBC, OLE/DB and embedded SQL (Oracle SQL*Net) to communicate with the database. So in Loadrunner vugen, I made a combination of ODBC and COM/DCOM for my testing but the scripts are not generated. I tried other combinations where possible but no scripts/actions where generated. In some cases, loadrunner will not let me combine oracle application with ODBC or SQl or Oracle NCA. So I am a little confused on what to do. Please help! What can I do to resolve this problem? Do you think the problem is comming from my protocol or do you think its a problem with other loadrunner functions? Please advice! Loadrunner Version: 8.1 Build #: 1793 Comes with the following all 8.1: Analysis Consol COntroller ERP and CRM Mediator Launcher Load Generator LTAgentCommon MI Listener Component Monitors Over Firewall ETC Post Resume: Click here to Upload your Resume & Apply for Jobs |
|
![]() |
|
debdas
Newbie ![]() Joined: 26Apr2007 Online Status: Offline Posts: 1 |
![]() ![]() ![]() |
Common causes of script not being generated for a given recording session
* Recording wrong protocol. You think the application uses one interface, but it does in fact use another altogether. Speak with your development staff to confirm. * API not supported. You could have a variant of a commonly supported protocol which is too new for your release of LoadRunner * Unsupported OS configuration. Your version of LoadRunner is running in an environment not supported. An example, LoadRunner 5.02 on Vista. * Firewall/Anti Virus impact. Becuase of the way LoadRunner operates to collect information, the behavior can at times be viewed by an Anti Virus program as a bad player in the system and thus be prevented from capturing anything. * Application makes no calls to other services. You are recording a file based system which makes no calls to remote services. * Out of process communication. Process A is started by LoadRunner VUGEN for recording. Process A communicates to Process B on the same box. Process B's communication upstream is not recorded. Process B then communicates with the database server. See bbhook references on Mercury website. * You have picked to competing protocols to record with. Pick one and retyr to see what happens. |
|
![]() |
|
![]() ![]() |
||
Forum Jump |
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
© Vyom Technosoft Pvt. Ltd. All Rights Reserved.