Customization publish freezing with no errors on local dev instance

@MichaelShirk - I posted this same thing to the community a while back.  I ran into same issue at one time.  It only happened on my internal test/dev server and not for every instance (never in SaaS production.  In my case, even though it never said successful - all customs were published and worked.  I linked to my topic a while back and you can see those replies.  This was on a 23R2 environment and once I upgraded I never ran into again.

@MichaelShirk For best practise of package publishing

1. Keep instance in Maintainence Mode.
2. Make sure no process are running in System Monitor- Request in process to completed all operations.
3. Publish the customization packages,

If you still facing an issue please increase the time for package publishing in the local environment.

@kyoung14 I marked your question as “Best Answer” in good faith that the issue will be resolved for me as well, once we upgrade to 24R2. 

Thank you!

I just started getting this same issue on both my local and production instance. It seems to only occur when I add a customization project (even just a comment-only database script). I can add the same code to older customization projects without any issue. 

Anything at the DAC or graph level seems to be working, but custom actions do not seem to load when the compilation screen freezes. For example, buttons I created that link processing screens to corresponding GIs do not display on the site.

I haven’t found a solution yet, but I would be curious to see if others are still having similar issues, or if updates seem to fix the problem. (I did update some of my laptop software recently, but that still does not explain the production server...)

Thanks,

Aaron

Coming back to this again because I’m having constant issues with this on 26R1. 
It was never really resolved, but I’m seeing it now more than ever. 

I think I’ve had it a time or two on our production environment, but definitely far more on my local dev instance. 

The publish process will freeze and never show any errors, but will also not proceed. Even if left overnight. 
This happens at any point in the publish process, seemingly without rhyme or reason. Sometimes I have to retry many times before the publish will complete. 

It’s extremely frustrating.

I am experiencing the same thing. When this happens, I usually check the system monitor, sometimes it will show the projects have been published, other times it just says at least one project has been unpublished, then I refresh my browser and try again. 

Hopefully this gets resolved soon! 

Please on the Profiler then allow expection,LINQ,LOG ,Trace then check in Profiler you get any error ? 

​@MichaelShirk 

I have been encountering this recently and almost always, it was due to the amount of memory IIS Worker Process was taking up. Very hard to get on a production SaaS instance but worth monitoring if you are on-prem and easy to do on a dev machine. In my business where I have a few tabs open and not handling day to day support, I don’t encounter it. At my day job, where I have mulitple applications, instances, and IDE’s open I get it frequently.

It almost always seemed like a silent IIS recycle, sometimes not even coming up with the ‘Server has been restarted’ message. It may be worth checking windows event viewer.

Have you guys set a limit on the IIS AppPool private memory? 

Thanks, this gives me a few more things to look into.

 
I haven’t tried it often enough to confirm, but it seems like I might not encounter the issue if I recycle the app pool for the instance, before starting the publish.
 

​@MichaelShirk 

Forgot to mention, it can also show up in form of a DB query timeout.

​@Chris Hackett who can we tag to find out if this is encountered/how it’s fixed internally? 

I would really like to know if there’s some setting that can be adjusted on my machine that would resolve it. 

Thanks!

Hi ​@MichaelShirk - Please open a case with Support in order to get to the correct internal resource unless we have someone internally chime in here. Thank you