"Requested label could not be found"

[mygcc]

We are setting up PowerChurch Check In for the first time and seem to have everything in working order. The check in works fine, does everything we want it to do, except print. The Dymo printers work fine when not being used by PowerChurch, so we are sure it's not how the printers are set up. Yet the "label set" never shows up under the dymo printer in the set up screen at the kiosks. When we try to print, we get the following message: "The requested label could not be found: http://server:8727/dymolabels/default.lwl"

8727 is the port opened for sharing on the computer that houses the server and databank. I feel like we're missing something simple, but don't know what it is. Can someone help?

[Tracy]

This sounds like the server has a permissions issue finding the label. The user the service is started with may not have NTFS permissions to the folder where the labels reside.

If the permissions look right give us a call in Technical Support at (800) 486-1800

[mygcc]

What's the best way for me to check that the permissions are set correctly?

[NeilZ]

What's the best way for me to check that the permissions are set correctly?

What version of Windows does the 'server' computer use ??

[mygcc]

Windows XP

[mygcc]

I figured out how to check the NTFS permissions on Windows XP, and made sure all the files were set to be shared in the network for the kiosks. It still will not read the labels and gives the same message. Any other ideas?

[Tracy]

The kiosk does not need to access the server, except through the port in the firewall.
A network share is not required for a kiosk workstation to access the Check In server.

There is a service that runs the Check In server. By default, if the PowerChurch data is on the machine where the Check In server is installed. The SYSTEM user runs and is able to access the data without problems. If NTFS permissions have been changed for the directories, or a different user has been setup to allow accessing the data which resides on a different computer, you may have this trouble.

Another reason that it might happen is you have an out dated kiosk and server. When the Check In system was released, both the server and the kiosk needed to be updated individually. Kiosk installs after Oct 2010 should update direct from the single Server maintenance release.

[mygcc]

Thanks, Tracy, got the update and that helped. Also realized by your post that we had the wrong path--we had been using a path that would access the server from the kiosk computer, but your post helped us realize we were already accessing the server, so we just had to have a path to the right file. That fixed it for us. Thanks!