Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

'AttributeError: 'str' object has no attribute 'decode'' 1603 error while upgrading vCenter Server 6.7 with a SQL database and Windows Authentication (66644)

Last Updated: 3/21/2024Categories: TroubleshootingTotal Views: 6597Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Upgrading from vCenter Server 6.7.x to vCenter Server 6.7 Update 1 fails with 1603 when using a SQL database and Windows Authentication. In vminst-con.log file, you will see entires similar to:

Traceback (most recent call last):
File "C:\Program Files\VMware\vCenter Server\vpxd\py\vcdb_update_hci.py", line 326, in <module>
if not main():
File "C:\Program Files\VMware\vCenter Server\vpxd\py\vcdb_update_hci.py", line 322, in main
return doWork(getDBConnection(getConnectionString()))
File "C:\Program Files\VMware\vCenter Server\vpxd\py\vcdb_update_hci.py", line 142, in getConnectionString
decodeStr(get_db_pass_symkey(is_windows_authentication())))
File "C:\Program Files\VMware\vCenter Server\vpxd\py\vcdb_update_hci.py", line 82, in decodeStr
return inputString.decode(sys.getfilesystemencoding())
AttributeError: 'str' object has no attribute 'decode'

Once the update fails, rollback also will fail and vsphere-client service or vsphere-ui service will never start. In vsphere_client_virgo.log file, you will see entires similar to:

[2018-12-04T17:24:59.711-08:00] [ERROR] GiLogServiceListener@ee251b8  org.osgi.service.log.LogService                                   Bundle org.eclipse.virgo.kernel.services_3.7.2.RELEASE, FrameworkEvent ERROR org.osgi.framework.BundleException: The bundle "org.eclipse.virgo.kernel.services_3.7.2.RELEASE [35]" could not be resolved. Reason: Missing Constraint: Import-Package: org.springframework.beans.factory; version="[2.5.6,5.0.0)"
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1332)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1316)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.setBundleSL(StartLevelManager.java:670)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:435)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
[2018-12-04T17:34:59.723-08:00] [ERROR] startup-tracker               org.eclipse.virgo.nano.core.internal.StartupTracker               Kernel has failed to start before the timeout of 600 seconds.
[2018-12-04T17:34:59.726-08:00] [ERROR] startup-tracker               org.eclipse.virgo.medic.eventlog.default                         KE0004E Kernel failed to start within 600 seconds.

Cause

In the case of Windows authentication, the vCenter server installer is unable to determine the database password and hence cannot successfully connect to the database.

Impact / Risks

Once the upgrade fails the roll back may be incomplete. You will need to revert the vCenter from a backup or snapshot to restore operation.

Resolution

This issue "AttributeError: 'str' object has no attribute 'decode'" 1603 error while upgrading vCenter Server 6.7 with a SQL database and Windows Authenticationis is resolved in vCenter Server 6.7 U2.
Available at VMware Downloads.

Workaround

To workaround this issue you can change the SQL authentication mode from Windows to SQL Server prior to starting the update. Please consult the following KB article on how to change vCenter Server database credentials.

*For more information click here: Changing the vCenter Server database user ID and password (1006482)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
使用 HTML5 客户端编辑虚拟机时，将新磁盘添加到 SDRS 群集失败 (66815)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 6.7.x

Take Our Survey

Support Assistant