Try creating a new Windows admin user

 

Yep, IT even created a user within admin and we tried signing in... no luck

 

Every windows user cred is also good for getting into the platform.
Make a new user, and then try not to forget the creds this time.

 

If you have the creds to make a new admin...uh why bother?

 

We have tried new users, admin rights, and still no luck.

 

Odd ..... Can you log into the station (not the platform as they are different)? Have you verified the platform daemon is running?

 

Is the computer part of a domain? If so try typing domainname/user name.

 

or if it's a domain computer and the accounts you are creating are local to that computer use the local computer prefix period backslash .\username.

 

Would also check if this station is using the LDAP driver and win AD or some of the other auth drivers.

 

Or maybe you are attempting to connect with a nonencrypted connection (no padlock) when the system is configured only for an encrypted (padlock) connection.

 

You wouldn't get the logon prompt if that was the case.

 

True, but we left the usual and wandered into the unusual. Good to cover bases.

 

Hmmmmm, I think we are using LDAP. I will verify

 

Yes, LDAP /AD is used for platform access

 

After reading your responses on LDAP; I took a look at the errors and found "Warning [java.util.prefs] Could not open windows registry node Software\JavaSoft\Prefs at root 0x80000002. Windows RegOpenKey(...) returned error code 5"

 

Sounds like a date with IT then.

 

All, Thanks so much for your reply's. The issue remains and of course now there's a project that requires access. I am trying all the stuff you mentioned again and will get back to ya. We have a probability that a rouge contractor decided to prank us.

 

Would think you can kick the door in and reset things if it comes down to that.

 

My HON WEBs N4 was running fine the other month. Fired it up the other day and could not get the Platform to open (running WIN10). Went to 'Services' - found out that Niagara.exe was not running and 'disabled'. Switched to WIN Admin user - same issue. Hmm... Contacted Tridium to verify the license - license ok but they informed that it was recently re-issued.
T-Support diagnosis process:
1) 'Services': view Niagara.exe properties. Unable to modify the 'Start up Type' in WIN admin session - locked in 'Disabled'. "Hmm..." says T-Support.
2) Launch Console.exe (C:/Honeywell/WEBStation-N2-4.8.0.110/bin). Enter Command line text: "plat installdaemon". Message: "Access is denied; ERROR: daemonservice: cannot open service manager; ERROR: installdaemon: Niagara service could not be installed".
Tech support: "Hmm...you might have an IT issue".

T-Support instructs how to run Station without Platform running (call it 'running Station via a command line'?).
1) Launch N4 (must be running).
2) Double-click on "Workbench User Home" shortcut (C:/Honeywell/WEBStation-N2-4.8.0.110)
3) Open 'stations' folder. Find the name of the Station you want to launch.
4) Launch Console.exe (C:/Honeywell/WEBStation-N2-4.8.0.110/bin).
5) Command line: Station <station name>
The Station name does not require lower/upper case syntax, but if not exact you'll get a message: "Could not find an exact match for a given station name". The process retries and starts the Station on port 4911.
6) N4 Workbench: right-click local 'My Host xxx' > 'Open Station'
7) 'Open Station' dialog box appears (port 4911).
8) Enter Username/Pswd.
9) Station runs.

So I'm in N4 'limp-home' mode for awhile (in WIN local account). Few hours after piddling around in my Station I later log into an WIN admin account. Check the Properties of Niagara.exe - able to set the 'Start up Type' to Auto. Now able to launch Platform in either WIN Local or Admin session. Hmm...curious. One wonders what IT would do. Maybe IT is really "Illogical Trap".

 

This is the 1 in 10000 trick that make me the hero in an oddball scenario. Thanks for the writeup

 

I went through this for years. Our IT took away our local admin accounts. Kept telling them we had to have local admin account to authenticate with for platform access. Well you are not getting it, but we will make you a member of the administrator group. Would only work if in the office or sometimes on VPN or not at all most of the time. Had to use the console and start stations from Niagara user home with station.exe station name. What a PITA.

 

I forgot about this post. We figured this out early this year... yep 4 years of not knowing. Similar to what you mentioned about IT admin accounts, IT may call it admin but never really admin. Ours finally created a group that gives us the credentials we required for Platform access yet keeps us off of C: drive. Ever so often we need a little tuning to ensure we have access the assigned drive. Its getting better, even the IT department is ..... lol

 

After my HON WEBs N4 got mysteriously corrected I launched Console.exe. Executed the statement: plat installdaemon.
Admin login: "Niagara service successfully installed" (failed previously).
Local login: "Access is denied; ERROR: daemonservice: cannot open service manager" (like before).
Possibly is a good diagnostic test when N4/Platform is "waist high & upside down". Any comments welcomed.

During the T-Support session they had me go to my User Accounts (via Control Panel) and to view "Manage User Accounts". Not there - no such line statement. Only (3) items to select:
1) 'Change your account type'
2) (gap)
3) 'Manage another account'
4) 'Change User Account Control setting'

Same situation in either Local or Admin account. T-Support reply: "Hmm...maybe IT issue". Can anybody confirm this? Curious that there is a gap between lines #1 & #3.
I often joke with the DDC crew: "to keep a room warm or cool you got to be an IT guy" (!).

 

Microsoft ruined the control panel. Right click start menu and select manage. Users and groups are in there.

 

Contacted my recent Spyder instructor (Cochrane Tech Services) per the failing 'plat installdaemon' statement using Console.exe (in local account). Informed to put my 'local account' in the Administrator Group. Did that using "Computer Management" ('Local Users & Groups') - thanks for that tip. Did a reboot and voila it works - get the statement "Niagara service successfully installed." When you use 'Settings > Accounts' you'll find that the local account name now has 'Administration' status.
So now my 'local account' has administrator permissions. Red flag alert. I generally prefer to run WIN10 in the local account 'mode' and run N4 that way (note: the 'local account' is really a Microsoft Account (MSA) - link to an email address). Possibly N4 Platform is 'happier' with the local account with administrator permissions however now my 'local user' account can access anything on the system - any malware that is encountered can use the admin. permission to potentially infect or damage any files on the system. Thinking of removing the 'local account' out of the Administration group - N4 seems to run ok that way. Starting to get out the 'DDC swim lane' into the 'IT swim lane'. Also, comments on running in a true 'local account' (off-line) vs. running in MSA is appreciated.

 

Microsoft is well aware some people need to run as admin, this is why user account control exists. Look for that setting and crank the confirmation dialogs up to whatever level makes you comfortable.

Accounts you create in management, local users and groups are local only accounts. Make as many as you want. You can switch when doing certain things.

 

We've run a little loose over the years with an IT dept. We now have a guy. He sets up all the new laptops. There would be a severe mutiny on his hands if were weren't setup as admins. Not even a discussion where I work. No dollars waiting on dimes at this place.

 

It is important to mention that "administrator" by name or group is just another name, it's only the microsoft defaults that allow it to do what it can do. It can be restricted like any other account/group. It may take some digging in support but there is a list of expectations of what these apps and services MUST be allowed to do that is what these IT departments really need. I got it once for ALC long ago and it's pretty lengthy, I'm sure tridium has one somewhere. Within the apps they are also doing a little better at error messages, these days when I install WebCTRL and launch SiteBuilder make one change to the web server and receive a message "unable to save changes" what that really means is the app was launched with so little permission it can't even update a config file within it's own install folder.