When I run the IDS login script this morning, I get the following pop-up error message labeled
Windows Script Host:
Script: \\pc-ad-1\NetLogon\login.vbs
Line: 27
Char: 2
Error: No network provider accepted the given network path.
Code: 800704B3
Source: WSHNetwork.MapNetworkDrive
A window is then opened: Program Window on IDS-PC-1
But double-clicking on the PowerChurch icon does not access our church's data files -- it wants to start a new setup from scratch.
Is this a rather obtuse way of telling me that there are already two people logged on from the church? Or, is there some underlying problem here?
Thank you. -- John
IDS login failure
Moderators: Moderators, Tech Support
-
- Posts: 23
- Joined: Tue Jul 17, 2007 12:17 pm
- Location: Lake Country UU Church
- Contact:
IDS login failure
-- John Staudt
Log on failure
I am having the same problem and I am the only user. I sent an email to tech support.
Thanks,
Snapper Mack
Snapper Mack
-
- Program Development
- Posts: 834
- Joined: Tue Sep 02, 2003 12:48 pm
- Location: PowerChurch Software
- Contact:
We're really sorry about this. I just got off the phone with our colocation provider, and they informed me that their entire building lost power for about 10 minutes on Saturday. It's a long story, but the short version is, they were replacing the transformers that service the whole building, and the backup generator failed to start. They were running on battery backup while they got that fixed, but it took them about 10 minutes too long. They sent out emails announcing that this work was going to take place, but we were somehow not on their list to notify.
So, power is back up, and our server farm is running properly now.
We are on their notification list in triplicate.
We are implementing additional monitoring that, before this, would have seemed like overkill.
Again, we are very sorry about your downtime, and we're working to make sure something like this does not happen again.
So, power is back up, and our server farm is running properly now.
We are on their notification list in triplicate.
We are implementing additional monitoring that, before this, would have seemed like overkill.
Again, we are very sorry about your downtime, and we're working to make sure something like this does not happen again.