Hi all,
I'm getting the error "Unable to execute 'fetchRelation' for type : ActiveDirectory : java.lang.NullPointerExeption
Played around with different configurations for the plugin without success. Any ideas?
The AD plug-in has been enhanced on the AD part but has no remote execution and WMI as did the Microsoft plug-in.
Please check what functionality you use before removing the Microsoft plug-in.
Christophe.
The old microsoft plugin was AD + WMI logic.
In new AD plugin The WMI part was removed.
The AD functionality was extended, so if your existing Workflows rely only on AD logic you can adjust it to work with the new AD plugin. This "adjustment" is minor change of input/output type names. For example Micosoft:Computer should become AD:Computer.
Hi,
Christophe Decanini schrieb:
The AD plug-in has been enhanced on the AD part but has no remote execution and WMI as did the Microsoft plug-in.
Please check what functionality you use before removing the Microsoft plug-in.
Christophe.
Okay, but the consequence of this is, that you you can have the old microsoft plugin with WMI support or the newer one with proper AD support.
But you can't have both. This is a loss in functionality. 😞 This also means you have to double check all the workflows in your vco deployment when moving to the plugin. In the best case you have to rewrite AD code in the worst case you will loose workflows (which uses the WMI functionality) 😞
That is true. This is because both plugins share some Java classes.
Are you using both ?
If so, if I recall well the WMI support in the Microsoft plug-in was done starting a WMI command line. While not ideal you could use the AD plug-in and start the WMI command line to replace the Microsoft plug-in.
Christophe.
Hi Christope,
to be honest.. I don't know. This is a grown VCO environemnt, so maybe some workflows uses classes/objects from the old plugin? Is there an smart way to check this, without looking at every workflow. For the start I could maybe use "Find elements that use this element" when ONLY actions/workflows are used. But first I have to know which packages,workflows and actions belongs to microsoft plugin and which to the newer AD plugin. How can this be done in a smart way?
What are the exact steps to remove the plugin. I tried the following:
1) Disabled Plugin in VCO Configuration
2) Removed Plugin from plugin/ directory
3) Restarted VCO + VCO Configuration
The plugins seems to be removed , but there are still workflows/packages (com.vmware.library.microsoft) in the VCO that seems to belong to the microsoft plugin. It ssems that the package contains workflows from the old microsoft plugin and some from the newer AD plugin.
i.E.
1) Create user in Organizational unit -> Seems to belong to the microsoft plugin because it throws the message "Unable to find plugin to manage type: Microsoft:OranizationalUnit)
2) Create a user with a password in a organizational unit -> Seems to belong to the active directory plugin, because the worklfow shows the failures from the start of this thread.
How can I clean up, is it safe to remove package com.vmware.library.microsoft?
You should do:
Since -1- is destructive, make sure you make a backup of your vCO DB first OR do this on a vCO server that points to a copy of the vCO prod server DB.
Also before doing anything. Since you have disabled the MS plug-in you can validate the workflows in the treeview to see which one fail because they have dependencies on the plug-in. You can then check workflow by workflow if there is a replacement workflow in the AD plug-in.
Christophe.
Hi Christophe,
Iam using VCO 4.1.0, Build 581..
Quote: "Go in the web configuration and reset plug-in version. This will force the AD plug-in to redeploy its package." I don't see a point where to "reset plug-in version". I only have a button "Reload plugins", but it seems to have no effect.
I tried serveral ways to clean up my VCO installation, but it fails. I also tried to remove both plugin, but it doesn't seem to work properly.
I tried to remove AD- and Microsoft plugin with the following steps:
0) Delete element with content (Package Microsoft)
1) Disable Plugins
2) Shutdown VCO
3) Delete DAR Files
3) StartUp VCO
But, I still have Workflows from these plugins in my "Workflow-View".
Next, I tried to install the old microsoft plugin again, to see if the package will be availabe again in the "Package-View". The plugin seems to be installed correctly but the package did not show up in the "Package-View"...anyway the Micrsoft Plugin seems to work. (Inventory, Walk throug directory)
I found something interesting in the logs (Configured LogLevel ALL).
[...]
2011-08-30 12:12:58.543+0200 DEBUG [ModulesFactory] Plug-in 'Microsoft' does not need installation : version number is the same !
[...]
Did you tried to login in configurator and pres in Troubleshooting tab the links "Clean directories" and "Reset current version". Then you need to restart.
If not tried it yet, please do so and let us know the result.
Best Regards,
Petar.
Hi,
The message is because you did not reset plug-in version in the web configure.
To do it go in Troubleshooting tab /
HI guys,
2011-08-30 12:51:49.605+0200 INFO [SDKModuleDescription] Performing server side installation for plug-in 'Microsoft'
2011-08-30 12:51:49.605+0200 DEBUG [SDKModuleDescription] Performing server side installation action 'Microsoft' -> 'Package installation'
2011-08-30 12:51:49.652+0200 TRACE [PackageFileManager2] Signature ok : dunes-meta-inf
2011-08-30 12:51:49.652+0200 TRACE [PackageFileManager2] Signature ok : elements/83808080808080808080808080808080B580808001175609873343b6bbd2e3eea/data
2011-08-30 12:51:49.652+0200 TRACE [PackageFileManager2] Signature ok : elements/83808080808080808080808080808080B580808001175609873343b6bbd2e3eea/categories
2011-08-30 12:51:49.652+0200 TRACE [PackageFileManager2] Signature ok : elements/83808080808080808080808080808080B580808001175609873343b6bbd2e3eea/content-signature
2011-08-30 12:51:49.652+0200 TRACE [PackageFileManager2] Signature ok : elements/83808080808080808080808080808080B580808001175609873343b6bbd2e3eea/info
2011-08-30 12:51:49.652+0200 TRACE [PackageFileManager2] Signature ok : elements/8F808080808080808080808080808080288180800116073419184677ff406c06b/data
2011-08-30 12:51:49.652+0200 TRACE [PackageFileManager2] Signature ok : elements/8F808080808080808080808080808080288180800116073419184677ff406c06b/categories
2011-08-30 12:51:49.652+0200 TRACE [PackageFileManager2] Signature ok : elements/8F808080808080808080808080808080288180800116073419184677ff406c06b/content-signature
[...]
2011-08-30 12:51:50.355+0200 TRACE [PackageFileManager2] Signature ok : elements/958080808080808080808080808080806081808001175609873343b6bbd2e3eea/content-signature
2011-08-30 12:51:50.355+0200 TRACE [PackageFileManager2] Signature ok : elements/958080808080808080808080808080806081808001175609873343b6bbd2e3eea/info
2011-08-30 12:51:50.355+0200 TRACE [PackageFileManager2] Signature ok : certificates/C=CH,OU=VMware Inc,O=VMware Inc,CN=VMware.cer
2011-08-30 12:51:50.543+0200 TRACE [VSOFactoryBean] --getWorkflowForId() called.
2011-08-30 12:51:50.559+0200 DEBUG [Action_InstallPackage] (plug-in - Microsoft) Element is up-to-date (same version) : Workflow : Create user in Organizational Unit
2011-08-30 12:51:50.559+0200 TRACE [VSOFactoryBean] --getScriptModule(string,string) called.
2011-08-30 12:51:50.574+0200 DEBUG [Action_InstallPackage] (plug-in - Microsoft) Element is up-to-date (same version) : Action : destroyElement
2011-08-30 12:51:50.574+0200 TRACE [VSOFactoryBean] --getWorkflowForId() called.
2011-08-30 12:51:50.590+0200 DEBUG [Action_InstallPackage] (plug-in - Microsoft) Element is up-to-date (same version) : Workflow : Start a service from AD
2011-08-30 12:51:50.590+0200 TRACE [VSOFactoryBean] --getWorkflowForId() called.
2011-08-30 12:51:50.590+0200 DEBUG [Action_InstallPackage] (plug-in - Microsoft) Element is up-to-date (same version) : Workflow : Start a process
2011-08-30 12:51:50.590+0200 TRACE [VSOFactoryBean] --getScriptModule(string,string) called.
2011-08-30 12:51:50.605+0200 DEBUG [Action_InstallPackage] (plug-in - Microsoft) Element is up-to-date (same version) : Action : createUser
[...]
This seems to reinitalize the plugins. But I don't have the microsoft package under the "Packages-View". I had this before, I think it must be availabe in Package-View?!
LIke I mentioned before, I deleted the package, but the workflows were not deleted and this is also "shown" in the second part of the log above.
It should be definitely available in the package view. From the log the package is effectively deployed after you did the version reset. Now I really wonder why it does not show up in the list.
I double checked the log. There are no failures only debuging information that states "everything is fine."
In my opionon,the solution has something to do with the "not deleted workflows". Orchestrator didn't create the workflows, because they already exist, see log. Therefore it doesn't create the package. When I try References->FInd elements that use this elemnt on an other VCO i see the package. When I try it on the problematic VCO I don't see a reference to the selected workflow.
But Iam not able, even as VCO Administrator, to delete the workflows?
Hi,
just to give you a debugging hint:
1) Created a custom package (Add package)
2) Inserted workflows which normaly belongs to the microsoft package
3) Delete package with content
Result: Package was deleted -> Workflows were not deleted
Next test:
1) Created a custom package (Add package)
2) Created a test workflow called "XXX"
3) Added microsoft workflows + workflow XXX
4) Deleted package with content
Result: Package was deleted, workflow XXX was deleted, microsoft workflows were not deleted
In my opinon it has something to do with the privileges on the workflows. Iam also not able to remove the workflows by hand. (In my package view I don't have the little pen icon (edit)). So they will not be removed. And the consequence of this VCO don't install the package because the workflows still exist.
Also the Trace:
[...]
011-08-30 15:26:00.809+0200 TRACE [DunesObjectJMSHelper] -- notify dunes model changes : 'del' on object : BC8080808080808080808080808080808A808080012886191115516f960e61333
2011-08-30 15:26:00.824+0200 TRACE [VSOFactoryClient] JMS Received (del) : null Registered : null
2011-08-30 15:26:00.824+0200 TRACE [VSOFactoryClient] Received change on an object not registered in the factory !
2011-08-30 15:26:00.824+0200 TRACE [DunesObjectJMSHelper] -- notify dunes model changes : 'edit' on object : 848080808080808080808080808080807C818080012886191115516f960e61333
2011-08-30 15:26:00.824+0200 TRACE [SharedVSOFactoryClient] JMS Received (del) : null Registered : null
2011-08-30 15:26:00.824+0200 TRACE [SharedVSOFactoryClient] Received change on an object not registered in the factory !
2011-08-30 15:26:00.824+0200 TRACE [VSOFactoryClient] JMS Received (del) : null Registered : null
2011-08-30 15:26:00.824+0200 TRACE [VSOFactoryClient] Received change on an object not registered in the factory !
2011-08-30 15:26:00.824+0200 TRACE [VSOFactoryClient] JMS Received (edit) : null Registered : null
2011-08-30 15:26:00.824+0200 TRACE [VSOFactoryClient] Received change on an object not registered in the factory !
2011-08-30 15:26:00.824+0200 TRACE [SharedVSOFactoryClient] JMS Received (edit) : null Registered : null
2011-08-30 15:26:00.824+0200 TRACE [SharedVSOFactoryClient] Received change on an object not registered in the factory !
2011-08-30 15:26:00.824+0200 TRACE [VSOFactoryClient] JMS Received (edit) : null Registered : null
2011-08-30 15:26:00.824+0200 TRACE [VSOFactoryClient] Received change on an object not registered in the factory !
2011-08-30 15:26:00.824+0200 TRACE [VSOFactoryBean] --getServerObject called.
2011-08-30 15:26:00.824+0200 TRACE [VSOFactoryBean] --deletePackage() called.
2011-08-30 15:26:00.840+0200 TRACE [DunesObjectJMSHelper] -- notify dunes model changes : 'del' on object : BC80808080808080808080808080808088808080012886191115516f960e61333
2011-08-30 15:26:00.840+0200 TRACE [VSOFactoryClient] JMS Received (del) : null Registered : null
2011-08-30 15:26:00.840+0200 TRACE [VSOFactoryClient] Received change on an object not registered in the factory !
2011-08-30 15:26:00.840+0200 TRACE [SharedVSOFactoryClient] JMS Received (del) : null Registered : null
2011-08-30 15:26:00.840+0200 TRACE [VSOFactoryClient] JMS Received (del) : null Registered : null
2011-08-30 15:26:00.840+0200 TRACE [VSOFactoryClient] Received change on an object not registered in the factory !
2011-08-30 15:26:00.840+0200 TRACE [SharedVSOFactoryClient] Received change on an object not registered in the factory !
[...]
It works!
Many Thanks!
Frank
I had the same issue and it works on mine with version 1.01 as well.
1.096 isn't so good.
This same issue has popped up for me with the current beta plugin build 1.0.2.681 . I can execute the workflows and actions and they seem to work but the inventory tree breaks. I have the same exact config on other vCO servers and they do not break. Is it safe to try rolling back to the previous version and if so what are the exact steps I should take? Help!
Paul