Disable default language selection control in MOSS

Product Apply : Microsoft Sharepoint Server 2007
Not for WSS 3.0 

Below are the steps that how I disabled the default language selection control in my site.

1. Open the folder “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\CONTROLTEMPLATES”
2. Open “VariationsLabelMenu.ascx” file.
3. Comment this line “<%–” IsCallbackMode=”true” runat=”server” />–%>”
4. Save changes and close the page.
5. Restart your IIS.
6. Default language selection control will be gone away.

*****AS IS*****

Exchange OWA not working

Ok, I was having a problem with some .net side by side errors so i uninstalled and reinstalled 2.0,3.0 and 3.5 .net framework. Now OWA will not show the login page. HTTPS://mail.provmedgroup.com/owa . Please help me.

My Suggestion : - 

You may need to rebuild the OWA , Run this command in the Exchange Management shell:
 Get-OwaVirtualDirectory |fl >Owavdir.txt
This provides an output file that can be used as a reference when you re-create the OWA virtual directories For Exchange Server 2007
Run EM Shell , Deletion of OWA Virtual dir:
    Remove-OwaVirtualDirectory

"exchange (default web site)"
    Remove-OwaVirtualDirectory "public (default web site)"
    Remove-OwaVirtualDirectory "exchweb (default web site)"
    Remove-OwaVirtualDirectory "owa (default web site)"
Recreation:
New-OwaVirtualDirectory "exchange" -OwaVersion Exchange2003or2000 -VirtualDirectoryType Mailboxes -WebSiteName "Default Web Site"
New-OwaVirtualDirectory "public" -OwaVersion Exchange2003or2000 -VirtualDirectoryType PublicFolders -WebSiteName "Default Web Site"
New-OwaVirtualDirectory "exchweb" -OwaVersion Exchange2003or2000 -VirtualDirectoryType Exchweb -WebSiteName "Default Web Site"
New-OwaVirtualDirectory -name "owa" -OwaVersion Exchange2007 -WebSiteName "Default Web Site" –InternalURL https://internalURL/owa -ExternalURL https://externalURL/owa

Incase you are different version of Microsoft Exchange then please see http://support.microsoft.com/kb/941201/en-us

IIS6 - App Switched from 2.0 to 4.0 Web Service Issue - Service Unavailable

Hello all,

I created a new app pool and the 4.0 framework is set to allowed.  The site I have works fine but when I get the ASMX web service I get a Service Unavailable error.  I looked at the web service folder and that folder the ASPNET tab is greyed out showing 2.0 framework but all the other folders show the 4.0 framework under the ASPNET tab.  What do I need to do to get this to work for the web service?
Asked by: sbornstein2 

My Suggestion : -
1) Run this command from the path
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319>aspnet_regiis -lk
And see if the website identity is showing in this list ..
2) Please verify if .Net is allowed under web services extensions
3) Please verify if Network Services have access to the root directory of the application.

sbornstein2 : -  couple of things:

- In IIS6, how do you set the App Pool to a framework?  I could not see that option only the tab under the virtual directory properties itself and yes I changed that to the 4.0 framework.   Like I mentioned though all the subdirectories are showing 4.0 but the web service directory is still showing 2.0 and greyed out.

- .Net 4.0 is allowed under the web extensions in IIS.

- Network Services does have access to the root.  If I switch the ASPNET tab back to 2.0 the web service ASMX when I browse to it does come up, however when I switch it back to 4.0 then I get the Service Unavailable.  I am pretty sure it is because the web service folder is showing 2.0 greyed out and 4.0 for the rest of the site.    In the event log it shows:

"It is not possible to run two different versions of ASP.NET in the same IIS process. Please use the IIS Administration Tool to reconfigure your server to run the application in a separate process."

However, I created a brand new App Pool just devoted to this virtual so no other processes should be using this app pool.

My Suggestion : -
On CMD, go to C:\WINDOWS\Microsoft.NET\F
ramework\v4.0.30319
Run >> aspnet_regiis -s (site path)
You can run " aspnet_regiis -lk " command to know the website path...

**Given solution are only for my record purpose, Please use them on your own risk.

Static and Dynamic Compression in IIS7

Question: We are running Windows 2008 Enterprise 32-bit on vmware using IIS 7. We have installed Static Content Compression but not Dynamic Content Compression.

First we can't find were to see the min and max settings for (Only compress files larger than (in bytes)) Also which settings would you recommend? (Google says, they recommend a minimum range between 150 and 1000 bytes) is this a good range?

 Second it seems to be working except it won't compress .js files. (According to https://developers.google.com/pagespeed/) Can these be added?

Third is it neccery to install Dynamic Content Compression or is Static Content Compression enough?
Thanks

My Reply :  Well Dynamic content compression is a feature which you could try to use but in corporate env, you should not use it because it delay the site reply on user end, because dynamic content takes time to unfold at user end and that could cause slowness on a busy env.

To implement compression:
Go to IIS -> Site level -> In feature view -> Compression -> Select "Enable dynamic content compression" and Apply

MinFileSizeForComp - Min 256 kbytes
CacheControlHeader  value -> max-age=86400 (To enable this setting, you must set the SendCacheHeaders property to true. )

probably it may help you

by: CityInfoSys Posted on 2012-02-02 at 10:20:07

Would it be OK to add this to applicationHost.config to work globally instead of web.config for each web server?

My reply 
The code should be :

   
     
            
--OR --
      
     
   

These both elements are defining client Cache and using Max-Age we are specifying the time lime limit but with "UseMaxage" , we are leaving it to remain there .. You may select one of them as per your requirement .

How to Clear the SharePoint Configuration Cache

Sharepoint 2007 : How to Clear the SharePoint Configuration Cache

The config cache is where the cache config information (stored in the config database) on each server in the farm.In order to delete that we need to delete it from all Moss servers in Farm.

To clear the config cache on the farm, follow these steps:

• Stop the OWSTIMER service on ALL of the MOSS servers in the farm. 
• On the Index server, navigate to:  

Server 2003 location: Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\GUID and delete all the XML files from the directory. 
Server 2008 location: Drive:\ProgramData\Microsoft\SharePoint\Config\GUID and delete all the XML files from the directory.

• Delete all the XML file in the directory. NOTE: Delete only XML files, and not the .ini files.
• Open the cache.ini with Notepad and reset the number to 1. Save and close the file.
• Start the OWSTIMER service on the Index server and wait for XML files to begin to reappear in the directory.
• After you see XML files appearing on the Index server, repeat steps 2, 3 & 4 on each query server, waiting for XML files to appear before moving to subsequent servers.
• After all of the query servers have all been cleared and new .xml files have been generated, proceed to the WFE and Application servers in the farm, following steps 2, 3, 4 and 5 for each remaining server.

You are done. All the steps mentioned above mentioned for my personal use, Please use on your own risk.