Installs Fine but Can't Login....

Try the default admin account in case it didn't get overwritten for whatever reason: admin@logicbase.com/admin

Yeah I've tried that. No luck.

Not a common error then? The strange thing is it announces the user/pass but doesn't work... even copy paste..

You can unlock the user in the DB my 'UPDATE [USER] SET IsLocked = NULL'... did the user you add have AD turned on? If so you might have to tack on the domain\ to the front,

It's only currently using Native login as I couldn't set the install settings to use AD even though all connections are fine and the user was domain admin... So native login..

I'm not the best with SQL so not sure how I'm supposed to unlock the user. Am I running that as a query?

Yes, the SQL to unlock the user would be:

UPDATE [USER] SET IsLocked = NULL

run aginst the Ensemble Db on the box where the DB is located (or whatever database name was specified)

What you can also attempt is to open the web.config of the \ProcessManager virtual directory on the SD box and look for admin user info in there (I believe some may be in there)

Thanks for the help, but that query doesn't unlock the account. It gives me the line;
(2 row(s) affected)
but nothing actually happened. Still locked out. 

Also, I looked through the config file you said about and found the line which I can change that relates to the user. I've changed & saved, and tried again to no avail...

This is really shoddy and I would really like to upgrade soon. Please help.

My mistake.. It did unlock the account but I still cannot gain access.. Is there a way I can force a new password in. Or would this be due to permissions on folders somewhere??!?

I'm researching this amond the other posts. In the meantime, please restore the changes you made to the web.config file (hopefully there is a backup... I think there actually is a web.config copy that gets delievered in the build, but unsure).

Yes. I always backup before I make changes to files like that. You are welcome to a remote session if you think there is more you could find out from one. Just remember if you do want a look I'm in the UK so there may be a massive time difference.

AdrianC,

I am experience the same issue with my ServiceDesk install. Did you get a resolution?

No resolution. I've tried completely uninstalling the SQL server and All altiris products and starting again but got exactly the same result. I'm wondering if I should re-build the server as I would like to see this software properly.

To be honest I'm surprised there has been as little help as this. Not that I'm knocking the responses given, just that I thought Symantec would want to support there own freshly released product a bit more. No light has been shed to why this is happening.

lwilliams02 - I would like to ask though... Did you try linking login to Active Directory and fail.. I had the problem of not being able to authenticate although everything was entered correctly. I had to use Native login only.. Just wondering if that is linked your end too..??

Ok.. I've resolved this issue myself. Here's what I done.

• I uninstalled all Altiris Components via Add/Remove and removed all Altiris directories from Program Files & Program Files x86.
• Wipe the servicedesk database from existence
• I installed CCleaner Slim (Found Here) and cleaned computer crap files. I also cleaned registry (with full backups registry changes).
• Reboot the machine
• After reboot I checked my login account (Domain Admin) was in the local administrator group. It was but worth the check.
• I installed again. This time when I got to login details I left all default (admin@logicbase.com) settings in and left as native install.. I did try AD but it wouldn't connect so Native it is.. Hopefully I can change this later.
• I completed the first part of the installation. When I got to the second setup part, I selected Full Install.
• Completed second part.. BUT before attempting to login to (http://servername/ProcessManager) I clicked on the bottom link to migrate incidents.
• While the incidents were migrating I attempted to login to the main part (http://servername/ProcessManager) and it let me in.. Bear in mind the User account was default (Username: admin@logicbase.com - Password: admin).

I am about to change the password and see if I can setup AD logins as thats what I require for our setup. If that fails I'll be back to figure it out myself again.. Poor humour?!?!?

Still doesn't explain what I've done wrong or where the issue is with the setting up of the software. Hopefully dev's will know and will fix it so other users don't hit the same Concrete wall I did.

But after this. A reboot and attempt to change password has locked me out again. Nightmare

AdrianC - I have tried native and AD authenication neither worked.

Well.. This problem is severely starting to wind me up. Anyone willing to help as it'd seriously appreciated. Thinking I should've not bothered to waste so much time and done a complete server rebuild which TBH seems like overkill but probably my only option..

Anyway, I've logged in with Default credentials and immediately changed the admin password. Logged out then in with the new password.. I have finally got an error.. Something that's probably helpful to one of you guys. I'd appreciate if someone could help decode it for me.

Error is as follows;

Process Manager Error
Message:  Verify Session ID failed  
Log:  at LogicBase.Ensemble.Userman.Userman.GetUserInfoByEmail(String sessionID, String userEmail) at LogicBase.Ensemble.Permissions.PermissionHelper.GetReferenceID(PermissionType permType, String referenceName) at LogicBase.Ensemble.Portal.ServiceCore.UserPersonalization.GetUserPersonalization(String PageID, String UserName) at LogicBase.Ensemble.Portal.ServiceCore.PersonalizationProvider.LoadPersonalizationBlobs(WebPartManager webPartManager, String path, String userName, Byte[]& sharedDataBlob, Byte[]& userDataBlob) at System.Web.UI.WebControls.WebParts.PersonalizationProvider.LoadPersonalizationState(WebPartManager webPartManager, Boolean ignoreCurrentUser) at System.Web.UI.WebControls.WebParts.WebPartPersonalization.Load() at System.Web.UI.WebControls.WebParts.WebPartPersonalization.LoadInternal() at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Symantec Logic is from where?? I have no idea..

When Setting up Process Manager Authentication and it asks for a pre-windows 2000 server domain when adding a AD server it's actually asking for your AD servers... that sorted out the ability to add the servers to this list. Even the manual says something completely different.

Still I'm hoping to god this doesn't still give me the same errors I had before, as I've rebuilt the server from scratch... Just hope this helps out someone else so they don't have the same sh*t I did.