Feeds:
Posts
Comments

Archive for the ‘MOSS 2007’ Category

Hello Friends,

MOSS2007 is still live and sometime we need to check certain features and that can give learning too. Recently one of my friend was installing MOSS 2007 on his Virtual machine and during the configuration of the “SharePoint Configuration Wizard” he encountered an error while creating a new farm.

Ashish-Sql connec

Error is reflecting that SQL Server cannot be connected to the network, To diagnose it further we check lot of stuff:

  • VMware network settings.
  • IP addresses Provided to the servers were in the same subnet mask.
  • Any specific DNS issue.
  • able to ping IP address from both ends.
  • Non blockage of SQL port 1433 by firewalls.

It was my mistake and didn’t check PS config Diagnostic configuration error log at first in the 12 Hive. After spending some time and checking the log thoroughly. We got a log entry that “Named Pipes” might not be enabled on the SQL Server.

I check the Microsoft sites and there was no need for Named pipes as the connection are made through TCP socket but still I enabled Named Pipes on Sql server.

I tried the things again and this time it run without any error. It was success.

“Named Pipes” can be enabled as:

  1. Go to “SQL Server Configuration Manager”
  2. Go to “SQL Server 2005 Network Configuration”
  3. Go to “Protocols for MSSQLSERVER”
  4. Right-click the “Named Pipes” and “Enable” it.

If you uninstall and install sharepoint again or disable named pipes on same server configuration you will never get the error again. But if you create a new server VM and all configuration it will give same error. I have checked it but not sure why it gives error on new servers. Might be on fresh it needs named pipes to be enabled for a single time.

But nevertheless problem got resolved.

Hope I was able to describe the content correctly based on my knowledge and learning.

If you liked this post, do like on Facebook at: https://www.facebook.com/Ashishsharepointblog

Feel free to Rate and provide feedback if you find post useful

Hope this help
Ashi

Read Full Post »

Friends, do every time we need the GUI ? or we feel the need of Customized things some times in life.

Given this thought in my mind and feel to discuss how to Configure MOSS with command line, Database name with our requirement not with additional unwanted GUID  attached with it. So after installing MOSS we would not use GUI to configure it, Instead use PSCONFIG command and give name and parameter as per our desire.

PSCONFIG command to configure MOSS:
Goto “c:\programfiles\commonfiles\microsoftshared\webserver extension\12\bin”

1. Create farm configuration:

Psconfig –cmd configdb –create –server (Sql server name) –database (database-name) –user (domain\username) –password XXXXXXX –admincontentdatabase (Sharepoint_AdminContent or as per your required name)

2. Ensure SharePoint has access to folders and registry:

Psconfig –cmd secureresources

3. Create Central Admin

Psconfig –cmd adminvs –provision –port (port no) –windowsauthprovider onlyusentlm

4. install SharePoint services

Psconfig –cmd services –install

5. install SharePoint features

Psconfig –cmd installfeatures

6. Launch browser to access Central Admin.

stsadm -o installfeature -name PublishingTimerJobs

Conventions:

-server: Sql server name on which you want to create config database.
-database: sharepoint configuration database name you want to give.
-admincontentdatabase: SharePoint admin content database name

Now SharePoint has been configured in the same way as with GUI mode, but this time you have database free from unwanted GUID all things configured as per your requirement.

Hope I was able to describe the content correctly based on my knowledge and learning.

If you liked this post, do like on Facebook at: https://www.facebook.com/Ashishsharepointblog

Feel free to Rate and provide feedback if you find post useful
Hope this help
Ashi

Read Full Post »

Friends, Life is not easy and every time we cannot create a fresh/new server, environment or a new configuration. What will happen if a production ssp goes corrupted or goes down. To create a new ssp with full customized configuration will take more than a week. If we would have any way to get this done in 3-4 hrs. we would be on the top of world.

Yes, we can do that: but how?

Production or any other UAT, DR environment are always supported with a regular backup of databases but how to use it in a way to get the same customization again. It is just same as restoring , but need to be done carefully and understanding the concept.

How can we do that:
1) We should have backup of ssp database and ssp search database.
2) We should have details of all the entries like ssp-url, account & mysite url.

Now the command is:

stsadm -o restoressp -title (SSP-Name) -url (http://ssp-url) -ssplogin (domain\accountname) -mysiteurl (http://mysiteurl) -indexserver (indexservername) -indexlocation (“C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications”) -ssppassword (password) -sspdatabaseserver (SSP database server name) -sspdatabasename (SSP database name) -searchdatabaseserver (search database server name) -searchdatabasename (SSP Search database name)

Conventions:
-tiltle: SSP-Name
-url: ssp-url
-ssplogin: ssp account
-mysiteurl: ssp mysite url

Note: This command can be used for two purpose:

1) creating a fresh new(dev or any other) environment by using production ssp backup.


