ServiceDesk

 View Only

How to Reinstall DOT Net Framework After ServiceDesk is Installed 

Mar 01, 2011 11:58 AM

Installing or reinstalling DOT Net framework after serviceDesk is installed. Hopefully you wouldn't have to do this. But in case you have to do it, here's a helpful guide.

  1. This is not a recommended that you install or upgrade .Net after ServiceDesk is installed. But if you have to do it, here's how.
  2. Uninstall the current version of .net framework
  3. Reboot the server
  4. Login with the account that you used to install ServiceDesk. Follow the following link to check if you're using the correct account for this purpose. http://www.symantec.com/business/support/index?page=content&id=HOWTO30389
  5. Install the .Net 3.5 preferably Sp1 if you have ServiceDesk 7.0 MR2.
  6. Run the script below. The Domain User name that'll be used in the script is the Service account that is used to run ServiceDesk. If you want to double-check what that account is, go to Start > Run and type in 'Services.msc' without the quotes and hit Enter. Scroll down to the service called 'Logicbase 2006 Server  Extensions' and double-click on it. Click on the 'Log on' tab.

 

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -ga [domain]\[domainuser]

 

  1. In IIS, "Web Service Extensions", Set ASP.NET v2.50727 to "Allowed"
  2. Now restart the server and restart logicbase servicer extension.
  3. If you try to open the servicedesk portal, you will most likely get a blank page with IIS error 403. That means that the default document content wasn't set. You will need to do that for each project. There are a few different ways to set the default document content. The best and most effective way is to edit the Metabase.xml file. Here's how you do that
    1. Go to C:\WINDOWS\system32\inetsrv
    2. Backup the metabase.xml file
    3. Edit the file in notepad
    4. Each DOT NET application published in IIS will have an entry that looks like this
 <IIsWebVirtualDir        Location ="/LM/W3SVC/1/ROOT/PM.ADMergeManagement"

AccessFlags="AccessRead | AccessScript"

AppFriendlyName=""

AppIsolated="1"

AppPackageID="{E561A285-D243-41F3-8E09-9FC22C8F0AA2}"

AppPackageName="IIS-{Default Web Site//ROOT/PM.ADMergeManagement}"

AppRoot="/LM/W3SVC/1/ROOT/PM.ADMergeManagement"

AppWamClsid="{4C5C9A66-29B4-4861-81ED-B76780C395D4}"

AspAllowSessionState="TRUE"

AspBufferingOn="TRUE"

AspScriptTimeout="900"

AspSessionTimeout="30"

ContentIndexed="FALSE"

DefaultDoc="Default.aspx"

DirBrowseFlags="DirBrowseShowDate | DirBrowseShowTime | DirBrowseShowSize | DirBrowseShowExtension | EnableDefaultDoc"

DontLog="TRUE"

Path="E:\Program Files (x86)\Altiris\Workflow Designer\WorkflowDeploy\Release\PM.ADMergeManagement" 
  1.  Add DefaultDoc="Default.aspx"as shown above, right below the line that says ContentIndexed="FALSE" .
  2. Do step 10 for all the applications that are published.

Hope this helps someone.

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Related Entries and Links

No Related Resource entered.