Error Creating Product Object Db2
LEI; LSXLC agent; lsxlc; agent; fails; agent fails; failing; crash; crashing; error; Error creating product object; LotusScript debugger; lotusscript; script; code; debug; debugger; LCConnection; db2 Technote (troubleshooting) Problem An LSXLC agent fails with the following error message: "Error creating product object." The LotusScript debugger reveals that the agent always fails on the line that declares the LCConnection, such as Set src = New LCConnection("db2"). This can also occur for Lotus Enterprise Integrator (LEI), and for Domino Enterprise Connector Services (DECS), that connect to a back-end database. Cause This error indicates that the files required to make the connection are missing or otherwise cannot be found or used. For example: -- If connecting from Microsoft Windows, the DB2 client on Windows is not installed. Alternately, if the path to the DB2 Connector files is not in the system's Path statement, then the connector cannot be found. -- If connecting from the iSeries, one or more of the following conditions may exist: The db2.srvpgm file on the iSeries is missing or unreadable. The iSeries db2 group PTF may not be up to date. The Relational Database Directory Entry table in the iSeries may not contain an entry for the target DB2 database. Check using the command WRKRDBDIRE. If you are creating an iSeries LC connection to a source that requires the data direct drivers (any ODBC connection such as SQL or Oracle), these drivers may not be correctly installed or the data source in the odbc.ini file may be incorrectly filled out. -- On AIX, the path statement may not be correctly filled out, and thus the connector cannot be found. The environment variables PATH, LIBPATH, and LD_LIBRARY_PATH must all contain the path to the connector. For example, to use the DB2 Connect Client, you would need something like this in each one: /home/db2clnt/sqllib/lib. There is also a DB2Instance environment variable on AIX that must be filled out. For example: DB2INSTANCE=db2clnt Note that your DB2 Instance may be named something different than db2clnt, that is provided as an example. -- You may have correctly configured a DB2 connection on one machine, but are accidentally running the age
Unix platforms created; LotusScript; Agent; LSXLC; run; agent; error; Error Creating Product Object; does not run Technote (FAQ) Question You have created a LotusScript Agent using LSXLC. When trying to run the agent, the following error occurs: "Error Creating Product Object" and the agent does not run. Answer This problem can occur for two reasons: The Unix user account that runs the Domino server does not have access to the RDBMS files that http://www-01.ibm.com/support/docview.wss?uid=swg21305189 are owned by the relational database Unix user. Required environment variables are not set to enable the agent to run on a Unix platform. For the first cause, add the Notes user to the Oracle, DB2, Sybase", etc. Unix group that owns the required relational files. For the second cause, add the required environment variables as http://www.ibm.com/support/docview.wss?uid=swg21205676 follows: AIX Environment Variables : Set and export the following environment variables in your appropriate configuration file (such as .login or .profile) so that they will be accessed each time you log on and invoke LEI. 1. Ensure that the LANG environment variable is correctly set to your proper locale and is exported. If this is not set, the default "C" is used. LANG=C 2. Ensure that the environment variable LOTUS is set as shown below: If you use the C shell, your .login file should contain the line: setenv LOTUS /opt/lotus For sh or ksh, your initialization file should contain the following: LOTUS=/opt/lotus; export LOTUS 3. Ensure that the environment variable Notes_ExecDirectory is set to specify the Notes executable directory and that the environment variable is exported. Notes_ExecDirectory=/opt/lotus/notes/latest/ibmpow 4. Ensure that the environment variable PATH is set to include the following directories and that the environment variable is exported. Notes Resource directory: $LOTUS/notes/latest/ibmpow/res/$LANG Lotus executable directory: $Notes_ExecDirectory Notes data directory (locates notes.ini file; for example /home/notes/notesdata) Fo
and Development View All Ajax Development Security Eclipse HTML J2EE Java JavaScript LEI and DECS Domino Designer Application Development Formula LotusScript Mobile and Wireless Development Web Development XML and Web Services http://searchdomino.techtarget.com/answer/Oracle-through-DECS-via-the-Web-connection-returns-Error-creating-product-object IBM Lotus Messaging and Collaboration Clients View All Domino Web Access (iNotes) Lotus Notes 5 Lotus Notes 6 Lotus Notes 7 Lotus Notes 8 Lotus Sametime Instant https://www.experts-exchange.com/questions/20449235/Error-creating-product-object-when-run-an-agent.html Messaging Mobile Devices IBM Lotus Messaging and Collaboration Servers View All IBM WebSphere Lotus Domino Server 5 Lotus Domino Server 6 Lotus Domino Server 7 Lotus error creating Domino Server 8 Lotus Quickr Notes/Domino Administration View All Domino Directory Administration Tools AdminP LDAP Calendar and Contact Management Interoperability Licensing Monitoring and Logging Performance User Settings Notes.ini Notes/Domino Coding and Development View All Ajax Development Security Eclipse HTML J2EE Java JavaScript LEI and DECS Domino Designer Agents Application Development Formula LotusScript Mobile and error creating product Wireless Development Web Development XML and Web Services Notes/Domino Data Management and Storage View All Archiving Backup and Recovery Clustering Database Management Hardware Management Mailbox Management Replication and Synchronization Storage Management Notes/Domino Deployment and Migration View All Deployment and Migration Advice Deployment and Migration Tools Notes/Domino Security View All Compliance Management Compliance tools Access, Permissions and Authentication Antispam Software and Spam Filtering Antivirus Software and Virus Protection Email Compliance Email Encryption Firewalls Password Management Phishing and Email Fraud Protection Policy Management Topics Archive View All Domino Resources Domino Resources - Part 2 Domino Resources - Part 3 Domino Resources - Part 4 Domino Resources - Part 5 Domino Resources - Part 6 Domino Resources - Part 7 Domino Resources - Part 8 Please select a category IBM Lotus Messaging and Collaboration Clients IBM Lotus Messaging and Collaboration Servers Notes/Domino Administration Notes/Domino Coding and Development Notes/Domino Data Management and Storage Notes/Domino Deployment and Migration Notes/Domino Security Section Problem Solve News Get
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Error creating product object when run an agent. Want to Advertise Here? Solved Error creating product object when run an agent. Posted on 2003-01-08 Lotus IBM 1 Verified Solution 5 Comments 2,796 Views Last Modified: 2013-12-18 Hi experts, I created an schedule Agent, it can run no error in manual mode, but when it run automatic at midnight as schedule it always send out a message "Error creating product object" in Event log and I cannot get the result. How can I fixed it. Thanks & Regards, Tuan. 0 Question by:tuancd Facebook Twitter LinkedIn Google LVL 24 Best Solution byHemanthaKumar Hello Tuan, You are using Notes UI objects in your agent, which is not supported for scheduled agents. Deal with backend methods, no frontend methods. Help documentation gives you more details about Go to Solution 5 Comments LVL 13 Overall: Level 13 Lotus IBM 13 Message Active 2 days ago Expert Comment by:CRAK2003-01-09 I've seen that happen before.... I was using an agent that was in it's turn using a LotusScript Library. It occured after releasing a new template containing the two, template signing by SA, design refresh in production and agent scheduling. As long as it's the plain agent code running, things run smoothly, but at the first call to the library the agent crashes. I haven't found a proper way to work around it, but having the libraries recompiled by SA first, and consequently having the agent recompiled by them (after signing) appears to work for now (untill the next release...). The problem even occurred when neither the agent nor the library were changed in the new release! Is this what happens in your case to? 0