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

Update of PNID via Appliance Management Interface (VAMI) returns Error: Failed to to start STS service (79037)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 14562Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

PNID Update via Appliance Management Interface (VAMI) fails with Error: Failed to to start STS service

/var/log/vmware/applmgmt/pnid_change.log:

2020-05-07 13:35:59,513 - pnid_utils-run_command():71 - INFO - Running command: /usr/bin/service-control --start vmware-stsd vmware-sts-idmd
2020-05-07 13:38:03,525 - pnid_utils-run_command():89 - INFO - Command exited with exitcode : 1
2020-05-07 13:38:03,525 - pnid_utils-run_command():91 - WARNING - Command failed with following error:
2020-05-07 13:38:03,525 - pnid_utils-run_command():92 - WARNING - b'2020-05-07T13:38:03.503Z  RC = 1\nStdout = \nStderr = Job for vmware-stsd.service failed because the control process exited with error code. See "systemctl status vmware-stsd.service" and "journalctl -xe" for details.\n\n2020-05-07T13:38:03.504Z  {\n    "detail": [\n        {\n            "id": "install.ciscommon.command.errinvoke",\n            "args": [\n                "Stderr: Job for vmware-stsd.service failed because the control process exited with error code. See \\"systemctl status vmware-stsd.service\\" and \\"journalctl -xe\\" for details.\\n"\n            ],\n            "localized": "An error occurred while invoking external command : \'Stderr: Job for vmware-stsd.service failed because the control process exited with error code. See \\"systemctl status vmware-stsd.service\\" and \\"journalctl -xe\\" for details.\\n\'",\n            "translatable": "An error occurred while invoking external command : \'%(0)s\'"\n        }\n    ],\n    "resolution": null,\n    "problemId": null,\n    "componentKey": null\n}\nError executing start on service vmware-stsd. Details {\n    "detail": [\n        {\n            "id": "install.ciscommon.service.failstart",\n            "args": [\n                "vmware-stsd"\n            ],\n            "localized": "An error occurred while starting service \'vmware-stsd\'",\n            "translatable": "An error occurred while starting service \'%(0)s\'"\n        }\n    ],\n    "resolution": null,\n    "problemId": null,\n    "componentKey": null\n}\nService-control failed. Error: {\n    "detail": [\n        {\n            "id": "install.ciscommon.service.failstart",\n            "args": [\n                "vmware-stsd"\n            ],\n            "localized": "An error occurred while starting service \'vmware-stsd\'",\n            "translatable": "An error occurred while starting service \'%(0)s\'"\n        }\n    ],\n    "resolution": null,\n    "problemId": null,\n    "componentKey": null\n}\n'
2020-05-07 13:38:03,525 - pnid_utils-run_command():97 - INFO - STDOUT : Operation not cancellable. Please wait for it to finish...
Performing start operation on service vmware-sts-idmd...
Successfully started service vmware-sts-idmd
Performing start operation on service vmware-stsd...
2020-05-07 13:38:03,525 - pnid_utils-run_command():98 - INFO - Done running command
2020-05-07 13:38:03,526 - pnid_utils-restart_services():1443 - ERROR - 2020-05-07T13:38:03.503Z  RC = 1
Stdout =
Stderr = Job for vmware-stsd.service failed because the control process exited with error code. See "systemctl status vmware-stsd.service" and "journalctl -xe" for details.
2020-05-07 13:38:03,526 - pnid_utils-update_task_status():1293 - INFO - Task : Failed to start STS Services.

/var/log/vmware/sso/catalina.yyyy-mm-dd.log:

07-May-2020 13:36:08.245 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Error during ServletContainerInitializer processing
javax.servlet.ServletException: com.sun.xml.ws.transport.http.servlet.WSServletException: WSSERVLET11: failed to parse runtime descriptor: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'tenantServices' defined in class path resource [stsApplicationContext.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.identity.sts.idm.impl.IdmTenantServicesImpl]: Constructor threw exception; nested exception is java.lang.IllegalStateException: Failed to initialize CasIdmClient
at com.sun.xml.ws.transport.http.servlet.WSServletContainerInitializer.onStartup(WSServletContainerInitializer.java:70)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5154)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:743)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:719)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:705)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:970)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1841)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.sun.xml.ws.transport.http.servlet.WSServletException: WSSERVLET11: failed to parse runtime descriptor: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'tenantServices' defined in class path resource [stsApplicationContext.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.identity.sts.idm.impl.IdmTenantServicesImpl]: Constructor threw exception; nested exception is java.lang.IllegalStateException: Failed to initialize CasIdmClient
at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.parseAdaptersAndCreateDelegate(WSServletContextListener.java:141)
at com.sun.xml.ws.transport.http.servlet.WSServletContainerInitializer.onStartup(WSServletContainerInitializer.java:65)
... 12 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'tenantServices' defined in class path resource [stsApplicationContext.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.identity.sts.idm.impl.IdmTenantServicesImpl]: Constructor threw exception; nested exception is java.lang.IllegalStateException:Failed to initialize CasIdmClient
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.identity.sts.idm.impl.IdmTenantServicesImpl]: Constructor threw exception; nested exception is java.lang.IllegalStateException: Failed to initialize CasIdmClient
Caused by: com.vmware.identity.idm.InvalidArgumentException: store.getExtendedIdentityStoreData().getAttributeMap() Must not be null.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

The issue is caused due the following conditions:

vCenter Server has the migration path as 5.x -> 6.0/6.5 -> 6.7

Source vCenter Server (Windows based) was installed with shortname instead of Fully Qualified Domain Name

LocalOS Identity source in vCenter Server Appliance (VCSA) is set to short name instead of localos

Resolution

This issue is resolved with VMware vCenter Server 6.7 Update 3j.

Workaround

Revert the node to a working state post PNID update failure

Login to the VCSA via vsphere client with Single Sign-on administrator credentials

Navigate to Administration -> Configuration

Delete the LocalOS Identity source with vCenter machine short name

Click on Identity Sources on the right pane

Select the Identity Source with type value as short name of VCSA

Click remove to clear the entry

Create an Identity Source with Domain as localos

Click on Add Identity Source

Select the Identity Source Type as Local operating system of SSO server

Enter the value under Name as localos and click Add

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
VMware Workspace ONE Web 7.13 for Android リリースのお知らせ (79051)

KB
•
Workspace ONE Tunnel 5.6 for Android リリースのお知らせ (79048)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

Take Our Survey

Support Assistant