I recently loaded Windows 10 on my PC with V 2015.1. I am having a few issues. #1 - I cant save to my C Drive anymore and if I open an existing program on C drive, I get "serialization error " and " File Closed because of bad archive" that kills program. #2 - With Datapage RT ,get errors "cannot update file DPUPDATE.EXE" . #3- Tried saving PDF Files from Report. It keeps updating like it's working but doesn't actually save the file. Everything looks as if it would be an issue with administrative rights on my PC, but I have full Privileges. My IT guy tells me it's PC-Dmis issue not windows 10 issue. I am looking for any advice I can get before I call hexagon.
If you don't run PC-DMIS as an administrator you will see all the shared network drives and when you do you will not have access. This is clearly a permission problem.
Not exactly a
permission problem, but mapping network drives in the wrong way. Clearly a case for IT!
Issues still going on here. Can't open or save programs inside C:Program Files and can't update Datapage in C:Program Data folders. But I can save Excel Documents in those drives. I would think if I couldn't save programs on that drive that I wouldn't be able to save anything on that drive.
Mike, I'm going to guess that your issue is a different issue, because I've used the fix on 3 separate computers, and IT has used the fix on others, and it fixes the issue of "Not seeing network locations when "Run as Administrator" is checked".
I think the issue starts right down at the fact that you cannot write to your C drive.
Did you try the same thing I suggested to Numbers? Delete your shortcut, grab the executable from the install location, go back through the compatibility tab, "Change settings for all users" button, check the "Run as Admin", apply and close, and then try opening by double clicking the shortcut.
You the man Vinnie!!! That did the trick. I haven't had time to mess with any of this. Took few minutes and tried it and all problems are fixed. Thank You!!
In my opinion, running as Admin should never be seen as a
solution, just a way to check if the problem is related to access rights. After verifying that access rights is the problem, those rights should be adjusted for the PC-DMIS users, but only where needed, not by giving the user full superpowers. The PC-DMIS ReadMe.PDF has an appendix C covering those things.
Actually it is (it can be argued either way though). VinniUSMC idea of running in “Compatibility Mode + Run as Administrator + Change all Users" makes sense (I wasn't aware of this option but I assume it works). It is not really a fix but a good work around.
Your link somewhat describes the problem. When you select 'Run As Administrator' you are now running this program as someone else (a local admin account). This account does not have permission to access the network drives therefore it is blocked from doing so. The compatibility version of 'Run as Administrator' sounds like it does it the way it did back in the XP days where you are seen as the same user with more rights (?). The new version means you are seen as someone else and not a user with elevated privilege.
I agree with your last comment in this thread; it should not be necessary to run PC-DMIS as an administrator. If Hexagon is recommending this by default they should put together some information they can send to the users and only suggest the 'Run as Administrator' option as a last resort (in cases where it must be done this way - like with legacy Datapage).
If security is a concern (it is in most places) then no software should be allowed that must run with elevated permissions and access to the network. Stand-alone or isolated is fine. Blocked access to shared network drives is actually a good thing in this case.
