PENDING Create Application Wizard - Error: Invalid Operation

[SPearson79]

Hi,

We updated our SCCM infrastructure to 2309 a few weeks ago and all has been mostly fine except for we saw the odd case of application creation failure with a basic "Error: Invalid Operation". If we tried to create the application a second time it seemed to be fine so we thought little of it. What we're seeing now is that we just can't create applications at all, even basic test apps with no content fail. We've rebooted the servers and tried creating the app on the console directly on the site server and we're still experiencing this issue. Packages seem to be working fine.

Any help?!?

The SmsAdminUI.log file has the following errors generated by trying to create a new app...

[36, PID:5244][12/07/2023 13:55:32] :System.Management.ManagementException\r\nInvalid operation \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.Put(PutOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)\r\nManagementException details:
instance of __ExtendedStatus
{
Operation = "PutClass";
ParameterInfo = "";
ProviderName = "WinMgmt";
};
\r\n
[36, PID:5244][12/07/2023 13:55:32] :Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nInvalid operation \r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put()
at Microsoft.ConfigurationManagement.AdminConsole.AppManFoundation.AppManWrapper.Put(ReportProgress reportProgress)\r\nInvalid operation
\r\nSystem.Management.ManagementException\r\nInvalid operation \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.Put(PutOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)\r\nManagementException details:
instance of __ExtendedStatus
{
Operation = "PutClass";
ParameterInfo = "";
ProviderName = "WinMgmt";
};
\r\n

 

[Prajwal Desai]

At what step on create application wizard do you get this error?.

 

[SPearson79]

It's right at the end. You get through the entire wizard as if nothing's wrong and then it just gives up. We're struggling to really start trouble-shooting this one.

 

[Prajwal Desai]

Ok that's little strange and I have never seen this before. Does the account has enough permissions to create applications?

 

[SPearson79]

Yes, global admin. My colleague, with the same rights, is experiencing the same thing too and it also happens if we run the console directly on the site server (where we have admin rights).

Worth noting that my colleague and I are basically the only two users of SCCM and we've been packaging applications and adding them to SCCM for years until this.

 

[Prajwal Desai]

I am not sure why this is happening. It will be difficult for me to troubleshoot this issue because I do not have access to your setup. If you have tried all the troubleshooting steps, I would recommend getting in touch with MS support.

 

[manumanu]

I had the exact same error, I found this page here :
https://techcommunity.microsoft.com...9-create-application-wizard-error/m-p/4003318
and the solution (running the command DBCC CHECKIDENT('CI_DocumentStore', RESEED); ) solved my problem.
I had also an error in the wsyncmgr.log :
*** [23000][2627][Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Violation of PRIMARY KEY constraint 'CI_DocumentStore_PK'. Cannot insert duplicate key in object 'dbo.CI_DocumentStore'. The duplicate key value is (33769817).
After the DBCC command, this error disappeared too.

 

[SPearson79]

Thanks for confirming that's worked for you. One of our DBAs confirmed that was an issue in our DB but wasn't happy to apply the fix and we are now waiting on our Microsoft account manager to get back to us for support.

Hopefully when this is complete we can relax as this still comes back every few days to stop us in our tracks.

 

[manumanu]

I launched this command after saving the DB and taking a snapshot of the server's VM (and crossing my fingers !!). But yeah, I think it's safer to wait the green light from Microsoft support !
Good luck and I hope in the end it'll be ok for you.

 

[eng.muath]

any help in this issue ? as i have the same one

 

[tbrooker]

I had the exact same error, I found this page here :
https://techcommunity.microsoft.com...9-create-application-wizard-error/m-p/4003318
and the solution (running the command DBCC CHECKIDENT('CI_DocumentStore', RESEED); ) solved my problem.
I had also an error in the wsyncmgr.log :
*** [23000][2627][Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Violation of PRIMARY KEY constraint 'CI_DocumentStore_PK'. Cannot insert duplicate key in object 'dbo.CI_DocumentStore'. The duplicate key value is (33769817).
After the DBCC command, this error disappeared too.

I thought I might share what MS support replied to our environment (2309 to 2409 upgrade)
The impacts were the same as above, where we couldn't create applications and wsync would fail creating new updates

They asked us to run these commands in this order
DBCC CHECKIDENT('CI_DocumentStore')
The output for us was:
Checking identity information: current identity value '33562697', current column value '33763854'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Was asked to then run
DBCC CHECKIDENT('CI_DocumentStore',RESEED, 33763854)

This resolved the issues immediately, have no idea how it could be 200,000 records off during an upgrade but I would say it was a known issue. They went straight to these troubleshooting step without any fanfare

 

[SPearson79]

I thought I might share what MS support replied to our environment (2309 to 2409 upgrade)
The impacts were the same as above, where we couldn't create applications and wsync would fail creating new updates

They asked us to run these commands in this order
DBCC CHECKIDENT('CI_DocumentStore')
The output for us was:
Checking identity information: current identity value '33562697', current column value '33763854'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Was asked to then run
DBCC CHECKIDENT('CI_DocumentStore',RESEED, 33763854)

This resolved the issues immediately, have no idea how it could be 200,000 records off during an upgrade but I would say it was a known issue. They went straight to these troubleshooting step without any fanfare

It's good to know that Microsoft support are asking to do that. So far we haven't seen that issue come back (or at least we've not noticed it / it's not impacted us).

We're planning on dong an SCCM upgrade at some point in the coming weeks / months so we'll keep an eye out.

 

[M.Stadlmayr]

I thought I might share what MS support replied to our environment (2309 to 2409 upgrade)
The impacts were the same as above, where we couldn't create applications and wsync would fail creating new updates

They asked us to run these commands in this order
DBCC CHECKIDENT('CI_DocumentStore')
The output for us was:
Checking identity information: current identity value '33562697', current column value '33763854'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Was asked to then run
DBCC CHECKIDENT('CI_DocumentStore',RESEED, 33763854)

This resolved the issues immediately, have no idea how it could be 200,000 records off during an upgrade but I would say it was a known issue. They went straight to these troubleshooting step without any fanfare

This worked for me too.

 

[tmcnees]

This worked for me too.

This worked for me as well.

 

[rradch]

I thought I might share what MS support replied to our environment (2309 to 2409 upgrade)
The impacts were the same as above, where we couldn't create applications and wsync would fail creating new updates

They asked us to run these commands in this order
DBCC CHECKIDENT('CI_DocumentStore')
The output for us was:
Checking identity information: current identity value '33562697', current column value '33763854'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Was asked to then run
DBCC CHECKIDENT('CI_DocumentStore',RESEED, 33763854)

This resolved the issues immediately, have no idea how it could be 200,000 records off during an upgrade but I would say it was a known issue. They went straight to these troubleshooting step without any fanfare

Perfect. Worked like a charm.
Thanks