cancel
Showing results for 
Search instead for 
Did you mean: 

Services not started after moving the standalone server to a virtual environment

Former Member
0 Kudos

Business Objects 4.1 SP 4
Windows Server 2012 R2
After moving the standalone server to a virtual environment
services not started
SIA is running, but i cant login to SIA using administrator account
WIA not running and i can't login to CMC

In netstat command i see 6400 port nut with mac address
maybe BO using mac address anywhere.

Joe_Peters
Active Contributor
0 Kudos

What is a "port nut"? BO should not be using the mac address anywhere. And I can confirm that P2V is possible in Bi4.1, even getting a different IP address in the process. If the SIA is not running, that's where you should start looking. Check the server's Event Logs, and the logging directory for SIA* files.

Former Member
0 Kudos

port nut
*port, but
*In netstat command i see 6400 port, but with mac address

in log files nothing yet
in Event Logs nothing yet

Joe_Peters
Active Contributor
0 Kudos

Sorry, I missed that SIA was running. How about the CMS?

And I don't think you're seeing MAC addresses in your netstat output -- those are probably IPv6 addresses.

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member185603
Active Contributor

Was it before Physical server and moved to VM? Is the server name same when you moved to VM? or different?

What do you mean stand alone server moving to VM? Can you give more details?

Former Member
0 Kudos

Yes from Physical server to VM
using "vcenter standalone converter" we convert to VM

Server name same

former_member185603
Active Contributor
0 Kudos

And also can you check the errors in event viewer and let us know exact errors are

denis_konovalov
Active Contributor
0 Kudos

As mentioned before by Jawahar - the method by which you have moved your server is very important to understand why it is not working.

In general terms, you can do following : stop all services (make sure nothing is running by looking at task manager and killing all processes that should be stopped), re-create SIA. Start SIA after re-creation.