Zephyr's SharePoint Blog

My Sharepoint world experience notes on day to day basis…..

Host Named Sitecollection or vanity URL

Posted by fillzephyr on September 10, 2008

 

Hey friends,

My client had a requirement of changing the regular URL name which is formed when you create a site collection http://vpc01:4444/sites/bluemoon123 to some good looking url name http://bluemoon123.corp.de for intranet purpose. This can be achieved by using host headed site collection or by giving vanity URL name. One more thing, this site collection should have its own content database WSS_Content_Bluemoon123 with the limit of 60 GB.

For specifying the particular QUOTA for your site collection you have to create a site quota template:

GO TO

Central Administration > Application Management > Sharepoint Site Management > Quota templates

In Template Name

Select Create a new quota template

In New Template Name give related name to your site collection quota here i had given name as bluemoon123.

In Storage Limit Values

(Tick both check boxes)

Limit storage to a maximum value of: 60000 MB

Send warning E-mail when site storage reaches: 50000 MB.

Click OK 

And here a site collection quota bluemoon123 of 60 GB is created. 

Now GO TO

Central Administration > Application Management > Sharepoint Web Application Management > Web Application General Settings

In Web Application select http:// vpc01:4444

In Default Quota Template select bluemoon123

Click OK.

IT CAN BE DONE IN TWO WAY:

First Method:

Creating Content Database for your site collection:

GO TO

Central Administration > Application Management > Sharepoint Web Application Management > Content Databases

In Manage Content Databases

Click Add a content database

In Web Application select http:// vpc01:4444

Database Name: WSS_Content_Bluemoon123

Click OK

This will create a content database WSS_Content_Bluemoon123 for web application http:// vpc01:4444. 

Creating a site collection using the following stsadm command.

C:\>”Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN”\stsadm -o createsite -url http://bluemoon123.corp.de  -ownerlogin VPC01\abcdef -owneremail abcdef@abcd.de -sitetemplate STS#0 -title BlueMoon –hhurl http://vpc01:4444 

(For particular site template see below)

When Operation completed successfully on command window you can verify it by navigating in your central administration site through these path

Central Administration > Application Management > Sharepoint Site Management > Site collection list

Select web application http://vpc01:4444 here you will find the site collection which is created using STSADM tool. 

 

Now go to

Central Administration > Application Management > Sharepoint Web Application Management > Content Databases

In Manage Content Databases select Bluemoon123 and in Database Capacity settings put these values 

Number of sites before a warning event is generated: 1

Maximum number of sites that can be created in this database: 2

Click Ok  

So now any new site collection created on this web application is not specifying this content database and this database is now only related to site http://bluemoon123.corp.de.

 

Second Method:  

Creating Site collection with Content database using stsadm command 

C:\>”Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN”\stsadm -o createsiteinnewdb -url http://bluemoon123.corp.de -ownerlogin VPC01\abcdef -owneremail abcdef@abcd.de -sitetemplate STS#0 -title Bluemoon -hostheaderwebapplicationurl http://vpc01:4444 -quota Bluemoon123 -databaseserver vpc01 –databasename WSS_Content_bluemoon123. 

This will create a site collection http://bluemoon123.corp.de on content database WSS_Content_bluemoon123 with quota of 60GB. 

Now u have to follow these step 

Central Administration > Application Management > Sharepoint Web Application Management > Content Databases

In Manage Content Databases select WSS_Content_bluemoon123 and in Database Capacity settings put these values 

Number of sites before a warning event is generated: 1

Maximum number of sites that can be created in this database: 2

Click Ok 

So now any new site collection created on this web application is not specifying this content database and this database is related to site collection http://bluemoon123.corp.de.

If you do not have any access to the network side then ask your network administration team to create DNS Entry for your site collection otherwise it will show you the DNS Error. They will assign an ip address for this site collection. OR else

 

If you are running on your dev enviornment go to

C:\WINDOWS\system32\drivers\etc hosts.

Open hosts and write ip address and host header and save it.

 

After they assign IP address you have to configure your site collection in IIS Manager.

GO TO

