There is good small utility out there on VMWare web site that can test your machine to ensure it has the necessary hardware for working with vmware virtual machines. There is a PDF available to with instructions on how-to. Available for Windows and Linux.
You can find it here: Processor Check for 64-bit Compatibility
I was trying to bring-up SharePoint Central Admin on my old virtual machine (VPC 2007), but it never seemed to show-up.
When I tried to start the IIS Manager, I found no listings in it. I remembered, I had the same issue with one of my client recently and wanted to get to the root of this.
The only thing that I saw on the left pane was “IIS…” and the message “There are no items to see in this view.” on the right pane.
Looking at the Event Viewer – Systems, I saw this error specific to the “Service Control Manager” -
EventID: 7024
Error description: “The IIS Admin Service service terminated with service-specific error 2149648394 (0x8021080A).”
A little bit of web searching gave me a quick understanding about the metabase file getting corrupt and needed a restore from the IIS history folder.
Note: Some posts advised killing the inetinfo.exe in the TaskManager, which I never found as one of the processes.
So this is what I did to restore my previous metabase file (Here, it needs your intuition to make a call, and select a proper metabase file that you know would have been in a “GOOD STATE” before things got corrupted.) I compared the timestamp of the current file and looked for a file which was earlier than that. It worked for me and hopefully should work for you too :)
#1. Go to the folder location “C:\WINDOWS\system32\inetsrv” and backup the file named “MetaBase.xml”. Then delete this file from this location.
#2. Browse to the “C:\WINDOWS\system32\inetsrv\History” subfolder and choose the right .xml metabase file that you found to be in a good state. It should be called something like “MetaBase_0000013890_0000000000.xml”.
#3. Copy this file and paste it in “C:\WINDOWS\system32\inetsrv” folder.
#4. Now rename this to “MetaBase.xml”.
#5. Restart IIS. If the “IIS Admin Service” and all its dependent services are enabled, you IIS tree would start appearing. If not then probably, you need to look for each of the dependant services and try to start them in the order they need to be. Good Luck!!!
Pronounced “Command-lets”, cmdlets are a great way of scripting Administrative tasks in SharePoint 2010. I personally feel that I was missing such a tool till last year working with MOSS 2007. But with cmdlets, it looks extremely promising that Microsoft has ultimately provided the SharePoint Administrators – a single platform to script their tasks and run commands remotely/locally.
Recently, I was trying to look into these cmdlets and here are some quick view into some of the most basic ones.
Interestingly, these cmdlets are in a format that resembles the verb-noun pair. The noun generally starting with a “SP” for all SharePoint cmdlets.
#1. Get-SPContentDatabase: This gives you a list of all the Content DBs in your farm, with information on ID, Name, Server and Site count.
Okay, now you must be thinking that I am going to get nasty by listing down all these cmdlets, uhh… you are definitely wrong.
Instead, I just figured-out how to retrieve a list of such SP cmdlets and also how to pull more information about each of them.
Get-Command and Get-Help can be really handy for anyone starting on these. Here’s an example of how to use the Get-Command.
Get-Command –PSSnapin “Microsoft.SharePoint.PowerShell”
Further-more, if you start creating your own scripts, you would also need to start using these two very often:
> Measure-Command: This gives you the cmdlets execution time.
> Trace-Command: gives you the ability for debugging short scripts.
So here is a another feature that makes you happier when you are using the SharePoint Designer 2010. The integration with Visio 2010 has been improved quite-a-bit. Now you can create your companies workflows diagrams as flowcharts in Visio 2010 and export the file, to consume/import it back in SPD 2010. Awesome! I like that.
So you must be thinking to get started right away……. but wait !!!
There are some pre-reqs to this. You need to have the Premium edition for Visio 2010. With this edition, you can find the specific “SharePoint Workflow” templates to start creating the flowcharts.
So buckle up – and lets start the tour.
#1. Open Visio 2010 Premium edition.
#2. Select “Flowchart” and then “Microsoft SharePoint Workflow” from “Choose a Template”. Select your own Units, I selected [US Units] and click Create.
#3. You will get to choose from a list of SharePoint Workflow Actions, Conditions and Terminators.
This can then be very easily exported as a .vwi (visio workflow interchange) file which can be imported in your SharePoint Designer workflows and vice-versa too.
So have fun with SPD 2010 workflows.
I had a SQL Server 2008 Standard edition setup for the DBEngine and Integration Services. For some reason I did not install the Reporting Services at that time. Now I was trying to get the Reporting Services (RS) deployed with SharePoint 2010 in the integration mode.
The first choice was to install the RS. I got started, but to my surprise I saw the first two options “Install the Native mode…” and “Install the SP integrated mode…” disabled. I only had the option “Install, but do not configure the report server.” available to me.
Man, where did I go wrong. This is what it came to me first. But after a little search, I realized that this happens if you try it installing after the initial installation. And that is what I was doing. So I decided to proceed. I did see some warnings but they were not of much concerns.
I had to start the RS Configuration Manager from the Configuration Tools option and the later setups were pretty much the same old way of going through the wizard steps.
So there I was. And as the next steps, definitely you need the RS Add-In on SP 2010 box and take care of the rest of standard CA configuration steps.
I had a SP 2010 site setup and access it from my client machines. I was able to perform all administrative tasks from CA when I decided to switch to the server box and use the same host url “http://sharepoint.mycompany.com” that I was using from my client machine.
Guess what, I was not able to login to the site and it kept prompting me for my userid/pwd.
After much of looking around, found this useful article which seems to be pointing to the security measures put in place by Microsoft starting Windows Server 2003 SP1 and later. It essentially got the loopback check in-place to prevent Man-In-The-Middle (MITM) attack from malicious apps.
You can read more about is here.
The news that Microsoft was not going to upgrade these Fab 40 templates has been giving jitters to quite a bunch of people like me, as we were already using them in MOSS 2007 and needed to upgrade with SP 2010.
But fortunately enough, TechSolutions has come for rescue.
These guys are making the upgraded versions available as and when they are getting ready. You can find the different versions as below:
Fab 40 Templates for SharePoint Server 2010
Fab 40 for SharePoint Foundation 2010
Keep watching them, if you do not find one you are looking for.
I was getting “List does not exist error” while accessing any list or doc library. It said something like this below:
The page you selected contains a list that does not exist. It may have been deleted by another user.
=======================================================
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 9067ed55-d26c-46a7-84d6-7c1838441992
Date and Time: 9/14/2010 4:12:33 PM
<- Go back to site
=======================================================
Got this resolved. Actually, there was no proper AAM for the corresponding DNS entry for the Intranet zone.
