Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4697
  • Last Modified:

VMware VCenter problem - vsphere client cant connect

I Really need some help!
VMWare vSphere Client will not connect to Vcenter.
The service keeps quitting, so i start it up and i try to log in, then i get a connection error with (the server committed a protocol violation. section=response statusline) and the error stack is: Call "ServiceINstance.RetrieveContent" for object "serverInstance" on server "192.x.x.x"  failed.
I check on the service, and the service is stopped.
I check the event logs, and it just says that event id 1000 did not get a error code, and connection could be corrupted.
Here is what i have done so far:  reinstalled vcenter, run the vcenter manager service as an adimistrator, and i have tried to run vsxd.exe -s and it gives me a lot of errors and shuts down, the last errors about App could not find LicMgr with no revision store.
im at wits end. please help.
0
renet123
Asked:
renet123
  • 3
  • 2
  • 2
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Is the SQL database local or Remote?

Is the SQL database started?

The SQL Express database is not larger than 4GB?
0
 
renet123Author Commented:
Is the SQL database local or Remote? Local

Is the SQL database started?
Service: SQL Server (SQLEXP_VIM) = Started
Service: SQL Server Browser = Started
Service: SQL Server VSS Writer = Started

The SQL Express database is not larger than 4GB?
Not sure how to check this - but on the SQL Manager, i right clicked the only container...
Database Container: VIM_VCDB = Size 6.19MB
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Does the VMware vCenter Service Stop all the time?
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
PerimeterITCommented:
The SQL Express database is not larger than 4GB?
Not sure how to check this - but on the SQL Manager, i right clicked the only container...


Easiest way is to do a search on the hard drive for *.mdf files

Look for the VIM databases, if they are 4gb or close then the services won't function properly.

If this is the case there are ways to trim the database, remove logs etc but easiest thing to do is upgrade the SQL EXP to 2008 R2 it has a higher DB size limit. There are guides for this I can provide if required
0
 
renet123Author Commented:
Ok, thanks.
The VIM_VCDB file is 5.18mb

biggest mdf i have on the machine is a resource mdf that is 38mb ..

nothing even close to 4gb..
and before anyone asks.. i have 64gb free out of 97gb on the hard drive..
0
 
PerimeterITCommented:

I'm going to go out on a limb and say you're support contract is expired?



Well lets start with "protocol error"

Is there anything else on that box that could be nabbing port 80 or 443?

Easiest thing to do is surf its IP and see what comes up.


Anti-virus, windows firewall ?



Worst case if you've exhausted everything else you may need to do a reinstall of Vcenter, just for god sake BACK UP THE VIM DATABASES if you're going to do that.
0
 
renet123Author Commented:
there is another service that seems to be running on the same port.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now