According to a study by Microsoft and IDC, cloud computing technologies is likely to create 14 million jobs worldwide by 2015. The study also says that the revenue generated by cloud industry will total $1.1 trillion beginning in 2015.
According to an article posted on InformationWeek last month:
“Most new cloud jobs will be created in media and communications, manufacturing, and banking. In the case of the latter industry, many enterprises are expected to deploy private clouds as security concerns limit their interest in the public cloud, according to the study’s authors.
Geographically, emerging markets are expected to see the most growth in cloud-related jobs. Brazil is in line to see growth of 186%, India will see 99% growth, and China is expected to experience 84% growth. Cloud jobs in the U.S. are expected to grow by 66% by 2015.”
You can read the entire story here.
In case you didn’t know, according to Microsoft, SharePoint Designer has nothing to do with designing SharePoint? Then why is it called SharePoint Designer? Good question. The simple answer is: for the same reason that you have to click Start to shutdown Microsoft Windows. Just kidding! I really don’t have a clue why Microsoft would name a product then tell us that the name is meaningless and we should ignore it. You would think a name like SharePoint Editor would have made more sense.
One thing is for sure, SharePoint Designer will no longer be called SharePoint Designer in future because the name makes no sense at all. That’s just my prediction. According to Microsoft:
“SharePoint Designer 2010 is designed for users to work on — not to design and publish — SharePoint Foundation 2010 and SharePoint Server 2010 web sites.”
Some people may consider SharePoint Designer 2010 to be a crippled version of FrontPage, even though when it comes to coding SharePoint Designer is a much better product. Others may consider SharePoint Designer 2010 a crippled version of SharePoint Designer 2007, which is perhaps a better way to describe it. Microsoft has removed a lot of features in SharePoint Designer 2010. Here is a partial list of what’s missing or changed.
I often create a new site collection based on Microsoft Office SharePoint Server (MOSS) 2007 Collaboration Portal template for my clients’ intranet site. Just so you know, the Collaboration Portal template is hidden in SharePoint Server 2010. I use a PowerShell script to create the top-level site collection using the site template ID (SPSPORTAL#0) for the Collaboration Portal, as documented in my post Installing Collaboration Portal in SharePoint 2010.
Sometimes you may want to create a site based on your own custom site template that you have previously saved. Of course, if the site is a subsite then you can use the GUI to create the site, unless it’s a hidden template. However, if you want to use a script, and there are several situations where you may want to do that, the following script will come handy to create a new site based on a custom site template. Thanks to SharePoint MVP Alex Pierce for this script.
Step 1
Get the site template ID using the following method.
Replace “http://www.contoso.com/” with your site URL.
Step 2
Use the method documented in my post Installing Collaboration Portal in SharePoint 2010 to create a new site based on your custom site ID.
Microsoft has documented some useful information on how to determine your current Microsoft SQL Server version number and the corresponding product or service pack level in the KB article 321185. The article also describes how to determine the specific edition of SQL Server that you are using.
There is another article that has information on how to find the latest builds for SQL Server. That information is available in the KB article 957826.
For example, to determine the version number of the SQL Server Client tools in SQL Server 2008 R2 you can start the SQL Server Management Studio (SSMS) and go to Help, About.
It’s easy to verify that you have the latest build by using these KB articles. For example, Build 10.50.2806.0 (Cumulative update package) was the latest build as of today for SQL Server 2008 R2 since the release of SQL Server 2008 R2 Service Pack 1.
I recently installed a new SharePoint Server 2010 Enterprise for a client. I also installed a SQL Server 2008 R2 Standard. Both were installed on separate Windows Server 2008 R2 servers running in a virtual VMware environment.
PROBLEM
After I successfully created the User Profile Synchronization (UPS) application and started the service, everything looked good. Then I went to Manage service applications in Central Administration under Application Management and clicked on the hyperlink for the newly created UPS application so I can configure Active Directory synchronization connection. Unfortunately, I received the following dreaded error.
An unexpected error has occurred.
SOLUTION
Here are some of the actions I took. I am listing all the solutions I tried because some of them are most likely to fix your error.
- Stop the Windows SharePoint Services Timer service (Found in Windows Services)
- Navigate to the cache folder In Windows Server 2008, the configuration cache is in the following location: Drive:\ProgramData\Microsoft\SharePoint\Config In Windows Server 2003, the configuration cache is in the following location: Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config Locate the folder that has the file “Cache.ini” (Note: The Application Data folder may be hidden. To view the hidden folder, change the folder options as required)
- Back up the Cache.ini file.
- Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.
- Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
- Double-click the Cache.ini file.
- On the Edit menu, click Select All. On the Edit menu, click Delete. Type 1, and then click Save on the File menu. On the File menu, click Exit.
- Start the Windows SharePoint Services Timer service
- Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
- Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.

After I installed the update KB2560890 I was prompted to restart the server. After the restart the error went away and I was able to successfully manage the profile service.
Hopefully one of the above solutions will solve your problem. In my case solution #11 did the job.
Contact E-mail | Terms of Use | Privacy Policy
Copyright ©2010 Zubair Alexander. All rights reserved.
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Apr | ||||||
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | 31 | |||
24 queries. 0.369 seconds