Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Donate Today!

Do you enjoy these
technical forums?
Donate Today! Click Here

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

gavinrifkind (Programmer)
20 Jul 06 9:24
Good Day

I have the following problem which I would appreciate some help with

I have a Stored Procedure which executes a System command to call a 4GE program.
When executing the stored procedure directly on the server using DBACCESS,
everything works correctly.

I have written a Java application which calls the Stored Procedure using JDBC
The application works on some computers, but not on the others.

The error that it gets is "668 System command cannot be executed" and ISAM error
is "1 Not Owner".

Both computers are using the same login credentials, and the same version of the
JDBC drivers.

The executable 4GE has execute permissions for all users.

I also have similar results trying to execute the Stored Procedure with other
JDBC clients eg. SQuirreL SQL. It works on some computers but not others.

Please can somebody point me in the right direction.

Thanks
Gavin Rifkind
mishradd (Programmer)
25 Jul 06 2:20
Did you check the finderr 668 code, check following points

1. Make sure that the system command is not trying to run something that is not in your path or that is not applicable to the environment.
2. Make sure that you have provided a user-id and password when connecting  to the database server. The database server must have the user's password in order to execute a command on behalf of that user.      
3. your procedure should have execute permission for that user.

hope this helps
              

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close