Dear All
I have one pro , 2 engineer, 14 ows, one HIST
ows 1, ows 7, ows 13 do not open control studio giving error Access denied as shown in photo
Note that these stations also could not access online database when using 'DVoperate in configuration mode:
provided that :
1- service password is correct and confirmed
2- when run deltav workstation configuration program it fails to complete and the only way to rerun the OWS is using regall /register command
NOTE : : SECOND PHOTO IS WHAT I GOT AFTER RUNNING DVWORKSTATION CONFIGURATION UTILITY
SO PLEASE ADVISE
THANKS
Andre Dicaire
In reply to Andre Dicaire:
Thanks for your response. Kindly find what I did as follows
1- I know Deltav admin password
2- on one of the working good machines I changed the pwd using servpwd.exe to change the password and rebooted but still control studio is working fine so the issue is not only pwd
3- on the pro I used servpwd.exe to confirm that I have the right pwd
4- on one mal function ows I used servpwd to change the pwd using the one I know for pro then rebooted but still control studio gives access denied
5- according to help I need to register services after changing pwd so I use regall /register , it works fine till the last point then it askes for Deltav admin PWD
and it stops until I put the right pwd.
6- after all still same problem
Thanks
In reply to hagouda:
In reply to Neil Castro:
Dear All Unfortunately I have tried all solutions followup all your recommendations/ steps still getting same issue moreover I compared services between one malfunctioning machine and other working well both have same service status. Firewall and windows defender are disabled in both machines
I am using Emerson smart switches and unmanaged
Network is OK all other machines are working well and these machines works well with Deltav operators run mode getting live data, alarm,..faceplate, open close valves....
Thanks for your response Hossam
Dear Neil Actually I tried to open control studio from windows start menu , from faceplate same results Access Denied Does this mean that the problem is in the application it self or the application connects at startup with proplus to test license? As on other machines with operator license control studio says during opening that "due to license for this machine control studio will open in view only." Then it opens The above behaviour is on all working OWS
≈============≈=
***just a question, Does control studio connects by default to online database/Pro plus during lunching ? Or just check the license on the local machine?
If so and you know these local files . Can these files be copied from other machine.
or can we unassigned the license then reassign again and download?
If so pls share procedure for doing this
Dear Neil
Kindly note that I have tried all your suggestions and still same issue DVCS don't open giving ACCESS DENIED without any errors generated on eventvwr for windows
Also note I have error also when using Dv operate in configuration mode it can not access online DB
also i noted today. That when try to regall /register it works till the end then it asks for DV admin service PWD I input it then it askes for reboot with oit any results
i confirm that this is fhe only pwd used all over the system
I double checked with the guy who installed the system and today I tried on another WORKING OWS
If you enter any other pwd the system stops refund the wrong pwd and won't complete until entering the right pwd
Thanks for your Time and support
Hossam
When Control Studio is launched from the start menu, it makes a connection to the database, even if no module is defined.
Below is a connection with user <none> when I launch Control Studio from the Windows Menu and I have not logged into DeltaV.
Below shows my Control Studio Session when I have logged onto DeltaV with account "AD".
What this tells us is that your current Windows User credentials are used to open Control Studio on the workstation. That is, the Windows Login user must have windows access to the Control Studio (CS.EXE) program. This user must be granted DeltaV access rights to the DeltaV folders, which is done by creating the user through DeltaV User Manager and selecting that a Windows user be created with the same NAME as the DeltaV User.
Troubleshooting through an open forum is always going to be a slow and painful process as we offer suggestions that don't pan out because we don't know what you don't tell us. And telling an open forum about your user security and computer node names is a security risk. So be careful what you share.
At this point, it sounds like a windows security issue, since launching Control Studio does not require a DeltaV logon, just the windows logon, which grants you file access on that computer. When Control Studio launches, it connects to the database and passes the DeltaV user to the database, which determines your DeltaV Privileges such as Can Configure and other database access keys. With out those keys, Control Studio will be in View Only mode.
You can logon to a DeltaV workstation with any windows account that Windows recognizes, including local accounts and Domain Accounts. If the Account is not in the DeltaV group, then launching any DeltaV program will have an Access Denied message. When you create the DeltaV user, you have a choice to link it to a specific version of the user: A Local account, a Domain Account, or any user with that name. The computer may recognize a local or domain user and authenticate it. But if it does not belong to the DeltaV group on that workstation, you can't launch programs.
So start by checking that the user is a valid DeltaV account by confirming how it is configured (Local/Domain) and that it is in the requisite security group.
That other possibility is that the DeltaV programs have had their security altered such that they do not allow DeltaV users to access them, that is, the DeltaV group has been removed from the program's access group.
If you cannot identify any issue relating to user security or program access rights, I recommend you Uninstall DeltaV and all other programs. Reboot and start over with a clean DeltaV install, ensuring you properly join the Domain. That would include Mcaffee and any other programs, support or not. This is the "I give up " strategy and will not identify the root problem, but it should restore all user and program rights and resolve the issue.
I still strongly recommend you log a call with the GSC so that you can discuss sensitive user security settings with a limited audience.
Dear Andre
Thanks for following up. Kindly not that Unfortunately my GSC was expired