*This post is locked for comments
*This post is locked for comments
The 3.5 Net Framework which was released 9 years ago, is not sufficient for the RMS 2.0.2000 cumulative update and in order for this customer to potentially resolve his deadlock error it was recommended he upgrade his RMS. It is also wise, to upgrade to SQL 2008 R2 Express or higher, as neither Windows 8.1 or Windows 10 are compatible with SQL 2005 Express. If you would like to continue to use hardware and a 15 year old operating system in your business, you certainly may. Encouraging others to follow your example however, may not be advisable because as this case demonstrates. Microsoft cannot provide a solution that is outside the limitations of your operating system XP was end of life over two years ago, and it isn't supported any longer.
Microsoft Net. Framework ver 3.5 that is required for SQL up to 2008 including for win XP can be downloaded from https://www.microsoft.com/en-au/download/details.aspx?id=21
and https://www.microsoft.com/en-au/download/details.aspx?id=25150 is for service pack which is required as well for the server to work.
Good luck
In order to apply the CU 5 update Malak, as we discussed in your other forum posts and per the requirements of CU5. (The dot net framework needs to be updated). Since no updates are available for Windows XP systems it is not possible to update the dotnet framework or upgrade your RMS to 2.0.2000. Unless you move to a supported operating system.
Hello Malak,
What version of RMS are you running?
The deadlock issue was identified as a product defect within RMS and was resolved on the Cumulative Update 5 release.
If you go to Help | About in Store Operations Manager, if your build is not at least 2.0.2000, I would recommend upgrading to CU5, as well as the latest hotfix, #60, both of which can be downloaded here:
https://mbs.microsoft.com/customersource/northamerica/RMSPOS/downloads/hot-fixes/20SPHF-V2
Thank you,
Scott Wardzinski
Microsoft Dynamics RMS & POS Support Engineer
It wasn't necessary for anything additionally to be mentioned, I recognized the error message format as one from a Windows XP machine and as I'm familiar with the system requirements for the RMS application as well as the error message two things immediately came to mind. 1. Windows XP isn't a supported operating system and 2. The customer isn't keeping his RMS build, his Windows or his SQL updated and because he's using Windows XP he can't.
My present build is 2.0.2022 on Windows 10 Pro 64bit running SQL 2008 R2 SP3 and I can assure you, I am not receiving deadlock errors.
Cheers,
RMS 2 works perfectly on XP. in fact many users complain about Win 7 and Win 10 not being good pairs then XP and RMS. But from the first post of this error there is no mention any information apart that is an error message. Are we missing something here?
I believe since Windows XP is not a supported or a secure environment in which to run RMS you may want to start with upgrading that machine to A Windows 7 Pro or higher operating system, just a thought.
Malak, if you give more details of your problem you may have some chance of getting help from the forum. Good luck.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 290,888 Super User 2024 Season 2
Martin Dráb 229,247 Most Valuable Professional
nmaenpaa 101,156