Websites>web application 4444> right click   go to properties Select website tab nearby ip address there is Advanced… button click on it. 

Click Add…

In TCP Port enter 80.

In Host Header value enter bluemoon123.corp.de

Click OK. Ok. Ok.

Type the URL in browser http://bluemoon123.corp.de. Team site site collection is created. Because we had use site template as sts#0.

 

If you want to use different templates you can use this following name: 

GLOBAL#0 = Global template

STS#0 = Team Site

STS#1 = Blank Site

STS#2 = Document Workspace

MPS#0 = Basic Meeting Workspace

MPS#1 = Blank Meeting Workspace

MPS#2 = Decision Meeting Workspace

MPS#3 = Social Meeting Workspace

MPS#4 = Multipage Meeting Workspace

CENTRALADMIN#0 = Central Admin Site

WIKI#0 = Wiki Site

BLOG#0 = Blog

BDR#0 = Document Center

OFFILE#0 = Records Center

OFFILE#1 = Records Center

OSRV#0 = Shared Services Administration Site

SPS#0 = SharePoint Portal Server Site

SPSPERS#0 = SharePoint Portal Server Personal Space

SPSMSITE#0 = Personalization Site

SPSTOC#0 = Contents area Template

SPSTOPIC#0 = Topic area template

SPSNEWS#0 = News Site

CMSPUBLISHING#0 = Publishing Site

BLANKINTERNET#0 = Publishing Site

BLANKINTERNET#1 = Press Releases Site

BLANKINTERNET#2 = Publishing Site with Workflow

SPSNHOME#0 = News Site

SPSSITES#0 = Site Directory

SPSCOMMU#0 = Community area template

SPSREPORTCENTER#0 = Report Center

SPSPORTAL#0 = Collaboration Portal

SRCHCEN#0 = Search Center with Tabs

PROFILES#0 = Profiles

BLANKINTERNETCONTAINER#0 = Publishing Portal

SPSMSITEHOST#0 = My Site Host

SRCHCENTERLITE#0 = Search Center

SRCHCENTERLITE#1 = Search Center

SPSBWEB#0 = SharePoint Portal Server BucketWeb Template

 

 

 

 

Posted in Moss Bolgs | Tagged: , , , | 1 Comment »

Error 6482 : Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance

Posted by fillzephyr on August 6, 2009

Error 6482

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6482
Date:  4/15/2009
Time:  3:50:10 PM
User:  N/A
Computer: MOSSPRD
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (0953efa6-baa1-474d-8e4d-58a31fad7a2e).

Reason: The underlying connection was closed: An unexpected error occurred on a send.

Techinal Support Details:
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. —> System.IO.IOException: Authentication failed because the remote party has closed the transport stream.
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
   — End of inner exception stack trace —
   at Microsoft.Office.Server.Search.Administration.SearchApi.RunOnServer[T](CodeToRun`1 remoteCode, CodeToRun`1 localCode, Boolean useCurrentSecurityContext, Int32 versionIn)
   at Microsoft.Office.Server.Search.Administration.SearchApi..ctor(WellKnownSearchCatalogs catalog, SearchSharedApplication application)
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Resolution:

I am getting this error after my fresh installation in Of Moss Prod with SP1. I am having 64 bit environment.

I had download iis resource kit from Microsoft website.
After downloading on the server I run the selfssl command from :

Then I type the following commands :

( Installs self-signed SSL certificate into IIS.
SELFSSL [/T] [/N:cn] [/K:key size] [/S:site id] [/P:port]

/T               Adds the self-signed certificate to “Trusted Certificates”
                 list. The local browser will trust the self-signed certificate
                 if this flag is specified.
/N:cn            Specifies the common name of the certificate. The computer
                 name is used if not specified.
/K:key size      Specifies the key length. Default is 1024.
/V:validity days Specifies the validity of the certificate. Default is 7 days.
/S:site id       Specifies the id of the site. Default is 1 (Default Site).
/P:port          Specifies the SSL port. Default is 443.
/Q               Quiet mode. You will not be prompted when SSL settings are
                 overwritten.

The default behaviour is equivalent with:

selfssl.exe /N:CN=MOSSPRD /K:1024 /V:7 /S:1 /P:443 )

