Hello, i am having an issue with a TCS that shipped running version S5.3 from the factory. i can RDP into the Windows OS no problem and access the OS management web page over port 8098 no problem, but if i try to login to the application web interface i get a username/password error. any ides on what is causing the issue? the server was working fine until after a reboot. thanks!
Jarrod - Can you be more specific as to the configuration of your TCS (attached to a domain, groups, or using local TCS accounts, etc) and the exact error or symptoms it is doing when you're trying to login?
Did you try to do a repair install via Control Panel > Add/Remove Programs? In the past when I've had login issues, that fixed most of them, as it was usually something to do with the TCS application on the server.
This will use the local authentication, since if you changed to domain or ldap without adding a domain/ldap user to the siteadmin before logging in with it you will basically block your self out since you are no longer authenticating locally to the box.
This is one way to go, but Patricks's answer is also valid if you did not make any changes to the authentication.
I should also note, that in the past with our authentication errors, as a result of something unknown the TCS application had stopped working in a way. Either the authentication settings in IIS or the database, something to that extent which resulted in an error message when simply trying to view the TCS website or when trying to login it would just keep going in a loop such a way that when you login, it would just pop back up the login prompt.
So without really knowing any specfic details of what you are seeing or the symptoms of what is happening when you try to login, it's really hard to say what to try or do to fix it. Authentication errors could be a number of things, as mentioned in my first post.
Mangus - I don't want to go off on another conversation here, but it might be beneficial. What exactly does that login method you provide do?
OK so Mahesh had the solution, allthough i am confident that rebuilding the server would have worked too
the issue was when i tried to get LDAP connected, which was unsuccessful, i didnt change it back to local auth mode. either way IMO this is serious flaw with the product as the local administrator account should always have access (just like with VCS) and you shouldnt be allowed to save the config in LDAP auth, if it can't successfully connect to the LDAP server. that way the sever is more idiot proofed for guys like me
This is documented in the documentation. That is also this url in case this will happen. The documentation also tells you to create a user when changing to ldap. If the url was the solution this was provided in my first post if you look upwards in the thread:) i'm glad it helped you.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.