Parallel Port Driver Service - parport

I have been some trusty Windows Server 2003 VMs from Virtual Server 2005 across to Windows Server 2008 R2 Hyper V this week and without fail each of them has given me the boot message "At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details."

Error - At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details. 

Now I expect this when network adaptors have yet to find their drivers as all sorts of things fall over, but even once the devices were all happy and working the prompt persisted - checking the event logs showed that the Parallel port driver service failed to start - I didn't think you could get parallel ports on VMs! :)

Anyhow, thought I'll check the services MMC and disable it - but it was not to be found there. A quick search later revealed some posts suggesting I tweak registry values to stop the service ; but I don't like doing that sort of thing, especially when this one is a DC. So fiddled around with command line options for services and found that the answer is one line in a dos prompt thus:

 sc config parport start= disabled

Simple, by the third VM I managed to remember it without looking at the help!

 

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Moss Timer Jobs - What do they do?

I came across an interesting post from Mark Arend today whichi nicely lists out all the Moss Timer Jobs with a description of what they do along with some assembly info, catch it here:

http://blogs.msdn.com/markarend/archive/2008/09/06/list-of-moss-timer-jobs.aspx

It was posted a while ago. But hey this way I'll find it again easily.

IainW

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

A public update for the Service Pack 2 expiration date issue is now available

Over on the SharePoint Team blog they have published details of an update that resolves the product expiration issue with SP2. A quick quote from their blog:

The update can be applied before or after Service Pack 2 installation.  If the update is applied prior to installing Service Pack 2 it will prevent the expiration date from being improperly activated during installation of Service Pack 2, if it is applied after Service Pack 2 it will remove the expiration date incorrectly set during installation of Service Pack 2.

Also they plan on releasing an updated SP2 package that doesn't exhibit this problem, time to update my slipstreamed install sources...

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Add the BIN folder to the path environment variable with powershell

I often go to execute a stsadm command and find it is not in the path on the server I am working on, so I looked for a while of a way of adding it permanently through powershell and then realised it's a straightforward task with .NET code. The following will add the BIN folder within the program files structure to the PATH environment variable at local machine level so that all users will benefit.

   1:  $envpath = [environment]::GetEnvironmentVariable("Path","Machine")
   2:  $binpath = $env:Programfiles + "\Common Files\Microsoft Shared\web server extensions\12\BIN"
   3:  if ($envpath.contains($binpath) -ne $true ) {
   4:  $envpath = $envpath + ";" + $binpath
   5:  [environment]::SetEnvironmentVariable("Path",$envpath,"Machine")
   6:  Write-output "BIN Path added."
   7:  }
   8:  else
   9:  {
  10:  Write-output "BIN Path already added."
  11:  }

I have added a check to not add it if it is already present as the traditional method of using

SET PATH=%PATH%;C:\Program files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN

ends up with multiple copies of the BIN path in the variable and only applies for the current session.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Multihomed IIS Servers

 

I was setting up a staging server this week to demo some our projects and products to clients, and ran into a situation where the external address seemed to stop responding. Initially I thought it was a firewall issue, but that all checked out ok and locally the server would supply pages to the url I was testing but not remotely. I wondered if I had misconfigured the networking somehow and searched for some articles on IIS & multihomed scenarios, I have one NIC set facing the internet and another facing  the local subnet. Anyhow turned out I had set the default gateway on the external NIC and the internal NIC was given it's IP via DHCP and so also gets a default gateway. D'Oh!... I found the following article gave not only a good explanation but also instructions on how to resolve it.

 http://www.shudnow.net/2009/02/01/default-gateways-and-multihomed-boxes/

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

SharePoint Best Practices Conference UK - Day 3

The final day of the conference - today I focussed on the IT PRO track – all 5 sessions. So that’s Steve Smith, Spencer Harbar, Daniel Wessels, Spencer again, Bob Fox and Brian Wilson, covering Intranets, Extranets, internet sites, search, Kerberos and Virtualising SharePoint.

Steve Smith started the day with a redefinition of WWW, as the wild wild west. It’s an open world out there and as soon as you attach your servers to the internet they’re insecure, you really don’t know who will be accessing your content or trying to do things they shouldn’t.  You have layers of security at the edge, (that may be ISA), IIS and then again at the SharePoint level, with your content  in the database and that’s what you’re delivering or protecting. I suppose it’s obvious really, but the more complex you make things in these layers, the less likely they are to be secure because of mistakes. 