C:\Program Files (x86)\IIS Resources\SelfSSL>selfssl /s:951338967 /v:1000
Microsoft (R) SelfSSL Version 1.0
Copyright (C) 2003 Microsoft Corporation. All rights reserved.

Do you want to replace the SSL settings for site 951338967 (Y/N)?y
The self signed certificate was successfully assigned to site 951338967.

Posted in Errors, IIS, Moss Bolgs | Tagged: , | Leave a Comment »

Errors 6398, 7076, 6482 on Only One server.

Posted by fillzephyr on August 6, 2009

I have 2 Web Front End  Server A  and Server B
I  ll find the errors  6398, 7076, 6482 on the event viewer of  server Server B  only (Not Server A) OR When I try to look at the web sites listed under IIS of Server B  , I’ll get a dialog box noting “Specific path cannot be used at this time”.
 
To resolve I ll have to just go to the services(Path : Start>Administrative Tools>Services) Open it.
Go to the Windows SharePoint Services Timer and restart it. This error will gone.
 
There are Hot fixes there for it but it happens sometime only and Again its effect to Server B only Not the Server A.
 
The reason for this error is beause “You may be unable to manage IIS by using Server Manager if two threads access IIS at the same time”
 
Thanks.
 

Posted in Errors, Moss Bolgs | Tagged: , , , | Leave a Comment »

Install ASP.NET v2.0.50727 in IIS

Posted by fillzephyr on August 6, 2009

i had install the .netframework 2.0 sp2. .netframework 3.0 sp2 and .netframework 3.5 sp1.
when i see in my IIS under the server node in folder Webserver extension. ASP.NET v2.0.50727 is missing. so now i had double check whether its installed or not, for that i go to
C:\WINDOWS\Microsoft.NET\Framework64 and its reside under there so to install it i run this following cmd.
 
Open the command prompt on the server. Then go to the specified path and run this cmd.
 
C:\>WINDOWS\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i
Start installing ASP.NET (2.0.50727).
……………….
Finished installing ASP.NET (2.0.50727).
 
Go to IIS expand the Node .Go to the Webserver Extensions and then check the ASP.NET v2.0.50727 installed. After it is installed clicked on it and select Allow.
 
Thanks
 

Posted in General, IIS, Moss Bolgs | Tagged: , | Leave a Comment »

Rename “My Site” Link Text to “My Something”

Posted by fillzephyr on July 9, 2009

I get a requirement to change the top global links for “My Site”  text to something different  like “My” instead of “My Site”. I had try this method

http://fillzephyr.wordpress.com/2009/06/26/redirecting-or-changing-my-sites-link-name-to-the-new-link-name/

and it works fine but when you access site in extranet zone it will shows “My” externally , which i dont want to.

so i get around this trick :

Go to MySiteLink.ascx located at 

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\CONTROLTEMPLATES 

Open MySiteLink.ascx modify at two places make the original hyperlink ” invisible” as shown below:

 Backup the MySiteLink.ascx before you do any modification

  < asp:HyperLink id=”hlMySite” runat=”server” Visible=”false” />  

check it after these changes that the My Site link disappear at the top global links.

Then add the following line below it :

< asp:HyperLink id=”NewMySiteHyperlink” runat=”server” Text=”My” Visible=”true” NavigateUrl=”http://mysitewebappurl/_layouts/MySite.aspx” /> 

Check that it will works.

I test it by deleting My site and recreate it, it works fine for me. Also i check externally and it will not shown up.

Hope it will work for you guys.

Thanks!!!!

Posted in MOSS Funstuff, Mysite | Tagged: , , , | Leave a Comment »

Hide Left Navigation

Posted by fillzephyr on July 7, 2009

I am trying to hide left navigation through this little javascript.

Go to site Action> edit page> Add webpart

Choose content editor webpart.

Select source editor and paste the below script :

<style>
.ms-quicklaunch
{
display:none;
}
.ms-navframe
{
display: none;
}
</style>
On the appereance change the Title to Hide Left Nav bar

