Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Monday, November 25, 2024 
 
slxdeveloper.com Community Forums  
   
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
 Architect Forums - Legacy Development
Forum to discuss SalesLogix legacy development including views, scripts, etc.. View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to Legacy Development | New ThreadView:  Search:  
 Author  Thread: Custom Apps running via Scheduled Tasks
Stephen Savage
Posts: 3
 
Custom Apps running via Scheduled TasksYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 28 Apr 08 5:13 AM
Hi,

Running SLX v5.2 SP 4 on an Oracle 8i database.

We currently have numerous custom apps that connect/communicate with the SLX database via the SLXAPI. The have all worked fine for months now suddenly, we are haveing problems.

All the apps are set to run a scheduled tasks on the server and each of the produces its own log. What we see now is that all the tasks run on schedule, but the apps are unable to connect to the database.

When we run the apps directly, they all work perfectly - it only seens to be a problem when we run them via the scheduled task. Surely this should not have an impact on how the apps work???

It would also appear that if we reboot the server, everything works ok for about a week then the problem comes back.

Any ideas???

[Reply][Quote]
Dan Carvin
Posts: 227
 
Re: Custom Apps running via Scheduled TasksYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 28 Apr 08 11:21 AM
The first thing I would look at is which user the tasks are configured to run as.

If your interactive login has the rights needed to run the job, then they will work fine when launched manually. But if the user the Scheduled job is configured to run as lacks sufficient rights (or the password has expired or changed), then the job might not run successfully.

[Reply][Quote]
Stephen Savage
Posts: 3
 
Re: Custom Apps running via Scheduled TasksYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 29 Apr 08 3:14 AM
This is the problem though. When I log in to the server as the user that is set to run the scheduled task, but i run the app manually it does work ok.

When I run the scheduled task, it does run, and it starts the custom app but it is the app that logs the error about not being able to connect to SLX when it did it ok via the manual run. The app then finishes and then so does the scheduled task.

This is further confusing, given that it has worked for months and now suddenly does not work on the schedule.

Thanks,
Stephen
[Reply][Quote]
Dan Carvin
Posts: 227
 
Re: Custom Apps running via Scheduled TasksYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 29 Apr 08 10:00 AM
Are any old servers running Windows NT involved?

I don't know if this is related or not, but I worked on a similar issue a few months ago. It was a SQL Server job which suddenly began failing to connect when launched by SQL Agent, but still worked when run manually. FWIW, here's the KB article that pointed me to the solution: http://support.microsoft.com/kb/241643/en-us
[Reply][Quote]
John H. Hedges
Posts: 62
 
Re: Custom Apps running via Scheduled TasksYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 29 Apr 08 10:58 AM
If it works for a week or so after you reboot the server, it could be that machine (not user-account) passwords are expiring after a few days of console inactivity, possibly because of a newly-added domain password-expiration policy. That would also explain why it would work while a user is logged in, rather than as a scheduled task. It's also possible (though probably just as unlikely) that DHCP contracts are expiring, or even being reset by your DNS server (if you have one).

Also, are these programs reporting any specific BDE error numbers, or just "unable to connect"? Another implausible theory might be that execution permissions might have changed on the folder containing the BDE executables, in which case it should give you a different error number. It may even be that the BDE, or SQLORA8.DLL specifically, is using the Task Scheduler's own security context for the connection attempt instead of the account that you specified in the task setup, though obviously it's not supposed to do that.
[Reply][Quote]
 Page 1 of 1 
  You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

   Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
 

 
 slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.
 This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 11/25/2024 9:31:33 AM