SQL Express installation messages

In case you just skip the post-installation messages... that may helps :P

Configuring and Managing SQL Server Express
·    For improved manageability and security, SQL Server 2005 provides more control over the SQL Server surface area on your system. To minimize the surface area, the following default configurations have been applied to your instance of SQL server:

o    TCP/IP connections are disabled
o    Named Pipes is disabled
o    SQL Browser must be started manually
o    OPENROWSET and OPENDATASOURCE have been disabled
o    CLR integration is disabled
o    OLE automation is disabled
o    xp_cmdshell is disabled

To enable or disable features and services, run the SQL Server Surface Area Configuration tool from the Start menu.

·    To install SQL Server Management Studio Express Edition, download it from the SQL Server Developer Center on MSDN (http://go.microsoft.com/fwlink/?linkid=51793).

Documentation and Samples
To install SQL Server 2005 Books Online, download them from the SQL Server Developer Center on MSDN (http://go.microsoft.com/fwlink/?linkid=51793).

To install the .NET Framework SDK, see "Installing the .NET Framework SDK" in SQL Server Books Online.

To install sample databases and code samples, download the SQL Server Samples from the SQL Server Developer Center on MSDN (http://go.microsoft.com/fwlink/?linkid=51793).

AutoIncrement in .NET and Autonumber in ACCESS

From my experience, try to avoid turning on both AutoIncrement (in DataColumn) in .NET and Autonumber in MSAccess at the same time. As somehow there is just no communication between them. They just work on their own.

For example, when you have records in ACCESS having ID (1,2,3,4) and suppose the next ID be 10 (as doing some record add and delete before). AutoIncrement in .NET just don't know about it as it's AutoIncrementSeed can just automatically set to 5.

Then 10 vs 5, I hope you can see how the problem being occurred. So avoid having them both at the same time.

Literal vs Label

When working with .NET, you may wonder the difference between Literal and Label.

Actually, when both controls are converted to become HTML, Label will add a pair of <span></span> tag, while Literal keeps everything unchanged.

So most of the time if would be better to use Literal instead of Label for the sake of simplicity.

Re-installing WMI

For those folks out there using Windows Server 2003 SP1 Build 1277 along with the SQL Server 2005 December CTP, you may be unable to install SQL Server 2005 with the following error: Microsoft SQL Server 2005 Beta 3 Setup

The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine SI4P64LF3-05 Error:2147749907 (0x80041013).

The cause of this error is a corrupt install of WMI, caused by upgrading Windows Server 2003 to SP1 build 1277. To fix this issue, copy the following into notepad and save it with either a .cmd or .bat extension. Then run the script to re-install WMI:

%SYSTEMDRIVE%
CD %windir%\system32\wbem
Mofcomp.exe cimwin32.mof
Regsvr32 /s wbemupgd.dll
Regsvr32 /s wbemsvc.dll
wmiprvse /regserver

If that doesn't work, try the info here posted on MSDN.

Ref: http://blogs.msdn.com/jpapiez/archive/2004/12/09/279041.aspx

Office 2003 SKU011.CAB problem

 

When Office2003 couldn't find file SKU011.CAB:

regedit -> [HKEY_LOCAL_MACHINE] -> [SOFTWARE] -> [Microsoft] -> [Office] -> [11.0] -> [Delivery] -> {90000409-6000-11D3-8CFE-0150048383C9} -> [CDCache] change to [0] .... Done!

Clean up a SQL 2005 instance name

A nice trick provided by Aaron Stebner
Ref: http://blogs.msdn.com/astebner/archive/2005/12/08/501885.aspx

I have heard from a few customers who have tried to uninstall beta versions of SQL 2005 and then install the final release and have run into errors with both the beta uninstall and the final release install. I have already described the most common uninstall error and a suggested workaround in this previous blog post (an error reading property "Installids" from the cache and/or an error writing property "flagCommit" to the cache).

I wanted to address one of the most common final release install errors I have seen - a duplicate instance name error that causes SQL setup to fail and rollback. It is pretty easy to tell if you are running into this error if you launch SQL setup directly and step through the SQL setup UI. However, if you are installing SQL Express as a part of Visual Studio 2005, setup runs in silent mode and you will only see a generic error bubbled up from Visual Studio setup indicating that SQL Express failed to install.

VS 2005 configures SQL Express with an instance name of SQLEXPRESS when it runs SQL setup in silent mode. It also used this same instance name in the betas, so if something goes wrong with uninstall, you may end up with an orphaned instance name on your system, and then installing the final release will fail. In this case, the verbose setup log file for SQL Express will show an error that looks like the following:

MSI (s) (AC!38) [00:01:41:056]: Product: Microsoft SQL Server 2005 Express Edition -- Error 28086. An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.

Error 28086. An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.

If you are running into an error installing SQL Express as a part of Visual Studio 2005 setup, you can check in the SQL Express log files (located at %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG). If you are receiving an error about the instance name not being unique, you can manually clean off the orphaned instance name by doing the following:

1. Click on the Start menu, choose Run and type regedit


2. Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server


3. Remove SQLEXPRESS from the REG_MULTI_SZ value named InstalledInstances


4. Delete the subhive named MSSQL.1


5. Delete the subhive named SQLEXPRESS


6. Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\Instance Names\SQL


7. Delete the value named SQLEXPRESS


8. Delete the folder %ProgramFiles%\Microsoft SQL Server\MSSQL.1

Note - the above steps apply to the instance name that is created when SQL Express is installed as a part of Visual Studio 2005. The actual instance name on your system may vary if you have had any other beta version of SQL 2005 (such as the developer edition). Please make sure to adjust the steps accordingly based on what instance name information is in your registry and file system.

DirectInput refresh

Simply remove files in:

Program Files\Common Files\DirectX\DirectInput\User Maps\*.*

Redirect Apache request to IIS

Just got some ideas for redirecting Apache request to IIS, if anyone make this work, please let me know.

RewriteEngine on
RewriteRule ^/(.*\.asp)$ http://localhost:81/$1 [P]

Usage on Weka Attribute Filter

I seldom use Weka, but just reminded me some work I did years ago...




AttributeFilter af = new AttributeFilter();
int i[] = {1,2,3};
af.setAttributeIndicesArray(i);
af.setInputFormat(data);
Instances ins = Filter.useFilter(data,af);
System.out.println(ins);




Some nice software to remember...

hddsaver.com provides some cool ways to set up a portable office in a Flash drive.

Foxit Reader: Small PDF reader

Fast stone provides images viewer and screen capturing software for free.

Notepad2 a handy Notepad replacement.