ServiceDesk

Trying to install ServiceDesk 7.1 and it's failing on the ASP.NET check.  The install.log gives this:

ServiceDesk Setup started at 3/25/2011 2:41:41 PM
License Agreement..
Checking Server Extensions service running
Checking Server Extensions service running
Maintenance..
Server Roles..
IIS Restart Confirmation..
Install Location..
Server Configuration..
Install Location..
Server Configuration..
Workflow Designer Tasks..
SMP Server Credentials..
Connection failed to SMP server domain\NS using URL: http://NS/altiris/Workflow/Licensing.asmx
The remote server returned an error: (401) Unauthorized.
Connection failed to SMP server domain\NS using URL: http://NS/altiris/ns/services/systeminformationwebservice.asmx
The remote server returned an error: (401) Unauthorized.
Connection failed to SMP server domain\NS using URL: http://NS/altiris/servicedesk/licensing.asmx
The remote server returned an error: (401) Unauthorized.
Database Connection..
Saving database page..
Database Configuration..
Getting current database version..
Error getting current database version: Cannot open database "ProcessManager" requested by the login. The login failed.
Login failed for user 'DOMAIN\Admin'.
Error getting current database version: Cannot open database "ProcessManager" requested by the login. The login failed.
Login failed for user 'DOMAIN\Admin'.
Database Replication..
Checking if replication database exists..
Saving replication page..
Advanced Cube Reporting..
System Accounts Access..
Skip if MS SQL Server Security selected
Process Manager Configuration..
Getting current Process Manager configuration..
Failed to fetch UserWelcome setting: Cannot open database "ProcessManager" requested by the login. The login failed.
Login failed for user 'NORPRO\svcaltiris'.
Process Manager Authentication..
Getting current authentication..
Unable to get current authentication mode: Cannot open database "ProcessManager" requested by the login. The login failed.
Login failed for user 'NORPRO\svcaltiris'.
Failed to fetch ActiveDirectoryServer table: Cannot open database "ProcessManager" requested by the login. The login failed.
Login failed for user 'DOMAIN\Admin'.
Failed to fetch administrator user: Cannot open database "ProcessManager" requested by the login. The login failed.
Login failed for user 'DOMAIN\Admin'.
Saving authentication page..
Workflow Persistence..
SymQ ORM..
System Check..
System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it XX.XX.XX.XX:443
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetResponse()
   at Symantec.Workflow.Installer.Core.ASPNetDetection.IsHttpsAllowed(String serverName, String virDirName, String physicalPath, String& message)
Connection to database succeeded at (local)

Has anyone seen this issue?

Hello,

Here is some advice for installing:

When building SD Server:

Make sure you are logged into box as an Admin User that has sysadmin rights on SQL 2008 Server, this is NOT the service account you’ll use later.

Install Application Server and Web Server roles, making sure to install IIS 6 compatibility features

Patch OS, but don’t install SP1

Install the 3 SQL components from the SQL 2005 December 2008 Feature Pack (just like for MR2). Please refer to this article for the prereqs:

How to Install and run ServiceDesk 7.0 MR2 with a domain account instead of a local system account
http://www.symantec.com/business/support/index?page=content&id=HOWTO31346 

Set DefaultAppPool to run as Identity account – this is service account just like MR2.  Running the aspnet_regiis –ga isn’t needed.

Run SD installation.

During installation on Service Accounts page; uncheck all the default items here and add your Service Account

Do NOT attempt to setup AD Authentication during install, the installation attempts to set this up prior to the Service Account being granted DB access and it fails as a result.  At least that’s my guess. 

Do NOT change the virtual directory from ProcessManager, changing will result in a failure during PostInstallWizard when setting permissions.  This appears to be related to something hardcoded to look for the default virtual directory. 

I hope that helps!

Thank you,

Randall Newnham

Thanks.   I fixed this early this morning.  I ended up removing all roles from the server and reinstalling the one's needed for ServiceDesk.