tugi's Posts

i solved the problem. Unfortunately, problem is local regional settings. When i change from Turkish to English, it works well. Thx for everyting, espacially RAMESA.
I've already checked this article.
under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware VirtualCenter\DB VCENTER vpxuser which kb article?
In the install wizard username is vpxuser and i enter just password at the dsn screen. Yes 32 bit and 64bit dsn is set by vpxuser What is the location of db username at registry? ... See more...
In the install wizard username is vpxuser and i enter just password at the dsn screen. Yes 32 bit and 64bit dsn is set by vpxuser What is the location of db username at registry? I ran the command you sent me "VCDatabaseUpgrade.exe DSN=vcenter UID=vpxuser PWD=****** QUIET=true"
You are right, the user name is blank. The same thing when looking at the database log. Why the user name is blank? I ran the command and same error.Log as follows. ... See more...
You are right, the user name is blank. The same thing when looking at the database log. Why the user name is blank? I ran the command and same error.Log as follows. Info: Beginning upgrade process.... Info: vcenter has been detected as a SQL server. Error: ERROR [SQL Native Client][SQL Server]Login failed for user ''. The user is not associated with a trusted SQL Server connection. ERROR [SQL Native Client][SQL Server]Login failed for user ''. The user is not associated with a trusted SQL Server connection. Initialize failed, exiting...
I tried but doesn't work. same error.
I have just 64 bit dsn. you can find all log files as attached. thx.
Hi, I have an error when i try to upgrade vcenter from 4.0 to 4.1. After run Setup, Upgrade databease step is getting this error. "Error occurred while connecting to the Data Source". ... See more...
Hi, I have an error when i try to upgrade vcenter from 4.0 to 4.1. After run Setup, Upgrade databease step is getting this error. "Error occurred while connecting to the Data Source". vcenter and sql is the same machine. Sql version is Std. 2005 Sp3 vpxuser is a sysadmin windows version is 2008 Std64 bit vminst.log VMware VirtualCenter-build-258902: 07/19/10 10:54:00 --- CA exec: VMLaunchDbUpgradeWizard VMware VirtualCenter-build-258902: 07/19/10 10:54:00 Getting Property SourceDir = C:\sources\VMware-VIMSetup-all-4.1.0-259021\vpx\ VMware VirtualCenter-build-258902: 07/19/10 10:54:00 Getting Property TempFolder = C:\Users\ADMINI~1\AppData\Local\Temp\1\ VMware VirtualCenter-build-258902: 07/19/10 10:54:00 Getting Property DB_DSN = VCENTER VMware VirtualCenter-build-258902: 07/19/10 10:54:00 Getting Property DB_EXISTING_VERSION = 400 VMware VirtualCenter-build-258902: 07/19/10 10:54:00 Getting Property DB_USERNAME = vpxuser VMware VirtualCenter-build-258902: 07/19/10 10:54:00 Found "C:\sources\VMware-VIMSetup-all-4.1.0-259021\vpx\dbupgrade\bin\VCDatabaseUpgrade.exe" VMware VirtualCenter-build-258902: 07/19/10 10:54:01 Process returned 6 VMware VirtualCenter-build-258902: 07/19/10 10:54:01 Error occurred while connecting to the Data Source. VMware VirtualCenter-build-258902: 07/19/10 10:54:01 Getting Property UILevel = 5 VMware VirtualCenter-build-258902: 07/19/10 10:54:01 Getting Property ProductName = VMware vCenter Server VMware VirtualCenter-build-258902: 07/19/10 10:54:02 End Logging VMware VirtualCenter-build-258902: 07/19/10 10:54:03 Begin Logging VMware VirtualCenter-build-258902: 07/19/10 10:54:03 --- CA exec: VMCleanupRegistry VMware VirtualCenter-build-258902: 07/19/10 10:54:03 Getting Property TEMPLATE = x64 VMware VirtualCenter-build-258902: 07/19/10 10:54:03 Warning: Deleting a key that isn't empty: "HKEY_CURRENT_USER\VMW" VMware VirtualCenter-build-258902: 07/19/10 10:54:03 Warning: Deleting a key that isn't empty: "\InstRTPaths" VMware VirtualCenter-build-258902: 07/19/10 10:54:03 End Logging
You can find the procedure that your need. Remove Damaged Restore Points Corrupt restore points, which are identified during integrity checks, should be removed. Restore points may... See more...
You can find the procedure that your need. Remove Damaged Restore Points Corrupt restore points, which are identified during integrity checks, should be removed. Restore points may be identified as damaged during transient connection failures. If transient connection failures are possible, check if damaged restore point issues are resolved after connections are restored. Prerequisites Before you can remove damaged restore points, you must have restore points in a functioning Data Recovery deployment. Procedure 1 In the vSphere Client, select Home > Solutions and Applications > VMware Data Recovery. 2 Click the Reports tab and double-click the integrity check that failed. The Operations Log for the event opens in a separate window. Note which restore points triggered the failure. 3 Close the Operations Log and click the Restore tab. 4 From the Filter dropdown list, select Damaged Restore Points. Available restore points are filtered to display only the virtual machines with damaged restore points. It may be necessary to expand a virtual machine's node to display the damaged restore point. 5 Select damaged restore points for removal and click Mark for Delete. 6 Initiate an integrity check. Completing an integrity check causes all restore points marked for deletion to be removed. 7 Review the results of the integrity check to ensure no damaged restore points remain. Turgay.
what was the network issue? can you explain. cause I have same problem. thx.