Tuesday, January 18, 2005

To Install Avalon and WinFX on Windows server 2003

Free pre-release download of Avalon and Visual Studio

SUMMARY:Microsoft has released a free pre-alpha copy of Avalon and Visual Studio Express for public download.

DEFINITIONS FOR NEWBIES LIKE ME:
Pre-Alpha - A version of software still under development, which means this version's API isn't 100% permanent.
Visual Studio Express - A lightweight version of Visual Studio for C# or Visual Basic.
Avalon - Microsoft's next-generation UI platform that runs on WinXP, Win2003, and Longhorn.WinFX -

I couldn't find a one-sentence definition on the web, so here's mine...
WinFX is Microsoft's next-generation API for building Windows applications, all based on the .Net 2.0 managed code framework. WinFX consists of several parts, and Avalon is a part of WinFX. Visual Studio is the best tool for writing WinFX applications in C# or Visual Basic.
SDK - Acronym for software development kit, which usually contains code samples, tools, and documentation for writing software. The WinFX SDK contains all those things for writing software based on WinFX technology.
Avalon CTP - Acronym for "Avalon Community Technology Preview". It includes WinFX SDK, .Net 2.0 Framework, and Avalon. It doesn't include Visual Studio, which you have to install separately.

DOWNLOADS:
Avalon with WinFX - http://www.microsoft.com/downloads/details.aspx?familyid=C8F904E1-B4CA-402B-ACCF-AAA2BD60DA74&displaylang=en
Visual Studio C# Express - http://lab.msdn.microsoft.com/express/vcsharp/
Visual Studio C# Express - http://lab.msdn.microsoft.com/express/vbasic/

INSTALLATION SEQUENCE:
I messed up on the sequence of installation steps, so I wrote down a clearer set of steps for myself:0. Make sure you've uninstalled the ".Net 2.0 Beta 1 Framework" if you had previously installed an earlier version of WinFX. Skip this step if this is your first time installing the WinFX SDK on this machine.

1. Download and install Visual Studio C# Express. Make sure you install it in the default directory.
2. Download the "Avalon CTP" installer and run it.
3. Burn a CD with the "en_winfx_sdk_ctp.iso" file after you've run the avalon ctp installer. (To avoid burning a CD-ROM, you can use the "Daemon Tools CD emulator" to access the iso file as a virtual CD drive if you know how from http://www.daemon-tools.cc, but run third-party software at your own risk).
4. After accessing the CD-ROM, a startup HTML page will appear. Click on the "Installation" link.
5. Skip the step for installing .Net 2.0 because it was automatically installed with Visual Studio C# Express from step 1.
6. Install Avalon.
7. Install the WinFX SDK.
8. Run the batch file named "ConfigureAvalonForExpressSKUs.cmd" from your Avalon CTP folder to get Avalon project templates in Visual Studio.
9. From Start menu, access Programs/Microsoft WinFX SDK/WinFX SDK Documentation.10. Start reading from the top, and follow the samples :-)

Whew, that's a lot of steps. Last year, it was more complicated, so this is an improvement, but I hope they simplify it even more in the future!

Wednesday, January 12, 2005

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

I was excited to install SQL Server 2005 Beta 2 on my Win2k3 Server.

The 2.0 Framework, SNAC, and Support files appear to go on fine. Our install failed at the point where the Setup Consistency Checker (SSC) was supposed to run.

Microsoft SQL Server 2005 Beta 2 Setup
---------------------------
The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine Error:2147749907 (0x80041013).

I also saw this in a log file;

Windows Management Instrumentation (WMI) is not functioning properly. Further checks cannot be performed. Action: Please make sure Windows Management Instrumentation (WMI) is functioning properly. The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine Error:2147749890 (0x80041002).

First, to get out on the table the environement:

Server: Win2003 server Enterprise
Yukon: SQL Server 2005 Beta 2
Other installed programs: Only SQL 2000 at the SP3a level


To fix this ‘kind’ of error, there are some classic files to look for, and rename them. Of course these only exist if a Yukon install had been performed or even tried. And in my case Yukon had never been attempted, but nevertheless I checked to make sure these files were not present, and they were not.

mmc.exe.manifest
w3wp.exe.manifest
inetinfo.exe.manifest
dllhost.exe.manifest
wmiprvse.exe.manifest

Next, there are a bunch of things that can get messed up on a server’s OS that could later cause WMI problems, here are some of the usual suspects that you can run to fix this type of problem, but in my case they did not help.

StartRunCommand

secedit /configure /cfg %windir%\repair\secsetup.inf /db secsetup.sdb /verbose
Mofcomp.exe %windir%\system32\wbem\cimwin32.mof
Regsvr32 wbemupgd.dll
regsvr32 wbemsvc.dll

At this point I was desperate, so I actually uninstalled and reinstalled the Windows Server 2003 SP1 and reinstalled it, but alas, to no avail. Remember, for Itanium boxes, you must have SP1 on if you want to install SQL 2005. But the reinstall did not help. Bummer.

But then Niko from the SQL Server Setup Team came to the rescue and suggested I try this:

wmiprvse /regserver

or
try this

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

And lo and behold, my Yukon (SQL Server 2005) went on smooth as glass. Turns out some WMI folks over in Microsoft passed that little tid-bit onto him.

I found out that this is an active bug in Windows Server 2003 for RTM to SP1 upgrades where it screws up WMI, so as a public service, I want to pass this on.

I’m sure MS will get this straightened out before they go golden with SP1.

Thankx to www.MSNSearch.com


Wednesday, January 05, 2005

check these links abt Sharepoint server

http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx
http://home.salloway.org.uk/mceblog/
http://www.sharepointexperts.com/
http://www.gotsharepoint.com/resources/resourcekit.asp
http://www.msd2d.com/
http://www.sharepointcustomization.com/default.aspx
http://www.sharepointcustomization.com/demos/webcasts/SharePoint%20Portal%20Server%202003%20Object%20Model%20and%20Web%20Services/default.htm
http://www.axosoft.com/products/ontime_whatsnew.aspx
http://www.axosoft.com/products/downloads.aspx
http://www.iwug.net/
http://www.sharepointcustomization.com/sps/default.htm
http://www.flickr.com
http://www.remotesoft.com/
http://microsoft-exchange.com/
http://www.microsoft.com/sharepoint/downloads/components/results.asp?s=5