nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

External task failing

swatis

I have an external task which uploads all the workflow related variables to the database using perl dbi. On my environment everything is working fine but when i moved my code to the client server i found that the task is failing. When i run the same script from command prompt and passing it jobid, taskid as arguments the task doesnt fail. When i run this script as part of workflow it fails at dbi->connect($dsn) but the same executes when the script is executed from command line.

Could it be that the user who is the owner of this task doesnt have much rights on the database. Still i come back to the same problem if its a role issue then the user should not be able to execute this command from command line without an error.

Please guide me.

Find more posts tagged with

Comments

ISCBorisB

I have an external task which uploads all the workflow related variables to the database using perl dbi. On my environment everything is working fine but when i moved my code to the client server i found that the task is failing. When i run the same script from command prompt and passing it jobid, taskid as arguments the task doesnt fail. When i run this script as part of workflow it fails at dbi->connect($dsn) but the same executes when the script is executed from command line.

Could it be that the user who is the owner of this task doesnt have much rights on the database. Still i come back to the same problem if its a role issue then the user should not be able to execute this command from command line without an error.

Please guide me.

Good chances are, your code does not set certain Environment variables required by DBI.

When you log-in directly your Environment is there, WF Engine however spawns external task process
under its own shell settings. That has been discussed few times in the Forum, take a look at [thread=31968]this[/thread] thread
for example.

Snap 2015-07-23 at 16.49.13.png

Snap 2015-07-23 at 16.49.27.png

swatis

If it would have the problem it should not have been working fine on my development environment. The problem arouse when i migrated my code to my client's environment. On my dev env the code is still working file,inserting and updating database.

Adam Stoller

If it would have the problem it should not have been working fine on my development environment. The problem arouse when i migrated my code to my client's environment. On my dev env the code is still working file,inserting and updating database.

It's possible (though certainly more likely for a CGI task rather than external task) that you have something configured with regard to iwwebd to pass through certain environment variables or some such on your DEV box, but not on your client's environment.

Without having access to the code and the two environments, it is difficult to tell what's going on.

SalesInvoice.rptdesign

OS_BIRT_442_Topic36969_SalesInvoice_MultipleOrderNumbersAndPages.rptdesign

Bhargav Coca

I have an external task which uploads all the workflow related variables to the database using perl dbi. On my environment everything is working fine but when i moved my code to the client server i found that the task is failing. When i run the same script from command prompt and passing it jobid, taskid as arguments the task doesnt fail. When i run this script as part of workflow it fails at dbi->connect($dsn) but the same executes when the script is executed from command line.

Could it be that the user who is the owner of this task doesnt have much rights on the database. Still i come back to the same problem if its a role issue then the user should not be able to execute this command from command line without an error.

Please guide me.

I suggest you spend sometime debugging your external task Perl Script with Proper significant Print statements to a logfile. And post the logfile with comments in it. Also post your DBI snippet, how you are making a call. First and formost is what your Db Env and whats U'r client Env?

Thanks

Migrateduser

I have an external task which uploads all the workflow related variables to the database using perl dbi. On my environment everything is working fine but when i moved my code to the client server i found that the task is failing. When i run the same script from command prompt and passing it jobid, taskid as arguments the task doesnt fail. When i run this script as part of workflow it fails at dbi->connect($dsn) but the same executes when the script is executed from command line.

Could it be that the user who is the owner of this task doesnt have much rights on the database. Still i come back to the same problem if its a role issue then the user should not be able to execute this command from command line without an error.

Please guide me.

If you're running windows, did you by chance create a "user" dsn on the server and not a "system" dsn. A "user" dsn would only be available to you, which is why it works when you run it from the command prompt. Where as a system dsn would work for everyone.

swatis

I was able to solve the issue. the problem was occuring as i was not using the connect() function with username and password although it works fine on my environment without usename and password coz both sql server and teamsite are installed on same server. But on my client environment they are on different server so it connect() was not able to login to that server using my windows authentication. I had to provide password to my script to log in to the other env. and had to make chanegs in the system dsn to use user authentication. I know providing password in the script is not good so we looking into alternative for this to use viper or something like this.

HeaderNotVisible.pdf

HeaderVisible.pdf

header_example.rptdesign