VMware client fails to connect and webclient show IIS7 page

I am attempting to connect to my VMWARE VCENTER with a C sharp client and I get cant connect via c sharp client I also cannot browse to the URL for this VCENTER , I get  the IIS7 landing page


I do see some services that are set to automatic and not started , what is the next step to troubleshoot
no started

thanks!!!!
LVL 1
NAMEWITHELD12Asked:
Who is Participating?
 
ITSysTechSenior Systems AdministratorCommented:
From your error log it says your "Server is configured for Windows authentication only" so you need to log in using Server Management Studio and switch the sa account to "SQL server and Windows authentication mode" see below.

1. Connect to SQL via SQL Server Management Studio.

2. Right click on the server name on object explorer -> Properties -> Security -> Change Server authentication to “SQL server and Windows authentication mode” -> click OK.

1.JPG
0
 
SeanSystem EngineerCommented:
Start the services. The management service is what you need running to be able to connect to vcenter.
0
 
ITSysTechSenior Systems AdministratorCommented:
If all your services are correctly configured, a reboot of the vCenter should start all the services for you. It does take time for the web interface to come up.
0
Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Do you have the web client installed ? I don't see it in your screenshot ?

Is the Web Client started ?

Are you going to the correct URL ?

IIS7 landing page is suspicious ?
0
 
NAMEWITHELD12Author Commented:
hi !!!

yeah the web client is installed, I was able to get to this before ,  via the webclient , but when I goto the IP address of the server ( see screen shot) I get the IIS landing page . If I goto my other VMWARE VCENTER I get the normal vmare landing page



Do you have the web client installed ? I don't see it in your screenshot ? , yes I can get to my other VMware environment no problem ,
Is the Web Client started ? yes see screen shot the webclient service is running on the Vcenter server

Are you going to the correct URL ? yes see the screen shot , I have also tried 127.0.0.1 as well

IIS7 landing page is suspicious ? yes I should be seeing the landing page for VMWARE

thanks
0
 
NAMEWITHELD12Author Commented:
I have rebooted many times this is the current state of the VMWARE services , I am assuming that the vmware virtual center mananagment webservices is the service  that I need to start
0
 
NAMEWITHELD12Author Commented:
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
vCenter Server service is not started, which will start the dependancy.
0
 
NAMEWITHELD12Author Commented:
ok when attempting to start it   I get this error

The VMware VirtualCenter Server service terminated with service-specific error The system cannot find the file specified.. in the system event log
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
time to start debugging vCenter Server....

SQL database is it available, if used, is it remote....
0
 
NAMEWITHELD12Author Commented:
seems like this is not the first time this has happened, i see it happen 1.5 years ago . what other logs can I look at to get an idea on what is going on ?
Capture-cant-find-the-file-specified.JPG
0
 
NAMEWITHELD12Author Commented:
yes it is local and is the express version , there is no issue with drive space BTW
0
 
NAMEWITHELD12Author Commented:
from the SQL error log ERRORLOG

2017-09-22 15:16:24.43 Server      Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
      Jun 17 2011 00:54:03
      Copyright (c) Microsoft Corporation
      Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)

2017-09-22 15:16:24.46 Server      (c) Microsoft Corporation.
2017-09-22 15:16:24.46 Server      All rights reserved.
2017-09-22 15:16:24.46 Server      Server process ID is 1332.
2017-09-22 15:16:24.46 Server      System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
2017-09-22 15:16:24.46 Server      Authentication mode is WINDOWS-ONLY.
2017-09-22 15:16:24.46 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.VIM_SQLEXP\MSSQL\Log\ERRORLOG'.
2017-09-22 15:16:24.48 Server      This instance of SQL Server last reported using a process ID of 1336 at 9/22/2017 3:14:45 PM (local) 9/22/2017 7:14:45 PM (UTC). This is an informational message only; no user action is required.
2017-09-22 15:16:24.48 Server      Registry startup parameters:
       -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.VIM_SQLEXP\MSSQL\DATA\master.mdf
       -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.VIM_SQLEXP\MSSQL\Log\ERRORLOG
       -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.VIM_SQLEXP\MSSQL\DATA\mastlog.ldf