On the Layour check the Hidden

Thanks!!!

Posted in MOSS Funstuff, Moss Bolgs | Tagged: | Leave a Comment »

Redirecting or Changing My Sites Link Name to the New Link Name

Posted by fillzephyr on June 26, 2009

 

I had got a requirement to change the name of hyperlink  from ” My Site “to the some other Name called “ My”. 

 

mybitmap3

 

I had download this codeplex project…………….

http://www.codeplex.com/SPMySpace/Release/ProjectReleases.aspx?ReleaseId=18151

Open the Project using Visula studio. Go to the \12\TEMPLATE\CONTROLTEMPLATES\MySpace in the Project and open the MySpaceLink.ascx file

Now go to the line

<asp:HyperLink id=”hlMySite” Text=”MySpace” NavigateUrl=”/_layouts/MySpace/MySpace.aspx” runat=”server” /> 

here change the Text = “My”.  Save the file.

Now  rebuild the solution to see if there is any error.

After builing solution successfully, create the solution package using WSP builder.

Now add the solution to the server. Deploy it globally.

You can see the change to “My” from “My site ” at the top link.

 

  Mysite

 

Hope It will helpful.

Thanks!!!

 

Posted in Moss Bolgs, Mysite | Tagged: , , | 1 Comment »

Unable to Delete Share Service Providers (SSP) in SharePoint 2007 (MOSS)

Posted by fillzephyr on June 23, 2009

I am trying to delete two SSP from my environment and I am always getting this error:

An object in the SharePoint administrative framework, “SharedResourceProvider Parent=SPFarm”, could not be deleted because other objects depend on it.  Update all of these dependants to point to null or different objects and retry this operation.  The dependant objects are as follows:

- here I don’t see any dependencies (that’s really makes me wonder what’s happening)

I tried both ways to delete SSPs from central admin as well as using STSADM command:

stsadm –o deletessp –title “SSPName”

When I go to the Manage this Farm’s Shared Services Then my both SSPs are shown as unprovisioning.

I went through this simple way of deleting ssp.

First of all I find the Object id of my SSP. To come out through this I open the SQL Server Management Studio gone to the Objects table.

Under Databases>sharepoint_config_DBName > tables > dbo.Objects

And run the following select query

SELECT * FROM [SharePoint_Config_ DBName].[dbo].[Objects]

where name like ‘SSPName’

and find out the ID of my ssp.

Then I run the following stsadm command:

Stsadm -o deleteconfigurationobject -id “id retrieved from object table”

And still it gives me the same above error.

(In most of the cases after running above cmd when you try to delete SSP it works , but not in my case)

I then try this other way:

I find out that the object status of my ssp is “3” which should be 0 by default, so to convert it to 0 I run the following update query on my objects table

UPDATE [SharePoint_Config_ DBName].[dbo].[Objects]

SET [Status] = 0 WHERE objects.name=’SSPName’

It sets my status to 0.

When I go to the Manage this Farm’s Shared Services and refresh it the unprovisioning warning sign gone.

Now I tried to delete ssp using stsadm still the same error and the ssp shows unprovisioning warning sign again. I check in the object table and it shows me the status update to 3. I again change the status and make it to 0.

Now I want to delete the row with the object id of my ssp as I feel it’s an orphaned. I find the object id running select query.

SELECT * FROM [SharePoint_Config_ DBName].[dbo].[Objects]

where name like ‘SSPName’

then find the dependencies running the following query on dependencies table loacte

Under Databases>sharepoint_config_DBName > tables > dbo. Dependencies

SELECT * FROM [SharePoint_Config_DBName].[dbo].[Dependencies]

where [ObjectId] = ‘EBE75FD3-4EA3-4BF0-BC15-E796A0F7BC21′

check the dependencies.

Then delete it using the following query on dependencies table

Under Databases>sharepoint_config_DBName > tables > dbo. Dependencies

DELETE FROM [SharePoint_Config_ DBName].[dbo].[Dependencies]

WHERE [ObjectId] = ‘EBE75FD3-4EA3-4BF0-BC15-E796A0F7BC21′

