Mitel Forums - The Unofficial Source
Mitel Forums => MiVoice Office 250/Mitel 5000 => Topic started by: bluewhite4 on February 27, 2014, 04:34:05 PM
-
Does anyone have or know a way to convert a 1.67 DB to be able to be loaded into 5000 System Diag?
The DB conversion tool states that it works for everything 2.2 or newer, so I'm hoping there's an older version to get it up to 2.2.
Thanks.
-
Bluewhite4,
Axxess version 1.67 used a DOS program so no there is not a simple way to upgrade it to a 5000. Personally I would hand key the whole database as there will be more issues with converting it anyway than just taking the time to hand key it from scratch. The bonus is you can get the customers input on how they want to do things when you do it this way.
Thanks,
TE
-
The customer is unwilling to assist. That's why I was hoping to find the conversion. Thanks for the information.
-
Agree with TE; Even if you could do it, I've converted several 2.x & 3.x systems that eventually revealed corruptions.
-
So was that an Axxess database or an Inter-Tel 5000? 5000 was never DOS, so conversion software in v. 3.2 will probably get it done for you.
-
It is an Axxess, that we're replacing with a 5000 HX.
Wasn't looking to upgrade so that I could load straight into the HX, more so I could refer back to data about current setup.
-
OK, I think I see where this is going... you have a 1.x version of Inter-tel 5000 (not Axxess) current and want to bring it current?
Can you reverify the version of the system from the front panel or inside system programmer? 1.67 doesn't hit me as a 5000 version (this might be a DB studio version, which is irrelevant)
-
The customer is unwilling to assist.
It's sad when a customer is willing to do that to themselves.
Ralph
-
Bluewhite4,
I think I may have the old DOS program for version 1.0 databases, but I will have to look in my old 3.5 floppies to find it. Do you have a way to get in to the system to download the DB?
I think I only saw like two of those old cabinets working in all the years I have worked on the Axxess system. I am also surprised that the customer doesn't want to assist in the upgrade to the new platform, but considering they have a system that is probably 20 years old it shouldn't surprise me that much.
Thanks,
TE
-
Bluewhite4,
I believe I got this figured out for you, but I need you to either post the database or tell us the real version you are working with.
After going back through a lot of disks I found that there is no Axxess version 1.67, but there is the DB Studio Version of 1.67. Now this version of DB Studio is used for several versions of Axxess software, but you need to either post the database version which will be above it on the help about.
Just so you can get there better, open up the database in DB studio and then go to help and then about inter-tel database programming and look in the middle where it says program version.
Thanks,
TE
-
I'd love to see a working Access v1 system, with that big olde style power supply.
-
Bluewhite4,
I believe I got this figured out for you, but I need you to either post the database or tell us the real version you are working with.
After going back through a lot of disks I found that there is no Axxess version 1.67, but there is the DB Studio Version of 1.67. Now this version of DB Studio is used for several versions of Axxess software, but you need to either post the database version which will be above it on the help about.
Just so you can get there better, open up the database in DB studio and then go to help and then about inter-tel database programming and look in the middle where it says program version.
Thanks,
TE
I will try to get access to the system again and get the information your requesting.
-
I've got the following:
Program Version 11.010
System Version 11.014d
-
Bluewhite4,
11.0 software is the last major version of Axxess Software and as such can be converted directly to version 2.3 of the 5000 and then upgrade it by the major versions from there.
Axxess 11.014d -> 5000 2.3 -> 5000 3.0 -> 5000 4.0 -> 5000 5.0 -> 5000 6.0
Now you could upgrade it to 1.x then 2.x and so on, but Version 11.0 came out the same time 2.2 did I believe and I know that 11.015 was out at the same time 3.2 came out, but I do not think the Axxess added anything new that wasn't already in 2.4 of the 5000. The good thing is that you are pretty much as far as you can go on the Axxess software versions so that is a good thing. I still wouldn't take that database and put it in a system as I find things get "lost" along the way sometimes, but you can convert it and be pretty sure the majority of it will remain intact.
If all you are wanting to do is just refer to it though you should be able to do that in Session Manager 11.0 as the majority of the programming is pretty much the same as for the 5000. If you put your 5000 interface in classic mode then it would look almost exactly the same.
Thanks,
TE
-
Thanks Tech,
I just realized that I hadn't loaded all the DB Plugins for my new laptop. Once I did that I was able to convert the DB up to 4.0.
However, it won't let me update it past that, and when I try to open that 4.0 db, it tells me that it can't open a db created by the previous version of this application.
Is it because I'm running x64?
-
I was able to open the 4.X database on a 32-bit windows client, but the conversion to either 5.x or 6.x database fails with a .Net error.
Anyone seen this before?
-
Bluewhite4,
I think I should have mentioned one thing about the upgrade process. After each upgrade you need to run the DBTest utility on it to fix an issues that are fixable at that point. Also keep an eye out for Referential Integrity errors since that is a major source of DB corruption.
As for the issue with whether or not your machine is 64 bit that shouldn't make a difference, but then again I never ran the software on a 64 bit machine yet. The .NET issue I ran into before when I loaded software versions and then had to delete them to load previous versions, but that hasn't happened since they started unbundling the DB software from the SAaD software. It could mean that your version of .NET is not the correct one, try reloading the latest version of the SAaD application to see if it repairs it.
Thanks,
TE
-
There should be no reason to do incremental back-ups from Axxess version 11.
I recently converted an Axxess version 10 directly to HX-5000 version 6, then loaded it with only minor clean up. No errors or issues popped up.
-
DND ON,
I have heard the same thing from other technicians, but I personally have had no luck with doing that so I stick with what I know works. Of course it is our policy to rekey databases instead of converting at this point, but you never know when that will change.
Thanks,
TE
-
I've done two conversions and have two more to go. Rekeying systems on a 50+ node network isn't my idea of a good time!
-
DND ON,
It is not my idea of a good time either, but it does allow me to clean up an old database as well as understand how the customer is using their system so I can offer ideas on improving their call flows or processes. Also since there are new features in the 5000 that did not exist in some Axxess versions it would be a good idea to move over to those features instead of reusing work arounds. Then there is all the hidden flags and features through Online Monitor that do not always translate properly that can cause service issues later on.
Of course there is the counter that someone just converting a database will complete the job faster than someone rekeying it, but that is more of a vendor bottom line argument that assumes that any issues that arise will be minimal and easy to fix and fail into a different "service" budget versus the installation budget.
Thanks,
TE