PENDING Unable to create application in ConfigMgr

[Brandi Youngberg]

I am unable to create a new application in Configuration Manager after and in place OS upgrade from 2012R2 to 2019. I get the following error message "The specified file does not exist or the computer running the Configuration Manager console has no Read permissions to the specified file." I have verified permissions are correct.
V/R
Brandi

 

[Prajwal Desai]

What's the ConfigMgr version and did you check if the SCCM server has permissions on the location where the application executable is stored?

 

[Brandi Youngberg]

The ConfigMgr version is 2309 and I did verify that the SCCM Server has permissions to that location.

 

[Prajwal Desai]

The error "Configuration Manager console has no read permissions to the specified file" indicates the permission issue. Create another folder in a different location, place the application file, and see if you encounter the same error.

 

[Brandi Youngberg]

I tried your suggestion and am still getting the same error.

 

[Prajwal Desai]

Run the console as administrator and try once..

 

[Brandi Youngberg]

I installed Configuration Manager Console onto my device and was then able to create applications and deploy them successfully. I am not sure why it will not work on the server but for now I am having success.

 

[Prajwal Desai]

I installed Configuration Manager Console onto my device and was then able to create applications and deploy them successfully. I am not sure why it will not work on the server but for now I am having success.

Did you try what I suggested previously i.e. running console as admin?

 

[Brandi Youngberg]

Yes, I did try your suggestion running console as admin but unfortunately it still gave me the same permissions error.

 

[Prajwal Desai]

If that error is persistent on the server and is occurring for other users too, you should try repairing the console once - https://www.prajwaldesai.com/repair-configuration-manager-console/

 

[Brandi Youngberg]

Thank you, that fixed the issue.