M
mroberts@rev.com.au
Guest
Hi Marko, We ran 11.6, and are now running 11.7.1 (both 64 bit) I have been through the same migration and experienced the same sort of issues with the documentation. As for the shared memory connection we are not having the same issue. We have 2 dev environments running PASOE, one shared one on a Windows Server 2012 R2, as well I am running one on my laptop running Windows 10. For the shared one, the Admin Server and PASOE are running both from services, as a Local System account. For my laptop, I run both the proserve for the database and the pasoe start from proenv, running both as my login account. Both of these work shared memory. My guess based on the issue you linked, is that maybe the PASOE and DB server might be running partially as a service, and partially as the local user, and windows security is getting in the way. We have experienced the same symptoms using OE10.2B on customer's servers, where the Admin Server is started as a system account,. and we connect via a user account that does not have any local admin privileges. We either get the user changed to have local admin privileges, which sometimes solves the problem, or where the local IT person doesn't come to the party, then we revert to TCP connections. Hope this helps. Mark.
Continue reading...
Continue reading...