2017-09-22 15:16:24.51 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2017-09-22 15:16:24.51 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2017-09-22 15:16:24.87 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2017-09-22 15:16:25.31 Server      Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2017-09-22 15:16:25.57 spid7s      Starting up database 'master'.
2017-09-22 15:16:25.66 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2017-09-22 15:16:25.91 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'VIM_SQLEXP'.
2017-09-22 15:16:26.18 spid7s      SQL Trace ID 1 was started by login "sa".
2017-09-22 15:16:26.19 spid7s      Starting up database 'mssqlsystemresource'.
2017-09-22 15:16:26.21 spid7s      The resource database build version is 10.50.2500. This is an informational message only. No user action is required.
2017-09-22 15:16:26.54 spid7s      Server name is 'VCTR02\VIM_SQLEXP'. This is an informational message only. No user action is required.
2017-09-22 15:16:26.54 spid10s     Starting up database 'model'.
2017-09-22 15:16:26.55 spid7s      Informational: No full-text supported languages found.
2017-09-22 15:16:26.57 spid7s      Starting up database 'msdb'.
2017-09-22 15:16:26.69 spid10s     Clearing tempdb database.
2017-09-22 15:16:26.88 spid10s     Starting up database 'tempdb'.
2017-09-22 15:16:26.90 Server      A self-generated certificate was successfully loaded for encryption.
2017-09-22 15:16:26.91 Server      Server is listening on [ 'any' <ipv6> 50667].
2017-09-22 15:16:26.91 Server      Server is listening on [ 'any' <ipv4> 50667].
2017-09-22 15:16:26.91 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\VIM_SQLEXP ].
2017-09-22 15:16:26.91 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$VIM_SQLEXP\sql\query ].
2017-09-22 15:16:26.93 Server      Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2017-09-22 15:16:26.94 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2017-09-22 15:16:26.94 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
2017-09-22 15:16:27.00 spid13s     The Service Broker protocol transport is disabled or not configured.
2017-09-22 15:16:27.02 spid13s     The Database Mirroring protocol transport is disabled or not configured.
2017-09-22 15:16:27.10 spid13s     Service Broker manager has started.
2017-09-22 15:16:27.11 spid7s      Recovery is complete. This is an informational message only. No user action is required.
2017-09-22 15:16:40.16 spid51      Starting up database 'VIM_UMDB'.
2017-09-22 15:16:41.78 spid51      Recovery is writing a checkpoint in database 'VIM_UMDB' (6). This is an informational message only. No user action is required.
2017-09-22 15:16:43.58 spid71      Starting up database 'VIM_VCDB'.
2017-09-23 19:49:37.79 Logon       Error: 18456, Severity: 14, State: 58.
2017-09-23 19:49:37.79 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-09-24 19:49:40.44 Logon       Error: 18456, Severity: 14, State: 58.
2017-09-24 19:49:40.44 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-09-25 19:48:14.41 Logon       Error: 18456, Severity: 14, State: 58.
2017-09-25 19:48:14.41 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-09-26 18:43:49.23 Logon       Error: 18456, Severity: 14, State: 58.
2017-09-26 18:43:49.23 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-09-27 18:42:02.63 Logon       Error: 18456, Severity: 14, State: 58.
2017-09-27 18:42:02.63 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-09-28 18:42:45.99 Logon       Error: 18456, Severity: 14, State: 58.
2017-09-28 18:42:45.99 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-09-29 18:43:02.78 Logon       Error: 18456, Severity: 14, State: 58.
2017-09-29 18:43:02.78 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-09-30 18:42:32.50 Logon       Error: 18456, Severity: 14, State: 58.
2017-09-30 18:42:32.50 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-10-01 18:42:16.70 Logon       Error: 18456, Severity: 14, State: 58.
2017-10-01 18:42:16.70 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-10-02 18:42:04.69 Logon       Error: 18456, Severity: 14, State: 58.
2017-10-02 18:42:04.69 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-10-04 18:43:31.49 Logon       Error: 18456, Severity: 14, State: 58.
2017-10-04 18:43:31.49 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-10-05 18:43:59.81 Logon       Error: 18456, Severity: 14, State: 58.
2017-10-05 18:43:59.81 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-10-06 18:44:39.98 Logon       Error: 18456, Severity: 14, State: 58.
2017-10-06 18:44:39.98 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-10-07 18:43:07.93 Logon       Error: 18456, Severity: 14, State: 58.
2017-10-07 18:43:07.93 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-10-08 18:43:16.00 Logon       Error: 18456, Severity: 14, State: 58.
2017-10-08 18:43:16.00 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-10-09 18:42:05.57 Logon       Error: 18456, Severity: 14, State: 58.
2017-10-09 18:42:05.57 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-10-10 18:45:48.66 Logon       Error: 18456, Severity: 14, State: 58.
2017-10-10 18:45:48.66 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-10-11 18:43:58.80 Logon       Error: 18456, Severity: 14, State: 58.
2017-10-11 18:43:58.80 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-10-12 18:47:09.47 Logon       Error: 18456, Severity: 14, State: 58.
2017-10-12 18:47:09.47 Logon       Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.56.2]
2017-10-13 13:53:51.70 Server      SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
2017-10-13 13:54:01.99 spid13s     Service Broker manager has shut down.
2017-10-13 13:54:02.20 spid13s     Error: 17054, Severity: 16, State: 1.
2017-10-13 13:54:02.20 spid13s     The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.
2017-10-13 13:54:04.23 spid7s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
0
 
NAMEWITHELD12Author Commented:
I can connect with a test
Capture-I-can-connect-.JPG
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Your SQL Express database is not exceeded 10GB
0
 
NAMEWITHELD12Author Commented:
will update soon
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.