|
|
|
|
Joined: Feb 2007
Posts: 3
Member
|
OP
Member
Joined: Feb 2007
Posts: 3 |
While trying to do a database save the db studio hangs when saving the numberingplanpatterns. I don't get any errors that I know of. The application just sits there and looks like it is running for hours.
Does anyone have an idea on how to fix this without having to revert to a backup?
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
|
Joined: Nov 2001
Posts: 2,500
Member
|
|
Member
Joined: Nov 2001
Posts: 2,500 |
What system and version is your phone system? What OS do you run on your PC?
Rhett
|
|
|
|
|
Joined: Feb 2007
Posts: 3
Member
|
|
OP
Member
Joined: Feb 2007
Posts: 3 |
The system is an Axxess running 9.100. I tried on an xp and 2k machine. I can back up our other node just fine.
|
|
|
|
|
Joined: Nov 2001
Posts: 2,500
Member
|
|
Member
Joined: Nov 2001
Posts: 2,500 |
Your saying with the same PC and Session Manager software, you can back up one node but not the other?
How do you connect to the system. Modem, direct, IP?
Rhett
|
|
|
|
|
Joined: May 2004
Posts: 244
Member
|
|
Member
Joined: May 2004
Posts: 244 |
I had that happen to a customer and me when I went to site. Tech support said that the db you were tring to save is corrupted. The numberingplanpatterns portion of the database is what is corrupted. You well se this if you are in the online view mode while in db wih the equipment. This is the internal memory arrangement that the system uses for telling you what the next number is available and can use.
What you have to do is use the last good saved db and run it through the db tester. Shut down the db tester. Restart the db tester and test the db that you just test to be sure that it is good. If it come back bad, try an earlier db saved to get a good db test twice.
Bring up the saved db, while connected to the working system and stare and compare to see what changes have been made from the earlier and present db.
Save the local db that you were staring and comparing to the working db. Run the db tester again to be sure.
Upload the db into the system at some appropiate time.
Hope this helps,
Mike
|
|
|
|
Forums84
Topics94,284
Posts638,771
Members49,765
| |
Most Online5,661
May 23rd, 2018
|
|
|
1 members (Toner),
126
guests, and
369
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|
|
