Jellas's Posts

Hi Team, Please help me here as I'm getting below error. Connect-VIServer : 16/02/2015 15:50:25    Connect-VIServer        Cannot complete login due to an incorrect user name or password. At C:\Users\Test\Desktop\test.ps1:1 char:17 + Connect-VIServer <<<<  esx1.local  -User root -Password mypassword    + CategoryInfo : NotSpecified: (:) [Connect-VIServer], InvalidLog    in     + FullyQualifiedErrorId : Client20_ConnectivityServiceImpl_Reconnect_Exception,VMware.VimAutomation.ViCore.Cmdlets.Commands.ConnectVIServer What I have tried: Login to the Jump box and copy pasted the script and saved as test.ps1 on the desktop. Now opened the vmwarepowercli as runasadministrator. now drag and droped the test.ps1 file from desktop hit the enter.got above mnentioned error. Please help me how to get ride of this error. Environemnet details: Vmwarevpsherepowercli 5.1 ESXi host 4.1 and also tried on 5.x Thanks Sravana

Many of us still evaluating the vSphere and vCenter in our test environments. Sometimes, it takes more than 60 days to evaluate where trial edition expires. We can't extend the trial edition in ESX host, either we have to reinstall it or license it. vCenter also have to follow the same way as ESX does. But, here we can keep old database contents as it is when you reinstall the vCenter software. This document using vCenter 4.0 and SQLEXPRESS 2005 (built in) database. At the time of installation of vCenter 4.0, it installs SQLEXPRESS 2005 by default unless any other Database specified. Mostly, we are using built-in database is SQLEXPRESS 2005 for testing environment. When you install vCenter 4.0, it installs SQLEXPRESS 2005 and creates a database called "SQLEXP_VIM". You can view this thru SQL Server Configuration Manager console. Start --> All Programs --> Microsoft SQL Server 2005 --->Configuration Tools ----> SQL Server Configuration Manager Creating DSN ================= Create a System DSN for this database using ODBC (Administrative Tools à Data Sources (ODBC) either before/after expiry of your vCenter trial period. Open the ODBC Database Administrator Source, Select "System DSN" and Click "Add" Button and Select "SQL Native Client" Provide the Datasource name (recommened to use as "SQLEXP_VIM") Select, the server and database name (mostly local host, since it is installed on the same server where we installed vCenter earlier) Leave the Authentication as default. It is important to change the default database to VIM_VCDB as shown in the picture: (Select in the list) Press Next and leave them to default settings and Test Connectivity. Use the Add/Remove Programs to uninstall the vCenter 5.0 after trail period is over. Reinstalling the vCenter When you reinstall the vCenter on same server, select the "Use an existing supported database" on database section. Then, enter "sqlexp_vim" as the DSN and press "Next" and leave blank for UN/PW Select "Do not overwrite, leave my existing database in place" and press "Next", leave it default    After complete database selection, continue with your installation as usual. Once the vCenter installation completed, open it thru vSphere Client, you can see your old settings such as Datacenter, Cluster and other configuration. Again, your evalution periods starts with 60-days again. Note : This is for Vcenter 4.X ..it should work with 5.x as well however I have not tested it....I'm not responsible if some thing goes worng.

Please try these things... To troubleshoot the VMware VirtualCenter Server service when it does not start or fails: Note: If you perform a corrective action in any of the following steps, attempt to restart the VMware VirtualCenter Server service. Verify that the VMware VirtualCenter Server service cannot be restarted. Open the Microsoft Services control panel and check the status of the service. For more information on starting the VirtualCenter service if it has stopped, see Stopping, starting, or restarting vCenter services (1003895). Verify that the configuration of the ODBC Data Source (DSN) used for connection to the database for vCenter Server is correct. For more information, see vCenter Server installation fails with ODBC and DSN errors (1003928). Note: For version 2.5.x, ensure that you are using SQL authentication if you are using a Microsoft SQL server. Windows Authentication is not supported. For version 4.x and above Windows Authentication is supported. Verify that ports 902, 80, and 443 are not being used by any other application. If another application, such as Microsoft Internet Information Server (IIS) (also known as Web Server (IIS) on Windows 2008 Enterprise) or Routing and Remote Access Service (RAS) or the World Wide Web Publishing Services (W3SVC) or Windows Remote Management service (WS-Management) or the Citrix Licensing Support service is utilizing any of the ports, vCenter Server cannot start. For more information, see Port already in use when installing vCenter Server (4824652). If you see an error similar to one of the following when reviewing the logs, another application may be using the ports: Failed to create http proxy: Resource is already in use: Listen socket: :<port> Failed to create http proxy: An attempt was made to access a socket in a way forbidden by its access permissions. proxy failed on port <port>: Only one usage of each socket address (protocol/network address/port) is normally permitted. For more information on checking ports, see Determining if a port is in use (1003971). Verify the health of the database server that is being used for vCenter Server. If the hard drives are out of space, the database transaction logs are full, or if the database is heavily fragmented, vCenter Server may not start. For more information, see Investigating the health of a vCenter Server database (1003979). Verify the VMware VirtualCenter Service is running with the proper credentials. For more information, see After installing vCenter Server, the VMware VirtualCenter Server service fails to start (1004280). Verify that critical folders exist on the vCenter Server host. For more information, see Missing folders on a vCenter Server prevent VirtualCenter Server service from starting (1005882). Verify that no hardware or software changes have been made to the vCenter server that may have caused the failure. If you have recently made any changes to the vCenter server, undo these changes temporarily for testing purposes. Before launching vCenter Server, ensure that the VMwareVCMSDS service is running VMware Link :  http://kb.vmware.com/selfservice/documentLinkInt.do?micrositeID=&popup=true&languageId=&externalID=1003926

Hi .. Even i'm facing the same issue. Please help me..i 'm getting the below error when i tried to login to the vcenter server . "Cannot complete login due to an incorrect user name or password" when i tried to telnet the port (902) was not sucessful..