Google

My Books recommendations

Wednesday, June 17, 2009

Cannot connect to the configuration database

My WSS/MOSS server was giving me this error after a restart of the server [I  have all in one server], later figured out that my SQL Server Browser service was set to manual start and SharePoint requires SQL Server Browser service enabled/started otherwise it will throw “Cannot connect to the configuration database” error. Fixed!


This message may be confidential, privileged or otherwise protected from disclosure. It does not represent the views or opinions of Ofgem unless expressly stated otherwise.

If you have received this message by mistake, please contact the sender and immediately delete the message from your system; you should not copy the message or disclose its contents to any other person or organisation.

SharePoint Designer 2007 _catalogs folder is empty

After frustrating  half an hour, I figured that refreshing the view [View > Refresh  or F5] does the trick and the master pages and other folders under _catalogs appears!!

 

 


This message may be confidential, privileged or otherwise protected from disclosure. It does not represent the views or opinions of Ofgem unless expressly stated otherwise.

If you have received this message by mistake, please contact the sender and immediately delete the message from your system; you should not copy the message or disclose its contents to any other person or organisation.

Friday, June 12, 2009

STSADMWin - a windows based STSADM Tool

As STSADM is a command line utility, and the command-line is somewhat limited compared to Windows GUI, especially when it comes to non-English usage, there is a room for GUIs like stsadmWin (STSADM for Windows). I am always a fan of STSADMWIN a windows based STSADM Tool since I found it in 2003/2004. The new version works with both Sharepoint 2003 and 2007. Try it! It will make your life lot easy..

 

How stsadmWin works?

stsadmWin reads a list of commands from an XML file (namely: operations.xml), and displays a combo with the operations, denoting mandatory and optional parameters, and linking to the utility’s help.

Download

 

You can download STSADMWin from following link:

 

http://blogs.msdn.com/ronalus/attachment/1411643.ashx

 

 


This message may be confidential, privileged or otherwise protected from disclosure. It does not represent the views or opinions of Ofgem unless expressly stated otherwise.

If you have received this message by mistake, please contact the sender and immediately delete the message from your system; you should not copy the message or disclose its contents to any other person or organisation.

Directory does not exist or the Sql server service account and the service account don not have permission to read or write to the back up folder

You receive  following error when you try to restore backup from local or remote network location:

“Directory (restore machine path on domain) \\testserver\backup does not exist or the Sql server service account and the (back up machine path on workgroup).

domain\accountname service account don not have permission to read or write to the back up folder”.

In my case, I was logged in to one of my WFEs and created folder in the WFE and then tried to use the local folder path like D:\Backupdata which was giving me the above error. I later realised that the path really didn’t exist as the D:\Backupdata was created on other front end when i logged in couple of hours ago and when I reclogged in the loadbalanced server the load balancer has switched the server to the different WFE and D:Backupdata didn’t exist on this server. So it’s always better to enable sharing of the backup folder and provide names in the restore like \\servername\backupfolder rather than D:\backupfolder.

 

Lesson learned!

 

 

 

               


This message may be confidential, privileged or otherwise protected from disclosure. It does not represent the views or opinions of Ofgem unless expressly stated otherwise.

If you have received this message by mistake, please contact the sender and immediately delete the message from your system; you should not copy the message or disclose its contents to any other person or organisation.

Only machine administrators are allowed to create administration service job definitions

 

Access denied. Only machine administrators are allowed to create administration service job definitions:

 

During restoring a sharepoint backup you might get this error basically this means few things:

 

1.  The SQL Server name specified has named instance missing (i.e. SQLSERVERNAME\NamedInstance) or

2.  The account used for the restore doesn’t have sufficient rights [make sure that account used to restore has appropriate rights on the WFEs and SQL Server also, it makes life bit easy if the account also has local admin rights and farm admin rights, you can always remove the rights later].

 

 

 


This message may be confidential, privileged or otherwise protected from disclosure. It does not represent the views or opinions of Ofgem unless expressly stated otherwise.

If you have received this message by mistake, please contact the sender and immediately delete the message from your system; you should not copy the message or disclose its contents to any other person or organisation.

Wednesday, June 10, 2009

The farm is not available

While installing one of the feature,i got following error

 

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsa

dm -o installfeature -name AKS -force

 

The farm is unavailable.

 

I found out that the account I am using to install the feature doesn’t have permission on the SharePoint DB server. I’ve added my self in the db server and the error went away!

 

Hope this helps..


This message may be confidential, privileged or otherwise protected from disclosure. It does not represent the views or opinions of Ofgem unless expressly stated otherwise.

If you have received this message by mistake, please contact the sender and immediately delete the message from your system; you should not copy the message or disclose its contents to any other person or organisation.

How to pass session variable in sharepoint webpart

 

During  my current project I came across this small hiccup, where I wanted to pass value of a variable from one page to the other in a sharepoint webpart, since Webpart doesn’t provide this out of the box. I have discovered this little gem from my research.

 

I wanted to retain value of logged in user’s style preference for the page, the following line of code besically retains the value in the combination of page session and and class variable.

 

strUser = loggedInUser [strUser declared at class level]

                 

                  Page.Session.Add("userStyle", strUser); //when user first time login/load on the page.

 

      Then use this Page.Session object to retrive the value of strUser for other functions like:

 

strUser = Page.Session["userStyle"].ToString();

 

and write the value of the strUser using

 

Page.Response.Write("StrUser:" + strUser);

 

 

 

Hope this helps.

SharePoint and Accessibility

Currently I am working at my client site on Accessibility project for SharePoint. My client is a government client and wants their website to be accessibility complient (WCAG 1.0 AA). My task is to convert their existing non WCAG 1.0 compliant site and convert it into a compliant site.

 

So far I have found following:

 

There is something called Accessibility Kit for SharePoint (AKS) from Hi Software. Hi Software has worked with Microsoft to produce this Accessibility kit.  The good news is the Kit

Key Features in the AKS v2.0

The AKS v2.0 introduces the following:

  • Smart Control adapters which greatly reduce the amount of custom configuration previously required for AKS control adapters.
  • The Web Part Zone Control Adapter, a special Smart Adapter that modifies the output of SharePoint so that it does not use tables for layout of the Web parts.
  • HiSoftware’s Compliant Code Engine (HCCE) to assist organizations in creating code that is compliant to standards-based HTML or XHTML.
  • Additional requirements under Canadian Common Look and Feel 2.0 (CLF 2.0) guidelines.
  • Examples of remediation to comply with WCAG 2.0 Level AA.
  • French language version of AKS 1.0 components.

 

I will post more as I progress in the project.