Waiting in Queue

(0) Share

Report

Posted on by Community Member

Hello,

I have been tasked with setting up an application server for Transaction Import within SL Dynamics. I have been able to create the server, and successfully send email TI requests. I am in a test environment but eventually it will be a dedicated desktop environment for employees to send requests to.

Transaction Import works by itself.. processing DTA files with the control files and everything no problem. As soon as I use Transaction Import with Application Server it goes to the Queue, it says "waiting in queue" and the screen will pop up (in this case Journal Transaction) and nothing will auto fill..it will be in "beginning" stage for hours with no forward movement. I'm not sure why this is happening. Any thoughts?

*This post is locked for comments

All responses (2)

Answers (0)

Community Member on at

Like (0)

Report

RE: Waiting in Queue

I don't think it's a read/write issue as far as I can tell. The temporary folder is established as soon as I create the Application Server and it's a freshly created folder.

I have all screen permissions granted. I went through the Access Rights Maintenance as Administrator and gave myself full access to all Application Server/Transaction Import/Journal Transaction screens, view, update, everything.

What about this:

Could it be that I'm trying to send the request from the same computer that's hosting the App Server? Would I need an employee with SL Dynamics to send a request from a different device?

Could it be because I am in a test environment within SL?

Also, how long does this process take, really? Could it possibly finish processing after a couple hours for one request?
Erich Strelow F 16 on at

Like (0)

Report

RE: Waiting in Queue

I've been using Application Server TI for some time now, but not really with e-mail based requests. An issue that would prevent the TI process to complete is access problems with the temporary folder. Each application server instance has its own temporary folder and needs reed/write access to it. Check also the screen permissions of the submit userid. There's also a bug in some AS versions that prevents the TI job to target the submitted company.