Error while executing plugin

With the PlanetPress Connect User guide close by and quite some help from several users on this forum - thanks again guys - I’ve succeeded in creating my first datamapper and template. Since this one is by far the most complex one I will - hopefully - ever have to create, I’m pretty pleased with the result.

On to the second step. The workflow. I’m quite used to creating processed in PP7 but Connect is quite another beast.

My first problem is uploading my datamapper and template to the server. By company policy we’re running PP Connect Designer on our personal computer and not on the server. When pressing the “Send to workflow” menu option the server is most of the time not visible, leaving only the file destination. After going into that menu multiple times after a while the server suddenly appears. Can anyone tell me why this is?

My second problem is that once I have uploaded a datamapper/template and after making some changes to the one on my personal computer uploading it again doesn’t seem to “update” the one on the server. That is, when looking at the properties of the datamapper or template (under Connect Resources) it still shows the last modified date and time of the old version. If I delete the datamapper and the template and then try the “Send to workflow” option the files get uploaded and the properties show the expected date and time. Is this normal?

My third problem is that when I create the most basic of processes (folder capture, all in one, send to folder) and go through it in debug mode I always get this error message on the All in One step:

W3001 : Error while executing plugin: HTTP/1.1 403 Forbidden Your credentials don’t allow access to the requested resource. (SRV000101)
All in One: W1603 : Plugin failed - 16:30:24 (elapsed time: 00:00:00:019)

What are these “requested resources” mentioned in the error message and why do I get this message. I assume I have missed some setting somewhere, but I haven’t the faintest idea which one. Can anyone point me in the right direction?

One last bit of information that might be important. By company policy the user running the service is not the same as the user with which I log in to the server, but since all paths used in the datamapper (e.g. for external JS libraries) and the template (e.g. for external images) refer to a local drive available both on my personal computer and on the server I wouldn’t expect that to be a problem.

  1. Sounds like the messenger service is having difficulty communicating. This service is responsible for communication between systems running ObjectifLune software and communicates on ports 5863/5864 on both TCP and UDP. These ports must be open on all machines both in and out. It might be worth getting your networking team to take a look at the communication.

  2. This is a known issue and is strictly visual. The properties do not update properly but the document does. Closing and re-opening the workflow software will force the properties to refresh.

  3. It looks like Workflow has not been configured to use the same credentials as your Connect Server. You can check this by going into the Workflo Preferences > Behavior > OL Connect. The server address, port, username, and password should all match whatever you’ve configured in the Connect Server Configuration.

In regards to the Connect Server Configuration, do note that you can only open this while logged in as the same user that Connect is configured to use. Given your security situation, this may be difficult, but you’ll have to arrange it if you need to modify the Connect Server credentials.

Edit: If all else fails, I’d recommend calling in and opening a support ticket to go deeper.

Given that our local network admin is on holiday for the moment and that I would prefer to get going on, I’ll try to solve this myself. I do need some more info though. Here’s what I know and can do:

  1. The services OLConnect_Server, PP Image 8, PP Workflow 8, PP Workflow 8 FTPPut Client, PP Workflow 8 HTTP/SOAP, PP Workflow 8 LDP Server, PP Workflow 8 LPR Client, PP Workflow 8 Serial Capture, PP Workflow 8 Telnet Capture, PP Workflow 8 Messenger 8 are all configured to run with account XXX.
  2. The other services OL Connect Send DBServer, OLConnect_MySQL, PP Workflow 8 PrintShop Mail Web Capture and PP Workflow SMTP Server are configured to run with “Local System account”.
  3. When I log in to the server with account XXX, seach for Connect Server Configuration and open that I find under Server Security Settings that server security is enabled with ol-admin as the Administrator’s username and what seems to be the default password.
  4. When I log in to the server with the account I’m suppost to use, let’s call it ZZZ, and I open PP Workflow Configuration and go to Preferences > Behavior > OL Connect I see server address localhost and port 9340. Originally the username here was ol-admin. Before starting this topic I had already changed it to XXX. But in both cases I got an error.

Now here things become weird. While writing this I couldn’t remember if the error I got when Preferences > Behavior > OL Connect was set to its original ol-admin setting was exactly the same as the one in my original post. So I changed it back to ol-admin and ran my test process again. Figure this: no errors. I don’t get this. I just changed it back to what it was. That’s the only change I made. But hey, I have learned not to wonder why sometimes things magically start working.

Anyway, with the information above, are there things you would advise us to change? One last thing: we don’t use much of Connect: no telnet, no printer, no serial capture (whatever that is). We only pick up xml files and turn them into pdf files.

I’d only suggest switching the workflow to use an actual Windows account, rather than the default Local System account, but this is primarily for ease of debugging. That is, if your services run as the same account as what you’re logged in as, it’s easier to debug a process and know it will also work as a service.

But hey, if everything’s running for you, there’s no need to change that.