Issue seen in build 5.4.2401.1004.
When installing RCT 5.4.2401.1004 on a Windows Workstation all configuration options are available.
When installing RCT 5.4.2401.1004 on a Windows Server all configuration options are greyed out.
Can you tell me what OS you are seeing this on? So we can try to repro this within our lab.
We have seen this both on Server 2019 - Version 1809 (OS Build 17763.5329)
and Server 2022 - Version 21H2 (OS Build 20348.2227).
I have not tried installing RCT 5.4 on server 2016.
RCT 5.3 runs just fine on both Workstation and Server, so we have gone back to 5.3 on Server OSes.
Thank you for looking into this issue.
Good morning!
Garth asked me to test this in my lab and I was not able to reproduce the issue. I donāt have RMS configured with RCT and my options are not grayed out. I was using Windows Server 2022 Standard. If you still seeing the options grayed out, you can put a ticket in with us here: Support Ticket Form - Recast Software
Respectfully,
Alex E.
Technical Support Engineer
support@recastsoftware.com
Learn more at Recast Academy!
Could you also look at the Console Extension logs here: C:\Users\<UserAccountAccessingTheConsole>\AppData\Roaming\Recast Software\Logs
Respectfully,
Alex E.
Technical Support Engineer
support@recastsoftware.com
Learn more at Recast Academy!
I will put in a ticket.
The Recast log shows āLicense is expiredā, but inside of the console, it clearly shows that we have a valid license, and that it does not expire until 5/30/2024.
Hi there Jeremy,
Thank you for the update. Can you please send this screenshot along with your logs to support@recastsoftware.com? We look forward to assisting you with this issue. 
Log location: C:\Users\<UserAccountAccessingTheConsole>\AppData\Roaming\Recast Software\Logs
Watching this with interest. Iām having the same issue on multiple servers with the community version. Since about the start of December, logs arent even being written (the last logs also indicated the license had expired)
Iāve removed, reinstalled and yesterday even upgraded to the new release. No change.
Deleting my app data for the product results in the folder not even being recreated, its no longer trying to write to %appdata%\Recast Software at all.
This is occurring on multiple servers, all users (who are full admins of SCCM) and has been the case of the last 3 versions of the tool.
The only thing in common is that we also run the HP MIK extension in the console. This wasnt previously an issue, but whether or not this is causing a conflict is anyones guess at this point.
HP MIK installs an outdated DLL within the ConfigMgr folder which it shouldnāt place it there. Recast has opened a support case with HP to have them remove this outdate DLL from the ConfigMgr console.
We created a PowerShell script to solve (work around it) this problem. you can learn more about it from this post. ConfigMgr Crashes After Right Click Tools | Recast Docs
1 Like
Excellent, thanks for this info Garth.
Any clues as to the chances of this script being run and it breaking MIK in its efforts to fix RCT?
The troubleshooting leans towards the removal of MIK, which Iām not going to do, for me its more important than RCT is at this point so equally I dont wish to break that just to solve this problem.
I notice there was a new release of MIK also in December that Iāve not installed yet. Iāll give that a go first, see if HP have got their act togetherā¦
Just as a follow up. This powershell script does indeed break MIK, so for the time being at least it looks like its one or the otherā¦ that or run an āoldā RCT.
I had to looked at the script since I didnāt write it myself. Was it does is make a copy of the config file as a backup then it editing the bindings to allow (force??) serilog.dll to bind the correct DLL as needed. HP is using old DLL which might have problems (sec risk, guess on my partā¦) We need to upgrade that DLL to support .Net 8.
I did touch base the the HP team this am. if/when they get back to me I will let you know. or if Iām bored (haha) I will try to repro it in my lab and get both working.
BTW what error do you get???
1 Like
It simply crashes the console Garth - the usual āstopped respondingā popup, then the console closes. Exactly what RCT did, prior to running the script.
Iām asking internally about what else we can do to fix thisā¦
Soā¦ The answer I got back is we would need to see the fusion logs.
I suggest closing as much as you can before enabling fusion logging and to turn it off (delete the key) after you are done. Then you can zip up the folder and hopefully email it to our support team. Make sure that you say it is for me, they will forward it to me.
For clarity, it is RCT or MIG that is crashing?
How to Enable fusion logging:
- Import the following reg file into the registry.
- Create a FusionLog folder under C:\
- Close and reopen the .NET application to collect Fusion logs under C:\FusionLog
I wanted to report back that the latest build 5.8 seems to have fixed this issue (at least options are not greyed out, and the ConfigMgr console is no longer crashing).
1 Like
How to Enable fusion logging:
- Import the following reg file into the registry.
- Create a FusionLog folder under C:\
- Close and reopen the .NET application to collect Fusion logs under C:\FusionLog
This forums will not allow me to attach the text from the reg file or attach it as a text file. look for a private message.
Depends on the situation. If the script has not been runā¦ RCT crashes if trying to access it from the left-hand menu. All right-click functions are greyed-out. If I run the script to fixā¦ then MIK crashes and is non-functional. Iāll get RCT upgraded again (as Iāve since reverted the config file and downgraded RCT,) and then Iāll enable logging as you suggest.
That is not the case at all for me. That sounds more like the update fixed an expired license which couldāve been that particular cause of the greyed-out menus.