# Tuesday, 25 July 2006

To get the lady back without reinstalling take the following steps:

Delete camcurve2.bin from C:\Program Files\Nikon\NCapture4\Control and the original image will be restored from camcurve.bin.

Tuesday, 25 July 2006 09:45:24 (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Tuesday, 09 May 2006

Well after a bit luck I have found a solution that was quite simple. I tried this once before but did not save (overwrite) the new selection - it worked perfectly this time:

Use NTbackup to remove Recovery Storage Group reference from the backup selection script.


a. Start -> Run -> NTBackup -> Advanced Mode -> Backup tab -> Job -> Load Selections.

b. Select Small Business Backup Script.bks

c. Click OK on the error message:
"Some invalid selections found in C:\Program Files\Microsoft Windows Small
Business Server\Backup\Small Business Backup Script.bks".

d. Job -> Save Selections (overwrite --> Small Business Backup Script.bks)

 

Who knows, have to try it on offending client's box soon.

sbs
Tuesday, 09 May 2006 11:26:18 (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Monday, 03 April 2006

Microsoft today (3 April 2006) a new price for Virtual Server R2 Enterprise Edition - £0/$0.  See the press release here.

All that's required is registration and an agreement to allow Microsoft (ore one of its third party agents) to contact you no more than three times for feedback.

Linux machine additions are available here, additional Linux to follow.

Download Microsoft Virtual Server R2 Enterprise Edition.

Monday, 03 April 2006 22:37:21 (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback

Symptoms

Type: Error
Source: Windows SharePoint Services 2.0
Category: None
Event ID: 1000
Description:
#50070: Unable to connect to the database STS_Config on <server_name>\SharePoint. Check the database connection information and make sure that the database server is running.

Cause

This issue may occur when the SharePoint Timer Service tries to contact the configuration database when the computer starts or shuts down. By default, the configuration database in Windows SharePoint Services is named STS_config.

Resolution

The error message that is mentioned in the "Symptoms" section does not affect the functionality of Windows SharePoint Services or of Windows Small Business Server 2003. If you can connect to the Windows SharePoint Services Web site successfully, you can safely ignore this error message.

Workaround

To work around this issue, add the DependOnService registry entry to the following registry subkey on the server, and then set the DependOnService registry entry to MSSQL$SHAREPOINT:

Key:    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SPTimer
Type:  String
Name: DependOnService
Value: MSSQL$SHAREPOINT

Links

http://support.microsoft.com/?id=840685

sbs
Monday, 03 April 2006 13:30:43 (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Sunday, 02 April 2006

To allow large attachments to be uploaded add change of override the MaxRequestLength parameter in Machine.config or Web.config.  For instance I added the following value to Web.config to allow uploads of up to 8MB:

<httpRuntime maxRequestLength="8192" />

So the full line read:

<httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="8192" />

See http://support.microsoft.com/default.aspx?scid=kb;en-us;Q295626

Sunday, 02 April 2006 14:39:37 (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback

 

Dell lists this (and other Event IDs) as normal and to be ignored! See ImpInf0.pdf (4.88 MB).

sbs | win
Sunday, 02 April 2006 14:32:49 (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Saturday, 01 April 2006

827603 Remote users cannot see a Windows Small Business Server 2003
computer in My Network Places
http://support.microsoft.com/?id=827603

isa | sbs
Saturday, 01 April 2006 02:47:44 (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Thursday, 30 March 2006

Backup Companyweb using Smigrate on the source server:

  1. Click Start, and then click Run.
  2. Type CMD and click OK.
  3. In the Command Prompt, type cd %ProgramFiles%\Common Files\Microsoft
    Shared\web server extensions\60\bin, and press ENTER.
  4. Type smigrate -w https://companyweb:444 -f c:\backup.fwp, and press
    ENTER.
  5. Copy the file to the C:\ drive of the second server.


Restore Companyweb using Smigrate on the new server:

  1. On the new server, click Start, point to All Programs, point to
    Administrative Tools, and then click SharePoint Central Administration.
  2. On the Central Administration page, under Virtual Server Configuration,
    click Configure Virtual Server Settings.
  3. On the Virtual Server List page, click the companyweb.
  4. On the Virtual Server Settings page, under Virtual Server Management,
    click Remove Windows SharePoint Services from virtual server.
  5. In the Remove Windows SharePoint Services section, select Remove and
    delete content databases, and then click OK.
  6. Click OK twice to continue.
  7. On the Central Administration page, under Virtual Server Configuration,
    click Extend or upgrade virtual server.
  8. On the Virtual Server List page, click the companyweb.
  9. In the Provisioning Options section, select Extend and create a new
    content database.
  10. On the Extend and Create Content Database page, in the Application Pool
    section, select Use an existing application pool, and then select
    DefaultAppPool (NT AUTHORITY\NETWORK SERVICE).
  11. In the Site Owner section, specify the administrator's e-mail address
    in the E-mail field.
  12. In the Database Information section, uncheck Use default content
    database server, and type STS_ServerName_1 in the Database name field.
    Click OK.
  13. Close the IE Windows when Companyweb virtual server is successfully
    extended. Do not connect to http://companyweb and apply a site template at
    this point.
  14. Click Start, and then click Run.
  15. Type CMD and click OK.
  16. In the Command Prompt, type cd %ProgramFiles%\Common Files\Microsoft
    Shared\web server extensions\60\bin, and press ENTER.
  17. Type smigrate -r -w https://companyweb:444 -f c:\backup.fwp, and press
    ENTER.
  18. When the command is finished, click Start, and then click Run.
  19. Type http://companyweb, and click OK. All the site content should be
    restored.

 


 

sbs
Thursday, 30 March 2006 11:56:01 (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback

The question mark indicates that the client user name has not been authenticated. This happens when a request arrives from a Firewall client, but the firewall policy does not require authentication. The Firewall client always sends the user name, and therefore it is always logged.

See: http://www.microsoft.com/technet/prodtechnol/isa/2004/plan/faq-monitoring.mspx

isa
Thursday, 30 March 2006 00:41:34 (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Sunday, 26 March 2006

This seems to be post SP1 in Virtual PC 2004...

New guest OSes start with the error:

"The network adaptier with address "00:00:00:00:00:00" of virtual machine <name> failed to initialize becaule the address is a null address"

Two solutions seem to be:

  1. Add "<ethernet_card_address type="bytes">000*********</ethernet_card_address>
    <is_dynamic_assignment type="boolean">true</is_dynamic_assignment>" to the .vmc file, or
  2. Follow suggestion at  http://blogs.msdn.com/virtual_pc_guy/archive/2005/01/17/354971.aspx, shown below.

 

 

Virtual PC SP1 Networking problems (address "00:00:00:00:00:00" failed to initialize)

There have been a number of people reporting that when they start a virtual machine - they get the following error:

The network adapter with address "00:00:00:00:00:00" of virtual machine "...." failed to initialize because the address is a null address.

To fix this problem you should use REGEDIT to:

  1. Examine the key value at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\<nnnn>\DriverDesc to locate the desired host adapter where <nnnn> is a four digit number.
  2. Look at the GUID value for the NetCfgInstanceId key value.
  3. Add the DWORD key at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VPCNetS2\Parameters\Adapters\<guid>\Flags and set the value to 0 where <guid> is the GUID found in step 2.
  4. Restart the computer.

This registry value was added in Virtual PC SP1’s Virtual Machine Network Services driver. It is supposed to be setup during installation by the driver’s notify object. However, under certain circumstances the notify object of the old version is used during the installation of the new version and this registry value is never created. It is used by the driver to determine if a particular host adapter can be used in the MAC address generation algorithm. If the key is not present, we assume that the host adapter cannot be. In the case you experienced, none of your adapters appear suitable as a basis for MAC address generation and the driver returns a NULL MAC address which causes VPC to report the error.

Sunday, 26 March 2006 13:05:07 (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback