Shoretel database migration steps

[w131jrd]

I are rebuilding our director server from scratch on new hardware because we are going from an enterprise license to a standard license of Windows Server 2003. Since we are making such a drastic change at the OS level I need to recreate the application on the new server and then migrate the database, call records and other data but I am having some issues with getting the data to be accepted by the new Application installation. I have looked on Shoretel's Website but I can not find any data migration documentation. We are using version 7.0 and are not switching versions between the installations.

[Telman2010]

I know you said you aren't swapping versions, but are using the exact same build?

[Jlorenz]

I are rebuilding our director server from scratch on new hardware because we are going from an enterprise license to a standard license of Windows Server 2003. Since we are making such a drastic change at the OS level I need to recreate the application on the new server and then migrate the database, call records and other data but I am having some issues with getting the data to be accepted by the new Application installation. I have looked on Shoretel's Website but I can not find any data migration documentation. We are using version 7.0 and are not switching versions between the installations.

Step 1
Build the New Windows 2003 Server (DO NOT PUT IN DOMAIN UNTIL AFTER ST IS INSTALLED)
Make sure you are using the same IP and Same Name of old server (Very Important here

Step 2
Shutdown Old Server

Step 3 (Important)
Move your Shoreline Data folder and all sub-folders form old server to new server

Step 3 (More Important)
Find and delete the MYsql folder form the Shoreline Data CDR records folder (NOTHING ELSE)

Step 4
Install the Same version of ST7 (Or Higher) on your new Server

Your done

*Disclaimer
Shoretel has a written proceedure in the KB articles I wrote, if your Partner supported or Enterprose you can get this from them.

I will be out of the office a few hours this morning, I will write up somethign more conclusive then above and post when I get back.

[w131jrd]

A couple questions:

You say in steps 2 and 3 to shutdown the old server. Is it ok to get the Shoreline data folder from the orginal server by going into safe mode on the original server and making a copy of it from there. Do you think it is OK to get the original data this way?

When doing step 3 are we putting the production version (version that was on the original server) of the database on the new server before installation?

[Jlorenz]

A couple questions:

You say in steps 2 and 3 to shutdown the old server. Is it ok to get the Shoreline data folder from the orginal server by going into safe mode on the original server and making a copy of it from there. Do you think it is OK to get the original data this way?

When doing step 3 are we putting the production version (version that was on the original server) of the database on the new server before installation?

The best way to copy the old data base is as follows

This is an addition of or expansin of 2 & 3

2a:
Shutdown old server, by Windows Services (Shutdown all Services starting with Shoreware Notification Server, then shut down all other ShoreTel Services

3a:
-1 Got to x:\Shoreline Data (where x is your install drive)
-2 Right mouse click on x:\Shoreline Data
-3 Choose Copy
-4 Right mouse click on x:\Shoreline Data
-5 Choose Paste

this will create a new folder called Copy of ShoreTel Data in the same location
That is your clean safe Folder to copy and safe gaurd

[w131jrd]

our problem is not with the migration process I how now realized. I believe it has to do with the service "ShoreWare Director Utilities". This service will not start and but when you go in and try to start it it responds with the error message below:

"Could not start the ShoreWare Director Utilities Service on Local Computer.
Error 0x80004005: Unspecified Error"

When I try to login to the Shoreware web interface with the default username/password (admin/changeme) I get the next message below. I believe this error has to do with the "ShoreWare Director Utilities" Service not running.


"CreateObject(KadotaUtil.System) Error: Permission denied"




When I built the server I used these configurations below:

1.) Microsoft Server 2003 Standard Edition 32-bit
2.) Installed Microsoft Server 2003 Standard Edition 32-bit R2
3.) Installed Must up-to-date Network Drivers from HP.com
4.) Set the static IP Address for adapter that we will be using
5.) Installed the following components (The bolded items are the ones that were checked):

-Application Server
--Application Server Console
--Enable network COM+ access
--IIS
---Common Files
---FTP Service
---IIS Manager
---SMTP Service
---WWW Service
----Active Server Pages
----World Wide Web Service

-Management and Monitoring Tools
--Simple Network Management Protocol


6.) Installed Shoretel Director Server build 12.5.9303.0

[Jlorenz]

our problem is not with the migration process I how now realized. I believe it has to do with the service "ShoreWare Director Utilities". This service will not start and but when you go in and try to start it it responds with the error message below:

"Could not start the ShoreWare Director Utilities Service on Local Computer.
Error 0x80004005: Unspecified Error"

When I try to login to the Shoreware web interface with the default username/password (admin/changeme) I get the next message below. I believe this error has to do with the "ShoreWare Director Utilities" Service not running.


"CreateObject(KadotaUtil.System) Error: Permission denied"




When I built the server I used these configurations below:

1.) Microsoft Server 2003 Standard Edition 32-bit
2.) Installed Microsoft Server 2003 Standard Edition 32-bit R2
3.) Installed Must up-to-date Network Drivers from HP.com
4.) Set the static IP Address for adapter that we will be using
5.) Installed the following components (The bolded items are the ones that were checked):

-Application Server
--Application Server Console
--Enable network COM+ access
--IIS
---Common Files
---FTP Service
---IIS Manager
---SMTP Service
---WWW Service
----Active Server Pages
----World Wide Web Service

-Management and Monitoring Tools
--Simple Network Management Protocol


6.) Installed Shoretel Director Server build 12.5.9303.0

New Server Questions
Did the IP address of the Server Change?
Was the Server on a domain Before you installed the ShoreTel Software?

"CreateObject(KadotaUtil.System) Error: Permission denied"

this is a launch permissions issue, and can be caused by the two questions above
WARNING -- Do not do anythign below until you answer the above questions
To fix

open Component Services, Drill down on My Computor
you will see two Hives or two listings DCOM
Drop the 2nd One down
Search and right mouse click on the Kadota Utility
Go to Properties
Go to Com Security tab
Choose Launch permissions
Make sure each user listed has all 4 options checked

DO NOT USE THE KB ARTICLE ON LINE IT IS OUT DATED

Call TAC for further support or your Partner, I could fix this in 5 min, But I have to run........

[w131jrd]

The Server was never on the domain or even plugged into any network at all. When I installed the OS the server did not load any drivers for the network device. When I got the driver from the HP website I put installed it and then right away I set the IP address to static from DHCP. This server has never got an actual IP Address because we have never plugged a network cable into the server since it was built.

Since I felt that I met the above requirements I tried you next steps. These also failed but did change the error message a little. I also looked at our current production director server to see if these component services were changed on it and there were not.

[Forum]

The network card must be active to install Shoretel correctly. Even if you plug a laptop with a cat5 to it, as long as she show's connected.

Since you didn't do that, you need to load MS Access and and edit the DB table with the correct IP address, and then reboot. Make sure the NIC is active when rebooting (plugged in, etc).

Charles

[Jlorenz]

The Server was never on the domain or even plugged into any network at all. When I installed the OS the server did not load any drivers for the network device. When I got the driver from the HP website I put installed it and then right away I set the IP address to static from DHCP. This server has never got an actual IP Address because we have never plugged a network cable into the server since it was built.

Since I felt that I met the above requirements I tried you next steps. These also failed but did change the error message a little. I also looked at our current production director server to see if these component services were changed on it and there were not.

More then likely the IP address for the Shretel Directoyr / Application does not match the Server IP

Do you have MS Access installed on the Server?

or
can you netmap the Shoreline Data folder to a PC that has MS Access?

I can PM you the info to change in the tables real time with access. Or you need to shut the entire system down and then change the DB.

Dang Charles beat me to it PM set as to the correct tables to edit

[w131jrd]

This last Idea Worked. I started from scratch and built the OS up with the correct server name, Set the IP Address static to the one we will be using in production, and put a network cable between the server and a laptop that was also off any network so it did not interfere with our current environment. When I installed the Shoreware Director Server it worked with no problem.