Now I try to delete the unnecessay SSP and it is deleted through the Central Admin.

Hope it will help you out in issues of deleting the SSP.

Thanks!!!

Read the rest of this entry »

Posted in Errors, Moss Bolgs | Tagged: , , , , | 4 Comments »

Change number of site collections view in Site Collection List

Posted by fillzephyr on May 14, 2009

Go to

Central Administration>Application management> Site Collection List

Default you can see 10 site collections in a list at a time.

I want to change it to 20 as I have 376 site collections and I don’t want to go long way to click for more pages.

So to change it I go to

C:\Program Files\Common Files\Microsoft Shared\web server extensions\ 12\ TEMPLATE\ ADMIN\sitecollections.aspx

Open sitecollection.aspx page

Find PageSize and do the following thing:

change the number 10 to your “specified number” in PageSize=” your number”

Thanks.

Posted in MOSS Funstuff | Leave a Comment »

Solutions Deployment Hungs up on Deploying/retracting in MOSS 2007

Posted by fillzephyr on May 11, 2009

Problem: During the execution of a retraction/deployment the timer job may hang showing ‘Retracting’ or ‘deploying’ and never completes

Cause: This is cause from one of the WFE not being able to finalize the retraction or deployment.

Solution: For each WFE in the farm execute a stsadm.exe -o execadmsvcjobs. I had follow up these two good articles to come out from deploying /retracting status.

http://msmvps.com/blogs/shareblog/archive/2007/12/27/process-appears-hung-when-deploying-retracting-solutions.aspx

http://www.alexthissen.nl/blogs/main/archive/2007/07/18/removing-malfunctioning-windows-sharepoint-services-solutions.aspx

But what next when I try to deploy/retract the solution again. It hung’s up.  So I tried to figure out whats the problem causing this thing. I checked in my Timer job status (Central Administration>Operations>Timer Job Status) and it show that the Solution is tried to deploy on my one WFE and the index server.   I had not found any deployment on my other WFE So I had executed the command stsadm.exe -o execadmsvcjobs manually on the other WFE server. And it works like a charm the solution deployed/retracted successfully.

Also I had tried to check the time of my servers and my CA web application to confirm that they both are on the same time zone sometime this may also create a problem for deploying/retracting the solutions on the servers. In my case they are on the same time zone. To check the time zone for your CA site just

GO TO

Central Administration>Application Management>Web Application General Settings

Select your central administration web application. In Default Time Zone just checks out the time to match with your servers. If it’s not matched then select the appropriate time zone and click OK.

Thanks.

Feedback appreciated.

refrences :

http://www.alexthissen.nl/blogs/main/archive/2007/07/18/removing-malfunctioning-windows-sharepoint-services-solutions.aspx

http://msmvps.com/blogs/shareblog/archive/2007/12/27/process-appears-hung-when-deploying-retracting-solutions.aspx

http://www.sharepointps.com/blog/?tag=/deployment

Posted in Errors, Moss Bolgs, Warnings in MOSS | Tagged: , , , | Leave a Comment »

An error occurred accessing a data source. An entry has been added to the Windows event log of the server. Log ID:5566

Posted by fillzephyr on May 3, 2009

I tried to open the InfoPath form from the form library as web-browsable form and I fall on to this error:

An error occurred accessing a data source. An entry has been added to the Windows event log of the server.

Log ID: 5566

The cause of this error is the installation of .net 3.5 SP1. So to resolve this error you have to add key to the registry on all of the servers I have 2 WFE and 1 Application server. I had change the registry key on the entire server and restart the servers. The first server I restart is of course WFE on which my CA resides and the other WFE and then Application server. I think it’s always best to change first in Server on which CA resides.

I had followed these steps on all my servers and it works for me:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
  3. Right-click Lsa, point to New, and then click DWORD Value.
  4. Type DisableLoopbackCheck, and then press ENTER.
  5. Right-click DisableLoopbackCheck, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor.
  8. Restart the computer.

Reference: http://support.microsoft.com/kb/926642

Posted in Errors, infopath | Tagged: , | 3 Comments »