WSS 3.0 Central Admin Screen

The screens below are the Windows SharePoint Services 3.0

 

How to Enable Sign in as Different User Option in SharePoint 2013

Problem

By default in SharePoint 2013 there is no option for "Sign in as different user".

Use the following procedure to enable this in SharePoint 2013.

Solutions

Step 1

Go to the location:
C:\Program Files\Common Files\microsoft shared\Web ServerExtensions\15\TEMPLATE\CONTROLTEMPLATES
Here we have a file named "welcome.ascx".
We need to edit this file to enable the option.

Step 2

Open the welcome.ascx file in Visual Studio or in Notepad and add the following code

<SharePoint:MenuItemTemplate runat="server" ID="ID_LoginAsDifferentUser"  Text="<%$Resources:wss,personalactions_loginasdifferentuser%>"  Description="<%$Resources:wss,personalactions_loginasdifferentuserdescription%>"  MenuGroupId="100"  Sequence="100"  UseShortId="true"  />

before the content SharePoint:MenuItemTemplate runat="server" ID="ID_RequestAccess"

and save it:

 
Step 3

Refresh the site and then "Sign in as different user" will be enabled.

How to Enable Sign in as Different User Option in SharePoint 2013

Problem

By default in SharePoint 2013 there is no option for "Sign in as different user".

Use the following procedure to enable this in SharePoint 2013.

Solutions

Step 1

Go to the location:
C:\Program Files\Common Files\microsoft shared\Web ServerExtensions\15\TEMPLATE\CONTROLTEMPLATES
Here we have a file named "welcome.ascx".
We need to edit this file to enable the option.

Step 2

Open the welcome.ascx file in Visual Studio or in Notepad and add the following code

<SharePoint:MenuItemTemplate runat="server" ID="ID_LoginAsDifferentUser"  Text="<%$Resources:wss,personalactions_loginasdifferentuser%>"  Description="<%$Resources:wss,personalactions_loginasdifferentuserdescription%>"  MenuGroupId="100"  Sequence="100"  UseShortId="true"  />

before the content SharePoint:MenuItemTemplate runat="server" ID="ID_RequestAccess"

and save it:

 
Step 3

Refresh the site and then "Sign in as different user" will be enabled.

This certificate cannot be verified up to a trusted certification authority.

Problem 1

When I access the remote server via SSL VPN , you see the following error message:

This certificate cannot be verified up to a trusted certification authority.

or

This CA Root certificate is not trusted. TO enable trust,install this certificate in the Trusted Root Certification Authorities store. 

Cause

This issue is caused by the Certificate Authority not being visible to the browser.

Solution

Do the following on the Certificate Server

1. Open MMC, click Start, Run, type MMC, and press ENTER.
2. Add the Certificates snap-in using the Computer Account.
   
   1. Click File, select Add/Remove Snap-In.
      You see the Add/remove snap-in window.
   2. Click Add.
      You see the Add Standalone snap-in window.
   3. Select Certificates and click Add.
   4. Select Computer Account and click Next.
   5. Select Local Computer (selected by default) and click Finish.
   6. Click Close.
      You now have a single snap-in called Certificates (Local Computer) in the snap-ins added section of the Add/remove snap-in window.
   7. Click Ok to close the Add/remove snap-in window and to return to the MMC.
3. Perform the following in the MMC window.
   1. Expand Certificates.
   2. Expand Trusted Root Certification Authority.
   3. Right-click the correct Root Certification Authority (you may need to select the certificates folder to view the list in the right hand window panel).
   4. Click Export, which opens the wizard. Select the following in the wizard: 
      1. Select Cryptographic Message Syntax Standard - PKCS #7 Certificates (.P7B).
      2. Select Include all certificates in the certification path if possible. 
      3. Click Next.
      4. Assign a relevant file name.
      5. Click Next, Finish.
         This will create .p7b. 
   5. Copy .p7b to the client used to access the site.
4. Install the certificate on the client using one of the following methods.

        

• Method 1 - Right-click on the certificate file
  1. Right-click .p7b.
  2. Click Install Certificate.
  3. Click Next, Place all certificates in the following store.
  4. Click Browse.
  5. Select Trusted Root Certification Authorities.
  6. Click Ok, Next, Finish.
      
• Method 2 -  Import using Microsoft Internet Explorer
  1. Open Internet Explorer. 
  2. Select Tools, Internet Options.
  3. Click the Content tab.
  4. Click Certificates.
  5. Select the Trusted Root Certification Authorities tab.
  6. Click Import.
  7. Browse to the .p7b file and place it in Trusted Root Certification Authorities.
  8. Click Next, then click Finish.

How can I add to the hosts file?

 Open the below location in the Windows folder

c:\windows\system32\drivers\etc

Open the Host file and do amendments

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host
# localhost name resolution is handled within DNS itself.
# 127.0.0.1       localhost
# ::1             localhost

you would like to add say

x.x.x.x website.xyz

SSRS Report Server was unable to process request(Sharepoint integrated mode)

An unexpected error occured while connecting to the report server. Verify that the report server is available and configured for Sharepoint integrated mode. --> Server was unable to process request. ---> Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.

Solution:

Check the Report Server websites has started in the IIS.
Restart the SP timer services and SSRS report services.
Check the SQL log files and account could access the SSRS reports.

SharePoint Designer workflows never reflects the new changes

I've ran into this scenario a lot it seems. I'm not sure if it's an issue with SharePoint Designer, or SharePoint itself, but the following seems to occur often:   I create a Workflow in SharePoint Designer, and when I save it, it's good to go, and works as expected. However, when opening it later for edits in SPD, I can make changes to the workflow, very large ones, and save it, and on the SharePoint site, it shows as a new version of this workflow, but never reflects the new changes I made to it.     For instance, I created a simple one to test, simply an email gets sent to me when a new item is created in a list. Works fine. However, when I add an item lookup in the body of the email, save the workflow again, and create a new item in my list, I still get a blank email, not the new item lookup in the body of the email as expected. Is there some kind of timer with SharePoint updating workflows? Am I missing something here?   SOLUTION:   For SharePoint Designer, the solution is similar to Dave's solution. It seems SharePoint Designer saves local copies of DLLs from your servers, and although everything seems OK, this prevents it from updating the workflow (this is when custom activities are involved, which the question didn't mention).   To solve this issue for MOSS 2007: Close SharePoint Designer Go to %LOCALAPPDATA%\Microsoft\WebsiteCache Or, on older versions of windows: C:\Documents and Settings\%USER%\Local Settings\Application Data\Microsoft\WebSiteCache Delete either (choose one, based on how annoyed you are by now): All folders. The folder that "looks most like your site" (can be more than one: site, site(1), etc, and should be the bottom level site, not the root site) The relevant DLL in that folder. Start SharePoint Designer, save the workflow again, it should be ok. To solve this issue for SharePoint 2013 or 2010: Go to the folder and delete the files and folders C:\Users\LOginUse\AppData\Roaming\Microsoft\Web Server Extensions\Cache C:\Users\LOginUse\AppData\Local\Microsoft\WebsiteCache Before that take backup  and delete it, some sites ask to delete the files and folders in the below location, Don't try to delete, Because after deleting the files the existing workflows never open C:\Users\LOginUser\AppData\Roaming\Microsoft\SharePointDesigner\ProxyAssemblyCache