Out of habit I still type iisapp at a cmd prompt even though its gone in IIS7. I was going to add a batch file but that’s just grasping
Reminder to self:
%windir%\system32\inetsrv\appcmd.exe list wp
Out of habit I still type iisapp at a cmd prompt even though its gone in IIS7. I was going to add a batch file but that’s just grasping
Reminder to self:
%windir%\system32\inetsrv\appcmd.exe list wp
Sometimes you need to stop and start a Windows Service from the Cmd line or from a batch file. To do this you need to know the Windows Service’s ‘KeyName’ rather than the display name of the service.
To get the KeyName run this command from the cmd line:
C:\sc.exe GetKeyName DisplayName
Example
C:\sc.exe GetKeyName “Windows Services Timer service”
will return Name = SPTimerV3
You can then use this name in your batch files i.e.
net stop “SPTimerV3”
net start “SPTimerV3”
I’ve been looking for a list of know issues in the SharePoint 2010 beta for a while now. There is now a list on the Microsoft SharePoint Developer Documentation Team Blog. Hopefully this will be kept up to date. Click through for full story.
Microsoft SharePoint Developer Documentation Team Blog : SharePoint 2010 Beta Release Known Issues
Good post from Chris at CJG: I’ve come across the same issues but CJG beat me to the blog:
Ok, the two most important things for you to check if something is NOT working in SharePoint 2010
That will solve ALOT of your problems!
Chris
See CJG : SharePoint 2010 - Wait, its not working! HELP! for original post.
In a previous blog post I whinged about errors when installing the SharePoint beta on Windows Server 2008 R2. I’m happy to say that Microsoft has now provided the WCF Hotfix to fix the allowinsecureTransport bug. To download it click here Be sure to read the whole story on the SharePoint Team blog.
I expect someone has been working very hard to get this fix out so quick, so…thank you.