(solved) - Failed to load the sqljdbc_auth.dll cause : no sqljdbc_auth in java.library.path

Failed to load the sqljdbc_auth.dll cause : no sqljdbc_auth in java.library.path

The reason behind the issue:

The vcdb.properties file does not get automatically updated, when we change from Windows Authentication to SQL authentication. Since migration assistant uses that vcdb.properties file to obtain the database configuration, it fails to connect because it is expecting integrated authentication instead of SQL authentication.

Resolution:

To resolve this issue modify vcdb.properties file. This file can be located in Windows vCenter Server at C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx\vcdb.properties and in VCSA at /etc/vmware-vpx/vcdb.properties.
Now modify the vcdb.properties files as mentioned below

from:

driver = com.microsoft.sqlserver.jdbc.SQLServerDriver
dbtype = mssql
url = jdbc:sqlserver://;serverName=Server_Name;DatabaseName=Database_Name;instanceName=Instance_Name;integratedSecurity=True

to

Retry the migration.

Comments

Error [403] The maximum number of sessions has been exceeded in the H5 client during login or logout

Symptoms In virgo log, you see messages similar to: [2020-05-19T07:25:45.285Z] [ERROR] http-nio-5090-exec-130 72026859 142953 501051 com.vmware.vise.security.spring.DefaultAuthenticationProvider logout failed for sessionId 142953, clientId 501051 java.lang.IllegalStateException: The specified cardinality of 1..1 for osgi:reference implementing com.vmware.vcenter.apigw.api.ApiGatewaySessionManager in bundle com.vmware.h5ngc requires that exactly one OSGI service satisfies the filtering criteria but no such service was found. at com.vmware.o6jia.context.ExternalServiceTargetSource.getTarget(ExternalServiceTargetSource.java:99) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:192) at com.sun.proxy.$Proxy159.logout(Unknown Source) at com.vmware.vise.security.spring.DefaultAuthenticationProvider.logoutInternal(DefaultAuthenticationProvider.java:548) at c

Investigating virtual machine file locks on ESXi

Details Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails. Failed to add disk scsi0:1. Failed to power on scsi0:1 Powering on the virtual machine results in the power on task remaining at 95% indefinitely. Cannot power on the virtual machine after deploying it from a template. Powering on a virtual machine fails with an error: Unable to open Swap File Unable to access a file since it is locked Unable to access a file <filename> since it is locked Unable to access Virtual machine configuration In the /var/log/vmkernel log file, you see entries similar to: WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path> When opening a console to the virtual machine, you may receive the error: Error connecting to <path><virtual machin

"Performance data is currently not available for this entity" viewing the performance tab

Symptoms While accessing the performance tab and navigating to Overview, you see: No data available The data for Real time, but fails to retrieve it for past 1 day, week, month or year. While selecting the advance parameter in performance tab, you see: Performance data is currently not available for this entity Cause This issue is caused by the vCenter Server database (Postgress) containing a stale/future time stamp reference for the ESXi host when the data was collected. For vCenter Servers using SQL, see "Performance data is currently not available for this entity" error after updating rollup in vSphere Resolution Backup the vCenter database. For more info

thatwaskube

Search This Blog