After moving your MOSS log files (etc. c-drive to d-drive) around, you are possible missing few folder permissions. Your MOSS log files are not deleted and are filled with the error in the title.
Add MODIFY rights to LOCAL SERVICE account in the new logs-folder and your error should be history.
I had an old WSPBuilder project and I wanted to add workflow to it. The old project was created with WSPBuilder project template and with .Net Framework 2.0.
For people who are not interested in my strugle with this problem, skip these first 12 steps 
For others, these are the steps I had to go through:
And here is the same info in a nutshell:
Is your virtual harddrive running low on free disk space? I have created many 20-30 GB VHD’s (accidentally or was it even some kind of default in Virtual PC 2007?) to contain Windows Server 2008, MOSS 2007 and so on… Sooner or later the hard drive is running out of space just when you’d need to install Infopath or Visio (Insert anything important here that currently stops you from doing your job) or something like that.
There is a small but very usefull program from vmToolkit called VHD Resizer. The tool can be downloaded freely, but requires registration. The tool creates exact copy of your existing VHD-file and at the sametime you can expand your VHD file to maximum of 127GB (VHDResizer seems that it could make it bigger, but Virtual PC said maximum is 127GB).
Notice! This works only for Vista/Windows7/Server2008, with earlier OS’s you need to use Diskpart.exe from the command line. Command line syntax for that can be found here. The basic syntax is like this:
extend [size=n] [disk=n] [noerr]
disk=n : The dynamic disk on which to extend the volume. An amount of space equal to size=n is allocated on the disk. If no disk is specified, the volume is extended on the current disk.
noerr : For scripting only. When an error is encountered, specifies that DiskPart continue to process commands as if the error did not occur. Without the noerr parameter, an error causes DiskPart to exit with an error code.
I got these errors when starting both Search Services from sharepoint central admin. The problem occurred because I just defined the username, not the computer name or domain name. The services started working after I entered username like domain\username.
I have this problem in my environment, but still haven’t quite figured it out. Event log shows error every 30-60 seconds and the error is like this:
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Launcher Service
Event ID: 6102
Date: 8/10/2009
Time: 8:00:00 ÁM
User: N/AComputer: server1
Description: LoadBalancer.RegisterLauncher failed: Unable to connect to the remote server
Here’s a list of different possible solutions to this problem:
This new feature is adds a great value for users, because now one does not need to keep the program visible to see the progress of any process (Report, web service call, download etc…) This feature is implemented already at least in the Internet Explorer 8 (Windows 7 version) and the file explorer (copying/moving).
Using the Windows7APICodepack to implement this feature is very easy and fast task. Here’s an example:
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 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 | using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Linq; using System.Text; using System.Windows.Forms; using Microsoft.WindowsAPICodePack.Taskbar; namespace TestingStuffOut { public partial class Form1 : Form { Timer timer; int value; public Form1() { InitializeComponent(); timer = new Timer(); timer.Enabled = true; timer.Interval = 250; timer.Tick += new EventHandler(timer_Tick); timer.Start(); progressBar1.Style = ProgressBarStyle.Blocks; progressBar1.Minimum = 0; progressBar1.Maximum = 100; progressBar1.Step = 1; value = 0; } void timer_Tick(object sender, EventArgs e) { // Reset the counter when it reaches maximum if (value == progressBar1.Maximum) value = 0; else value += 10; progressBar1.Value = value; // Here's the Taskbar Progressbar part TaskbarManager.Instance.SetProgressState(TaskbarProgressBarState.Normal); TaskbarManager.Instance.SetProgressValue(progressBar1.Value, progressBar1.Maximum); } } } |
And the example looks like this:
Normal mode
Error mode
Paused mode
There was also a indeterminate mode (continuous), but I did not have time to test it also (means, I did not get it to work after one try and it’s very late )
Be sure to check out other parts of the “Testing It Out” series from the series starting page!
I don’t do much pure Windows development. I’m more of a sharepoint guy myself, but these new Windows 7 features got me to boot up my visual studio and start testing these features out. When I started searching information about these features and using them in my programs, I found out that there is an API code pack for .NET Framework, because these features are not yet implemented directly to it.
Things to do before you can use these new features through API code pack:
I’ll update a list of “Testing It Out” series here:
If you have used WLM with earlier MS operating systems, you may have gotten used to the small WLM icon at the notification area (lower right corner). After installing Windows 7, the icon does not go to the notification area, but instead goes to the task bar 
The icon does not go away until you completely close messenger (and we all know how it does not like to do that). Here’s a picture:
Picture of WLM in Windows 7
If you want it to work like it used to work in Vista or XP, all you have to do is this:
Just kidding…Here’s how it should look after the changes:
Picture of WLM in Windows 7 in XP compatibility mode
For the last few days I have constantly refreshed and checked my MSDN Subscription RSS feed (and double checked the web page, just to be sure) to know when the Windows 7 and 2008 server R2 is published… And now my long wait has been answered!
Windows 7 can be downloaded from MSDN today, but some of us still need to wait. Rest of the release schedule can be found from Windows Team Blog. Windows 2008 server R2 is still nowhere to be seen
Downloads currently available only for MSDN users, but non-MSDN users will be able to download the packages on wednesday!
Info about the new features and download links can be found here.