They continued with best practices for your Web applications and SSL scenarios – where Spencer Harbar put in the one liner – “host headers are evil” – but it transpires  that this is only in the context of SSL, where life really is a lot easier if you use fixed IPs and stick to standard port numbers.

Daniel Wessels took us through Search Infrastructure, Architecture, Setup and Management. It seems there are varying rules of thumb for the size of your search DB, depending on which whitepaper or documentation you read, going from 2x to 6x the size of your index, but you won’t really know what that figure will be for you until you run some tests on the mix of data your farm is indexing. Looking at the servers in the farm, the maximum ratios for Query, index and DB server are 7:1:1, above that the performance actually tails off... time for an extra index server and thus another SSP to scale the capacity and performance.

For your default search content access account this really should not be a farm administrator, in this scenario both minor versions and unpublished documents will be indexed and potentially visible to end users. So although if they have not got permissions to see these versions of the documents they won’t be able to see them when clicking on the search result link, they will see the words around the keyword matched in the search results page. Another interesting point was around the content access account used for external websites, here you need to be using an account that has no permissions on your network, because if challenged the indexer will give up the account’s username and password to the external site and you really don’t want that being used to access your network do you?

During the lunch session Andrew Woodward and Alex Pearce gave us a view on some of what is happening in the education space in the UK with SharePoint and showed us a great looking interface for a VLE built with Silverlight sitting on top of the SharePoint Learning Kit for a UK Learning Gateway.

After lunch, Spencer Harbar and Bob Fox took us through setting up Shared Services and Excel Calculation Services to use Kerberos and it went well, apart from the demo on shared services causing some problems, but hey nothing like a live demo to go wrong... but there was good discussion and questions while Spence battled with IIS & SP to get it to work.

Some key pointers from the session – case matters when you are setting your SPNs, and all the SSPs in your farm must be either all NTM or all Kerberos, you can’t mix them.

Brian Wilson finished off the speaker sessions for the day covering virtualisation of SharePoint in a production farm. He addressed the issues of resource usage and how you need to look at this from both a physical and virtual perspective. A key point is that restoring snapshots of a server in the farm is not supported – you are likely to get all sorts of mess and probably database corruption as timer jobs are likely to go out of sync.

The conference was finished off with open mike sessions in all the tracks, it’s great to have the opportunity to ask the experts those questions you find really hard to get answers to. In the IT Pro track we had discussion around admin accounts, should you use a shared account among a team or assign the permissions to users  directly? Generally using a shared account is likely to end up being less secure as those details get shared around, and you would be better assigning the farm admin permissions to the users’ own accounts. This also gives you an audit trail as to who has made the changes. Large databases came up again and some of the issues around that, sometimes you have to remind people to ask the question whether data should really be in SharePoint in the first place.

A good question was how should you structure a support team? Well it depends... :) but a minimum would be one and a half people dedicated to it, so that when that one person is on holiday the half can still pick things up and know how to fix things if problems arise!

And so from SharePoint by day to SharePint by night, the guys at Syntergy gave us a pot for the beer, thanks guys! It was a good chance to chat to some more people and enjoy a beer or two or three... sadly I needed to be on the train home this evening so had to leave early.

And finally, thanks to Steve and co at Combined Knowledge, you have done a great job of this conference and we look forward to the next one...

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Crawling Exchange 2003 Public Folders on SBS 2003 from Moss 2007

Setting this up for the first time was a little challenging. I couldn't figure out why no matter what combination of settings and credentials I gave the search service it wouldn't crawl the public folders. I tried crawl rules, complex URLs, content access accounts, but eventually I gave up focusing on SharePoint options and started to look more closely at what was happening at the other end - what was exchange doing?

I had already checked the IIS settings for the public virtual directory and it showed that Basic and Integrated Windows Authentication were both enabled, so I next tried to hit the public folders URL with it in my local intranet zone so that windows would pass through my credentials automatically - just like we set up SharePoint all the time. Anyhow, I realised that no matter what I did with the IIS settings I couldn't get to the page without first entering my credentials on a form based login for OWA. I googled some more to find that although I was setting the authentication options in IIS, there are some additional settings in Exchange System Manger.

If you open ESM, then expand Servers, <server name>, Protocols, HTTP, you'll find the exchange virtual server, if you right click on the virtual server and select properties on the second tab there is an innocuous little box that says "Enable Forms Based Authentication".

