![]() It fails to do its automatic repair and just bootloops but if I disable driver signature enforcement then I can get it to boot. Then I was going to reboot it 5 more times while still making sure to run the task scheduler event once between each reboot but on the 3rd reboot I got this Then I connected it to a Test Domain(default setup, not being used for anything other than this test) I had created on another Hyper-V VM. This ran fine and I rebooted it 5 times while making sure to run the Task Scheduler event once between each reboot. (On this Virtual Machine Test it's set to an arbitrary folder I created with some empty text files in it, as SolidWorks PDM isn't installed so the normal folder I'd backup doesn't exist.) Its simple a batch script that deletes the contents of a network drive folder and then calls robocopy to copy a folder to that same location on a network drive. Then I set up the same Task Scheduler script I have been using this entire time. In an effort to narrow down what could be the cause of this I decided to make another Hyper-V virtual machine with Windows Server 2019 and all I did was install the OS and all of the updates through Windows Update(no SQL or SolidWorks PDM). I am open to any sort of debugging just let me know what to do. I also saw this in the tool BlueScreenView: I was able to pull a MEMORY.DMP file from one of the crashes but I don't really know what I am looking at. ![]() I have also contacted SolidWorks and they have no records of other people experiencing this error with SolidWorks PDM 2022 SP2 and Windows Server 2019.Īlso, for the record I initially used SolidWorks PDM 2019 SP5 which uses SQL Express 14 and encountered the same issue, so I switched to 2022 because 2019-2021 all use SQL Express uses SQL Express 19. I have contacted Dell and their support has said that it must be a software or driver conflict because they have run multiple hardware diagnostics and everything passes. This has happened 5+ times exactly like this. If I don't restart it right then, then it will still eventually BSOD on its own within the following 24hours. But when this error comes up, the very next time I restart this server it will BSOD. This happens while I am logged in as the administer and sometimes it will happen right after I had just closed the Task Scheduler, realized I forgot something and I will try to open it again to the error I just mentioned. For more information contact the administer." The reason I think this is because on multiple occasions right before a BSOD happens, I will try to open the Task Scheduler and error will pop up that says "An administer has blocked you from running this app. I think this issue may be related to the Task Scheduler but I am not sure. I have attempted every repair of the installation that I can find online(sfc, dism, bcdedit, bootrec etc) and none of them work to fix and boot the Server 2019 install. ![]() I have tried both Option 1 and Option 2 when it comes to Backup Method 3)īut without fail the server will BSOD on me with stop error code CRITICAL_SERVICE_FAILED 0x0000005A. I install and configure Windows Server 2019(bare metal), then I install SolidWorks PDM and get it fully configured with its included SQL Express 19 installation and then lastly I configure the backups of the SolidWorks PDM/SQL components using some batch scripts and the Task Scheduler. EDIT: I install SQL Server Management Studio 18.11.1 as well, this is needed for the backup process I am using SolidWorks PDM 2022 SP2, no other software gets installed on this server other than whats needed for SolidWorks PDM to function. ![]() This server will be for all of our CAD documents and revision control. I have a brand new Dell R340 server that I have installed Windows Server 2019 on.
0 Comments
Leave a Reply. |