Network Description:
-Server running M$ NT v4.0 SP6 SERVER
-PC's running NT v4.0 SP6a Workstation, Win2k Pro and WinXP Pro
PCPlus85 directory resides on network drive I:\
All PCPlus users are domain admins (no, I didn't set it up this way. It was decided for me).
We have now added five new users to the domain (who are not domain admins) and to PowerChurch. The users can log into the network with no problem. When they attempt to run PowerChurch (from the network drive; yes it is mapped correctly), they get the subject error. This error has occured on both an NT v4.0 workstation and an XP Pro box.
Ideas? Solutions?
We are planning on moving to a new server by the end of the month. This new server will be running a real OS, namely FreeBSD. I'll share those experiences as they happen.
AdvanceThanks,
Jeff
"Cannot update cursor" message when accessing PC v
Moderators: Moderators, Tech Support
-
jeffkoke
- Posts: 298
- Joined: Sat Oct 11, 2003 9:43 am
- Location: Great Bridge Church of God, Chesapeake VA
- Contact:
"Cannot update cursor" message when accessing PC v
Jeff
--
Jeff Koke, KK4SN
Great Bridge Church of God
Chesapeake VA
"Every Father should remember that one day his
children will follow his example instead of his advice."
--
Jeff Koke, KK4SN
Great Bridge Church of God
Chesapeake VA
"Every Father should remember that one day his
children will follow his example instead of his advice."
-
Zeb
- Tech Support
- Posts: 116
- Joined: Tue Sep 02, 2003 12:43 pm
- Location: PowerChurch Software
- Contact:
In every instance we have found and tested in every version of PowerChurch, Can not update the cursor is caused by having a read-only file within the PowerChurch directory or permissions making the files seem as read-only.
If the program runs fine for some users and not for others, it would sound like its not a read-only file but more of a permissions problem.
Permissions in domains can get tricky and unfortunatly we are not network admins. You may need to call your network admin or the person(s) that set up the network.
For further assistance feel free to call our technical support office at (800)486-1800.
If the program runs fine for some users and not for others, it would sound like its not a read-only file but more of a permissions problem.
Permissions in domains can get tricky and unfortunatly we are not network admins. You may need to call your network admin or the person(s) that set up the network.
For further assistance feel free to call our technical support office at (800)486-1800.
I found this error when transitioning to version 10 from version 9.
We have PowerChurch Plus installed on a Windows 2003 Small Business Server.
I went to the PCPlus10 folder and applied Full Control NTFS permissions to the Data folder for the PowerChurchPlusUsers group I set up.
Now that I think of it, I had to do the same thing when I installed version 9.
We have PowerChurch Plus installed on a Windows 2003 Small Business Server.
I went to the PCPlus10 folder and applied Full Control NTFS permissions to the Data folder for the PowerChurchPlusUsers group I set up.
Now that I think of it, I had to do the same thing when I installed version 9.
John Michell
Unitarian Church of Calgary
Unitarian Church of Calgary
Yep ... my advice to anyone installing Powerchurch for the first time on a server:jmichell wrote:I found this error when transitioning to version 10 from version 9.
We have PowerChurch Plus installed on a Windows 2003 Small Business Server.
I went to the PCPlus10 folder and applied Full Control NTFS permissions to the Data folder for the PowerChurchPlusUsers group I set up.
Now that I think of it, I had to do the same thing when I installed version 9.
Share the directory with FULL access to everyone. Let Powerchurch take care of the permissions internally.
Neil Zampella
Using PC+ since 1999.
Using PC+ since 1999.