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!
|
|
SalesLogix Agents stuck in Pending status
Posted: 25 May 07 8:14 AM
|
-W2K3 SP1
-6.2.6.1007
-SQL2000 SP4
-SalesLogix Server and Synchronization Server Services set with admin privlaged service account with membership of policies "Log on as service", "Log on as batch job" and "Access this computer from the Network".
Any type of Agent scheduled in the WGAdmin moves from "scheduled" to "pending" status after the "scheduled" time passes and does not reschedule again. As a result AgentRunner.exe and AgentQueue.exe hang in the task manager with no CPU utilization. 
|
|
|
| |
|
Re: SalesLogix Agents stuck in Pending status
Posted: 18 Jul 07 9:36 AM
|
| My only guess as to what might be happening is that the task has an error in it. You probably already know this, but you can't use the Application object in an agent task that you can normally use in SalesLogix code - I think that would cause what you are seeing. If you could post the code you are trying to run in the agent, that might help. Always nice to have more than one pair of eyes on code. Also, it was very nice moving to SQL Server 2005 - the ability to set up ActiveScript jobs is wonderful, and I don't ever have to worry about fickle SalesLogix agents. |
|
|
| |
|
Re: SalesLogix Agents stuck in Pending status
Posted: 18 Jul 07 4:00 PM
|
| I've had this exact problem and it was a problem with the code in my agent. Make sure your agent isn't erroring out by running it from a tool bar button within the application. Also in v7.0 I had a problem with an agent I was running because it used the application object and that isn't allowed in an agent because the application isn't open. |
|
|
|
Re: SalesLogix Agents stuck in Pending status
Posted: 18 Jul 07 8:55 PM
|
Hi Jeff - I was interested in your comment about moving to SQL Server 2005. Can you elaborate on what you are able to do now that you could not do in SS 2000 please?
Cheers
Phil |
|
|
|
Re: SalesLogix Agents stuck in Pending status
Posted: 19 Jul 07 9:27 AM
|
Man, you had to call me out on that one, didn't you? Ok, I just checked, and you can run ActiveScript jobs in SQL Server 2000 as well - so I guess everything I'm doing in SQL Server 2005 can be done in SQL Server 2000. However, there are performance benefits and greater processing capabilities in 2005. You can go to http://www.microsoft.com/sql/techinfo/whitepapers/why-upgrade.mspx to see if any of the benefits are worthwhile. I also found reviewing the job history is a bit simpler in 2005 as well.
Anyway, I didn't know about running VBScript in SQL Server until after I had upgraded to SQL Server 2005, which is why I made that less-educated remark... :P But, my point was that I have spent a bunch of time figuring out, dealing with, and getting frustrated with SalesLogix Agents, and I had a wonderful time getting SQL Server VBScript jobs to run. Since you can't use the Application object in either the SLX Agents or the SQL Server Jobs, I recommend using the SQL Server jobs - much smaller headache and greater reliability. I would think the only time you would want to use a SLX Agent is if you wanted to email one of the reports in SalesLogix or run a remote task.
Anyway, those are my thoughts, and I tried to research them a little better this time...  |
|
|
|
Re: SalesLogix Agents stuck in Pending status
Posted: 19 Jul 07 5:00 PM
|
 Sorry Jeff, I wasn't trying to score any points - I promise I was genuinely interested!
As for the benefits of moving to SQL Server 2005 - I was sold within 10 minutes of migrating. The user interface is so much better, regardless of any performance improvements. There is also a suggestion that support for SS 2000 will be dropped later this year, though I am not sure that will actually happen, given the huge numbers of users who have yet to migrate.
Another advantage of running SQL Server jobs rather than SLX agents is that it doesn't matter which level of SLX you have purchased. |
|
|
|
Re: SalesLogix Agents stuck in Pending status
Posted: 19 Jul 07 5:13 PM
|
Absolutely agree on the user interface - it is much nicer than SS 2000!
Yeah, I figured you were genuinely interested. I was just caught speaking before I truly thought it out... 
|
|
|
|
Re: SalesLogix Agents stuck in Pending status
Posted: 23 Jul 07 9:33 AM
|
Originally posted by Ian Fitzpatrick
I've had this exact problem and it was a problem with the code in my agent. Make sure your agent isn't erroring out by running it from a tool bar button within the application. Also in v7.0 I had a problem with an agent I was running because it used the application object and that isn't allowed in an agent because the application isn't open. |
|
Ian,
This is exactly the situation I had. For this agent the service account that runs the SLX Server service is required to have SalesLogix.exe running in memory.
To resolve this without having to physically keep the service account logged in to the console with SalesLogix.exe running I made a scheduled task that kicks off minutes before the agent kicks off. It runs SalesLogix.exe as the service account for the duration of the Agent, then closes the process.
Thank you everyone for your input. I have finally put this issue to rest!
|
|
|
|