2) When the ssp got corrupted. In this case you have to create a dummy ssp with dummy ssp site and other stuff(to delete afterwards). As you cannot delete a defult ssp. Make the new dummy ssp and made it default. And then delete the corrupted ssp with it site url and my site url and db. Use the above command and it will do all for you.


Now you can made the new ssp as default and carry on with your task successfully.

Hope I was able to describe the content correctly based on my knowledge and learning.

If you liked this post, do like on Facebook at: https://www.facebook.com/Ashishsharepointblog

Feel free to Rate and provide feedback if you find post useful
Hope this help
Ashi

Read Full Post »

Friends, As covered in one of my previous blog:

How crawl works in SharePoint ||How indexing work||Basic concept .

We were discussing about ifilters , so How to get these ifilters and what are the various steps need to be taken in the configuration of ifilters? I will work with the example of PDF and the same works for the other types of ifilters or the extension of document which you want in search.

So, to install a PDF ifilters:

  1. Download Adobe PDF Ifilters for 32 & 64 bit platform in MOSS and 64 bit for SharePoint2010.Example Link for pdf version 11 is given below:
    http://www.adobe.com/support/downloads/detail.jsp?ftpID=5542
  2. Run the setup
  3. When the welcome page comes in, click Next.
  4. When the Software License Agreement page comes, click Accept.
  5. When the Choose Installation Location page comes, click Next.
  6. When the confirmation is displayed that the installation was successful, click OK.

Now to crawl the pdf files with pdf icon images , we have to put the image at SharePoint binary location:

Copy ICPDF.gif(it can be copied from installed files of ifilter) to location drive at which SharePoint Binaries installed: $\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Images.

A PDF extension entry need to be added in SharePoint XML file:

Edit the file \Program Files\Common Files\Microsoft Shared\Web server extensions\12\Template\Xml\DOCICON.XML and put
<Mapping Key=”pdf” Value=”icpdf.gif”/>

Reset IIS to clear the cached settings. It is better to go for iisreset with noforce command: iisreset /noforce

It is pretty necessary to add the file types in the index list, only then the search will work:

  1. On the SharePoint Central Administration home page, Goto Shared Service Provider to open the Shared Services Provider administration site.
  2. On the Shared Services Administration home page, in the Search section, click Search settings.
  3. On the Configure Search Settings page, click File types.
  4. On the Manage File Types page, click New File Type.
  5. On the Add File Type page, in the File extension box, type pdf and click OK.

Note: If the filter for a document is installed after content is indexed, Full crawl on the content indexes need to be done in order to reflect the changes and include PDF documents in search results.

Hope I was able to describe the content correctly based on my knowledge and learning.

If you liked this post, do like on Facebook at: https://www.facebook.com/Ashishsharepointblog

Feel free to Rate and provide feedback if you find post useful
Hope this help
Ashi

Read Full Post »

Yesterday I was working with my team mates and their came a requirement to create a site collection but with consideration of future also. Things need to be fulfilled with help of Managed path. So , I thought to share the concept of managed path, wildcard inclusion and explicit inclusion with you all.

Let’s work with an example. Suppose I have a SharePoint site http://abc.com or any for abc company and today I got a requirement to create 3 site collection 1 for HR , Finance and Learning and the first 2 (HR and Finance will contain no of sites & site collection in it) and constraint for the 3 Learning, is that it should be directly under the root site abc.com .

How the things will be configured and work? We have to work with Managed path.
Managed path is a concept given by Microsoft to create different site collection according to different requirement. It is a path managed by SharePoint which will specify how many site collection can reside in a particular url. SharePoint has two type of managed paths:

1) Explicit Inclusion: it is a managed path under which no further site collection can be created. By default MOSS has a root as an explicit inclusion. N no of inclusion can be created manually. So as per my requirement I have to create site collection directly under abc.com. so first I will use root explicit inclusion to create my first ever site collection http://abc.com/ . and then I will create an another explicit inclusion “/Learning” and then I have a site collection with url as http://abc.com/learning .

Constraint: in Future I will never be able to create any site collection under learning.

2) Wildcard Inclusion: It is managed path under which n number of site collection can be created. By default MOSS has sites as only wildcard inclusion. N no of inclusion can be created manually
So as per my requirement I have to create 2 site collection under which number of site and site collection can reside .So with this requirement I will create an wildcard inclusion with name /HR and /Finance and the url for that will be http://abc.com/HR and http://abc.com/finance and now I have n no of site collection under /finance and /HR . ex. /HR/dep1 & /HR/dep2

So, on working with concept of wildcard and explicit requirement should be crystal clear . so that the things can be created to suit specific purpose.

Hope I was able to describe the content correctly based on my knowledge and learning.

If you liked this post, do like on Facebook at: https://www.facebook.com/Ashishsharepointblog

Feel free to Rate and provide feedback if you find post useful
Hope this help
Ashi

Read Full Post »

Older Posts »

Follow

Get every new post delivered to your Inbox.

Join 107 other followers

%d bloggers like this: