I created a new project in my on premise LAB installation of Azure DevOps Server 2019 Update 1 (Express), with repo TFVC and process template CMMI (predefined).
When I try to save any work item (of any workitem type) or any activity in product backlog, raises error
TF401320: errore nella regola per il campo Valutazione - CMMI. Codice errore: Required, HasValues, LimitedToValues, InvalidEmpty.
translating from italian some like
TF401320: error in rule about field Triage - CMMI. Error code: Required, HasValues, LimitedToValues, InvalidEmpty.
Before saving, when i open edit form to create a new workitem, under column "Planning" appears
Valutazione Non è possibile creare il controllo dell'elemento di lavoro di tipo "FieldControl"
translating from italian some like
Triage Cannot create the control of work item type "FieldControl"
If I create a project with process template Scrum, there is no issue creating any workitem.
Have you any idea or advice?
Thanks in advance
Related
I have integrated authentication jbpm with LDAP. But, When start process instance. I cannot create user task.
Here is log server, can anyone can help?
2021-05-14 17:18:39,683 ERROR [org.jbpm.services.task.wih.LocalHTWorkItemHandler] (default task-10) Fri May 14 17:18:39 ICT 2021: Error when creating task on task server for work item id 5. Error reported by task server: There are no known Business Administrators, task cannot be created according to WS-HT specification: org.jbpm.services.task.exception.CannotAddTaskException: There are no known Business Administrators, task cannot be created according to WS-HT specification
at org.jbpm.services.task.commands.UserGroupCallbackTaskCommand.doCallbackOperationForPeopleAssignments(UserGroupCallbackTaskCommand.java:298)
at org.jbpm.services.task.commands.AddTaskCommand.execute(AddTaskCommand.java:109)
at org.jbpm.services.task.commands.AddTaskCommand.execute(AddTaskCommand.java:53)
at org.jbpm.services.task.commands.TaskCommandExecutorImpl$SelfExecutionCommandService.execute(TaskCommandExecutorImpl.java:80)
at org.jbpm.services.task.commands.TaskCommandExecutorImpl$SelfExecutionCommandService.execute(TaskCommandExecutorImpl.java:65)
You need to create an "admin" group, for example
cn=admin,ou=Roles,dc=jbpm,dc=org
You may take a look at "LDAP structure" chapter and source code:
https://blog.kie.org/2021/02/migrating-jbpm-images-secured-by-ldap-to-elytron.html
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I am facing an error when I try to create a collection on Azure DevOps On premises from the administration console.
It seems to happen when DevOps manages the CreateCollection.Service.Analytics part. I can't find any reference to this problem on Google.
I choose the Inheritance process model in the wizard and when I launch the installation, after a few minutes :
[15:15:32.793] Executing step: Enable analytics on-prem for new collections
[15:15:32.793] Executing step: 'Enable analytics on-prem for new collections' AnalyticsCollection.EnableAnalyticsOnPrem (360 of 387)
[15:16:13.407] [Warning] Impossible d'activer Analytics pour cette nouvelle collection. Vous pouvez y remédier en réactivant Analytics manuellement. Pour plus d'informations, consultez la documentation : https://go.microsoft.com/fwlink/?linkid=2093060.
[15:16:13.533] [Warning] Analytics failed to enable for new collection due to: Le bail de AnalyticsStateService.SetFeatureState, dont le propriétaire est f24b9929-5d00-498c-9b4c-1e6d8c5f8f77, obtenu le 10/03/2020 14:15:33 par le processus abde3e12-0d37-4751-a1fe-23387f8c5268 a expiré le 10/03/2020 14:16:03
***
in english :
Unable to enable Analytics for this new collection. You can fix it by reactivating Analytics manually (so later no ??? )
The lease for AnalyticsStateService.SetFeatureState, owned by f24b9929-5d00-498c-9b4c-1e6d8c5f8f77, obtained on 10/03/2020 14:15:33 by the process abde3e12-0d37-4751-a1fe-23387f8c5268 expired on 10 / 03/2020 14:16:03
***
[15:16:13.540] Step passed (with warnings): Enable analytics on-prem for new collections. Execution time: 40 seconds.
[15:16:13.540] [StepDuration] 40,7454734
[15:16:13.597] [GroupDuration] 67,5660477
[15:16:13.597] [OperationDuration] 67,56617
[15:16:13.597] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[15:16:13.597] ++ Executing - Operation: CreateCollection.Service.Analytics.Sdk, Group: CreateCollection.Service.Analytics.Sdk
[15:16:13.597] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[15:16:13.597] Step skipped: Queue Analytics Maintain Staging Schedules Job.
[15:16:13.600] [GroupDuration] 0,0046515
[15:16:13.600] [OperationDuration] 0,0046985
[15:16:13.600] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[15:16:13.600] ++ Executing - Operation: CreateCollection.Service.Notifications, Group: CreateCollection.Service.Notifications
[15:16:13.600] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[15:16:13.600] Executing step: Load service tokens
[15:16:13.600] Executing step: 'Load service tokens' FrameworkTokens.ConfigureServiceTokens (362 of 387)
[15:16:13.603] Step passed: Load service tokens. Execution time: 3 milliseconds.
[15:16:13.603] [StepDuration] 0,0002612
[15:16:13.603] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Executing step: Create Framework Security Namespaces
[15:16:13.603] Executing step: 'Create Framework Security Namespaces' Security.CreateSecurityNamespaces (363 of 387)
[15:16:13.603] There are 1 security namespaces to create/update.
[15:16:13.603] Validating 'EventSubscription' security namespace.
[15:16:13.603] Creating/updating security namespace(s).
[15:16:13.603] [Error] Le bail de AnalyticsStateService.SetFeatureState, dont le propriétaire est f24b9929-5d00-498c-9b4c-1e6d8c5f8f77, obtenu le 10/03/2020 14:15:33 par le processus abde3e12-0d37-4751-a1fe-23387f8c5268 a expiré le 10/03/2020 14:16:03
***
in english :
Same error but with stack trace
The lease for AnalyticsStateService.SetFeatureState, owned by f24b9929-5d00-498c-9b4c-1e6d8c5f8f77, obtained on 10/03/2020 14:15:33 by the process abde3e12-0d37-4751-a1fe-23387f8c5268 expired on 10 / 03/2020 14:16:03
***
[15:16:13.633] Microsoft.TeamFoundation.Framework.Server.LeaseLostException: Le bail de AnalyticsStateService.SetFeatureState, dont le propriétaire est f24b9929-5d00-498c-9b4c-1e6d8c5f8f77, obtenu le 10/03/2020 14:15:33 par le processus abde3e12-0d37-4751-a1fe-23387f8c5268 a expiré le 10/03/2020 14:16:03
[15:16:13.633] à Microsoft.TeamFoundation.Framework.Server.VssRequestContext.CheckCanceled(Boolean throwIfShutdown)
[15:16:13.633] à Microsoft.TeamFoundation.Framework.Server.VssRequestContext.get_ServiceProvider()
[15:16:13.633] à Microsoft.TeamFoundation.Framework.Server.VssRequestContextExtensions.GetService[TService](IVssRequestContext context)
[15:16:13.633] à Microsoft.VisualStudio.Services.Framework.SecurityStepPerformer.CreateOrUpdateSecurityNamespaces(IVssRequestContext requestContext, ServicingContext servicingContext, LocalNamespaceDescriptionStepData[] securityNamespaceDescriptions)
[15:16:13.633] à Microsoft.TeamFoundation.Framework.Server.TeamFoundationStepPerformerBase.PerformHostStep(String servicingOperation, ServicingOperationTarget target, IServicingStep servicingStep, String stepData, ServicingContext servicingContext)
[15:16:13.633] à Microsoft.TeamFoundation.Framework.Server.TeamFoundationStepPerformerBase.PerformStep(String servicingOperation, ServicingOperationTarget target, String stepType, String stepData, ServicingContext servicingContext)
[15:16:13.633] à Microsoft.TeamFoundation.Framework.Server.ServicingStepDriver.PerformServicingStep(ServicingStep step, ServicingContext servicingContext, ServicingStepGroup group, ServicingOperation servicingOperation, Int32 stepNumber, Int32 totalSteps)
[15:16:13.633] Step failed: Create Framework Security Namespaces. Execution time: 30 milliseconds.
It is the first collection that I created from scratch on Azure DevOps, but I already have a migrated collection from tfs 2015 which works very well. I don't want to create my collection on tfs2015 only to migrate it to devops :(
The reports are not configured, I understand that I can configure them later when I really want to use them. I did not install SSRS but if it is necessary I would do it.
The Analytics service feature is installed on my instance of SQL Server. SQL Server is installed on the same server.
The database for the collection was created but the state in the console is Offline and I cannot re-execute the creation work I have an error, I have to delete it with command line.
Edit:
I tested a creation with the xml process model and it's working. In the settings page I see Analytics is activated.
Edit 2: Thanks to #PatrickLu-MSFT, that's work.
I had already tried to restart the server before posting but without success.
This time I tried to restart all SQL services from SQL Configuration Manager and recreate the collection, but it still failed, it was not enough.
Then I used Services to restart the service again: SQL Server (MSSSQLSERVER) and I reboot the server as Patrick told me. And it worked, I was able to create my collection with inheritance model!
According to your description, there maybe something wrong with your SQL Service.
Please attempt to restart the SQL Server service, and if it hung up on trying to stop the service. Then you could try to reboot the server and try to create a new collection again.
If this not do the trick, also kindly check if there are some information in Event View. That might help pinpoint the problem.
In Dynamics CRM 2016 on-premise, I need to read in a plugin some information from another Dynamics CRM 2016 on-premise.
I am trying to use use Microsoft.Xrm.Tooling.Connector to get a CrmServiceClient object for getting information from the remote Dynamics CRM.
I can register the plugin but when the step of the plugin is triggered I receive an error message:
Business Process Error
Impossible de charger le fichier ou l'assembly 'Microsoft.Xrm.Tooling.Connector, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' ou une de ses dépendances. Le fichier spécifié est introuvable.
I want to know if this is the right way to get information from another CRM in the context of a plugin, and how can I resolve the above error.
Thank you
Radu
The Microsoft.Xrm.Tooling.Connector.dll is not available on the CRM Server, because it is a client-side library.
You need to make it available on the server by adding it (and any dependencies) to the GAC (on each CRM server) or including it with the assembly using ILMerge.
We have recently migrated from TFS 2010 to TFS 2015 (Update 2) and everything seems to work fine apart from
the following error we get every 12 minutes.
TF53010: The following error has occurred in a Team Foundation component or extension:
Application Domain: TfsJobAgent.exe
Assembly: Microsoft.TeamFoundation.Framework.Server, Version=14.0.0.0, Culture=neutral,
Detailed Message: TF221123: Job Version Control Warehouse Sync for team project collection JLT TFS 2010 was unable to run after 20 attempts.
After checking "Process status" through the "Warehouse Control Web Service" I get the following message.
I would like to understand the core reason of why this is happening and how we can resolve this isue?
<Job JobProcessingStatus="DataChange" Name="Version Control Warehouse Sync">
<LastRun Result="Stopped" EndTimeUtc="2016-06-30T14:10:50.19Z" ExecutionStartTimeUtc="2016-06-30T14:00:49.877Z" QueueTimeUtc="2016-06-30T14:00:49.203Z">
<ResultMessage>
[Version Control Warehouse Sync]: ---> MakeDataChanges() result=DataChangesPending.
---> MakeDataChanges() result=DataChangesPending.
---> MakeDataChanges() result=DataChangesPending.
---> MakeDataChanges() result=DataChangesPending. --->
...
...
---> TF221123: Job Version Control Warehouse Sync for team project collection JLT TFS 2010 was unable to run after 20 attempts.
</ResultMessage>
</LastRun>
<CurrentRun ExecutionStartTimeUtc="2016-06-30T14:12:50.75Z" QueueTimeUtc="2016-06-30T14:12:50.19Z" JobState="Running"/>
</Job>
After checking this further we found that this is a known issues (confirmed by Microsoft) and has been fixed in TFS 2015 (Update 3).
Although, it requires to apply the latest Update of TFS 2015, however, it can be achieved by applying the following workaround at database level.
Please run the following script on the TFS Collection Database
DECLARE #partitionId INT = 1
DECLARE #registryUpdates typ_KeyValuePairStringTableNullable
INSERT #registryUpdates ([Key], Value)
SELECT ‘#\Configuration\VersionControl\CodeChurn\InUpgrade\’, NULL
EXEC prc_UpdateRegistry #partitionId, #registryUpdates
DROP TABLE tbl_UpgradeCodeChurn
Detailed information can be found in the following article.
After running this script and leaving it for few hours resolved this reported issue.
I have a simple use case of the Drools Expert KnowledgeAgent. I'm using Drools 5.3.0.Final and my rules are already compiled in Guvnor 5.3.0.Final.
My changeset xml file looks like the following:
<add>
<resource type="PKG" source="http://ssmdeoasd01.susalud.com:7777/drools-guvnor/org.drools.guvnor.Guvnor/package/co.com.sura.seguros.adultomayor.consultas/LATEST"/>
</add>
Tha PKG contains rules from a single simple DTABLE.
When I change the DTABLE and upload it to Guvnor (while the app is still running), Drools Expert indeed identifies the change, but do not apply it. The console looks like the following:
Compilando reglas ...
Reglas compiladas ...
Tiempo de compilacion de reglas: 0 ms
Obteniendo manager ...
Manager obtenido ...
Obteniendo sesión de conocimiento ...
listKnowledgePackages.size(): 1
Sesión de conocimiento obtenida ...
3 Padre
2 Hermanos
1 Conyuge
[2013-01-16 15:54:17,670:debug] ResourceChangeScanner attempt to scan 1 resources
[2013-01-16 15:54:17,684:debug] ResourceChangeScanner modified resource=[UrlResource path='http://ssmdeoasd01.susalud.com:7777/drools-guvnor/org.drools.guvnor.Guvnor/package/co.com.sura.seguros.adultomayor.consultas/LATEST'] : 1358369287000 : 1358369637000
[2013-01-16 15:54:17,684:debug] ResourceChangeNotification received ChangeSet notification
[2013-01-16 15:54:17,684:debug] ResourceChangeScanner thread is waiting for 60 seconds.
[2013-01-16 15:54:17,684:debug] ResourceChangeNotification processing ChangeSet
[2013-01-16 15:54:17,684:debug] ResourceChangeNotification ChangeSet modified resource=[UrlResource path='http://ssmdeoasd01.susalud.com:7777/drools-guvnor/org.drools.guvnor.Guvnor/package/co.com.sura.seguros.adultomayor.consultas/LATEST'] for listener=org.drools.agent.impl.KnowledgeAgentImpl#10655dd
[2013-01-16 15:54:17,686:debug] ResourceChangeNotification thread is waiting for queue update
Compilando reglas ...
Reglas compiladas ...
Tiempo de compilacion de reglas: 0 ms
Obteniendo manager ...
Manager obtenido ...
Obteniendo sesión de conocimiento ...
listKnowledgePackages.size(): 1
Sesión de conocimiento obtenida ...
3 Padre
2 Hermanos
1 Conyuge
Even though the KnowledgeAgent identifies the change, the rule keep compiled the same and no changes are reflecte in the result.
I have no particular configuration for the KnowledgeAgent nor specific extensions. I have used the default listeners and so instead.
Why is this happening?
I was making a mistake.
I was building the agent with an existing KnowledgeBase. Then when the agent was instantiated I was obtaining the base from that agent and keeping a reference to that base in order to always obtain a session from that base. I thought that if the base in the agent changed, then my base -which was obtained from the agent- changed too.
Then, when the rules changed in Guvnor, the agent indeed did its job and recreated its KnowledgeBase but because of the fact that I was always referencing the base obtained immediately after the agent instantiation and getting a session from that old KnowledgeBase then the rules executed were those in the old base.
The references are ok now and the changes in the rules are reflected in the execution :)