So it didn't matter what I did in IIS Manager because it was overridden by the settings here. Well, someone helpfully pointed out in a forum that you can in fact create a second virtual server and set that to work without Exchange FBA. Yay! That's what I need, our existing users can keep their interaction the same on the current URLs, we'll create a new virtual server and set that not to use Exchange FBA, just Windows Integrated authentication and hopefully our crawl will work fine.

So the crawl has reached the end and 18,224 items are indexed and searchable in milliseconds. Lovely. I just need to make sure I've put all the settings back how they should be (you did make a note of all those changes you made as you fiddled in IIS, Exchange & SharePoint didn't you?) and once I'm happy that the URLs are accesible in the right places the job's done.

Currently rated 5.0 by 1 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Detaching and Attaching Content DBs - prepare to move.

Todd Carter has posted some interesting info on using stsadm -o preparetomove with a SharePoint Farm with the infrastructure update or later installed - basically you don't need to anymore - read more here.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Moss Search results pages are consistently inconsistent in returning slowly!

I've just completed a migration from SharePoint Portal Server 2003 to shiny new Moss 2007 implementation. And whilst looking for some content that had gone missing, I noticed that the search results page sometimes took 30 - 60 seconds to return the next page in the result set, whilst on other occasions it came back very quickly. My first thought was perhaps it's busy, all those users making lots of use of it! But no, processor usage on the boxes was all negligible.

As I explored this some more I discovered that it was consistently inconsistent! By which I mean that the first page of a particular query always came back quickly, the second slow, the third and fourth quickly, then the fifth slow and so on.  I think that's a quick step ( - I've been subjected to too much strictly come dancing), anyhow some digging around eventually showed up the following message in the logs:

 12/08/2008 22:32:19.57  w3wp.exe (0x1134)                        0x0EC4 Search Server Common           MS Search Query                0 High     Exception while finishing web request or starting web page read on http://search.live.com/results.aspx?q=safety&count=3&first=1&mkt=en-GB&format=rss&FORM=SHAREF: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host 194.217.240.73:80     at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)     at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)     --- End of inner exception stack trace ---     at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)     at Microsoft.Office.Server.Search.... 
12/08/2008 22:32:19.57* w3wp.exe (0x1134)                        0x0EC4 Search Server Common           MS Search Query                0 High     ...Federation.HttpAsync.RespCallback(IAsyncResult asynchronousResult) 

and

12/08/2008 22:27:35.20  w3wp.exe (0x1134)                        0x0EC4 Search Server Common           MS Search Query                0 High     Exception while finishing web request or starting web page read on http://search.live.com/QSOnly.aspx?q=safety&count=3&first=1&mkt=en-GB&FORM=SHARES&format=rss: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host 194.217.240.71:80     at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)     at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)     --- End of inner exception stack trace ---     at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)     at Microsoft.Office.Server.Search.F... 
12/08/2008 22:27:35.20* w3wp.exe (0x1134)                        0x0EC4 Search Server Common           MS Search Query                0 High     ...ederation.HttpAsync.RespCallback(IAsyncResult asynchronousResult) 

I thought it a bit strange that a federated search was being performed as there were no federated search webparts on the results page I was looking at. Anyhow it seems that by default the federated searches at Microsoft's live.com are run anyway... disabling these federated search locations in Search Administration > Federated Locations instantly gave me nice quick results all the time.  Well disabling - I added a prefix that's unlikely to get used as I thought they might come in useful when Microsoft has fixed the delay!

If you find another solution - please add a comment to let me know. Thanks.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Powershell and Sharepoint

For those that haven't yet looked at Powershell, please do. Aside from being an extremely powerful means to interact with SharePoint and control items that are not available from the web UI, it is more than likely that as with Exchange, Powershell will be the means of interacting with SharePoint v.next (as opposed to stsadm)

Some links to interesting resources and example scripts....

http://www.u2u.info/Blogs/karine/Lists/Posts/Post.aspx?ID=9

http://darrinbishop.com/blog/archive/2007/04/08/54.aspx

http://blogs.flexnetconsult.co.uk/colinbyrne/PermaLink,guid,1665700b-e0de-4b8a-bb1c-014d6fbcf2db.aspx

Powershell download

http://www.microsoft.com/windowsserver2003/technologies/management/powershell/download.mspx

Useful Powershell editor

http://www.powergui.org

 

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

 

Dilbert of the day