April 2005 - Posts
My ASP.NET Tab in IISMgr went missing when I installed Beta 2. I got quite upset at first thinking that we dropped this but it was due to some extra registry entries
I found this on the MSDN Product Feedback site and it did the job.
Microsoft comments: If a previous version was not uninstalled correctly, please regedit eliminate all versions except 2.0.0.0 in the following locations:
HKEY_CLASSES_ROOT\CLSID\{7D23CCC6-A390-406E-AB67-2F8B7558F6F6}\InprocServer32\
HKEY_CLASSES_ROOT\CLSID\{FD5CD8B1-6FE0-44F3-BBFB-65E3655B096E} \InprocServer32\
HKEY_CLASSES_ROOT\CLSID\{FEDB2179-2335-48F0-AA28-5CDA35A2B36D}\InprocServer32\
When installing the framework SDK the quickstarts require you to run config on it before the websites http://localhost/quickstarts (or localhost/quickstartsv2 for V2) work properly. I ran this config and went off to a meeting. I came back and it was done. Now I try to browse to the site and I get a 404. I check IIS and the file system and everything seems ok. I checked the IP restrictions in IIS and even “allowed all”. Still no luck.
Finally a brainwave. Good ol Sharepoint (or Windows Sharepoint Services in my case) has probably taken over. WSS runs in FX 1.1 and ASP.NET2.0 is v2.
Steps to recover.
1) Exclude the quickstarts dir from sharepoint by running stsadm
Do this by
-
Open a Command Prompt and change directory to the %ProgramFiles%\Common Files\Microsoft Shared\Web Server Extensions\60\BIN directory.
-
Run the following commands to exclude the QuickStart Web applications:
STSADM.EXE -o addpath -url http://localhost/QuickStartsv2 -type exclusion
2) Goto web.config for the quickstarts and a <trust level="Full" originUrl="" />. The trust might be less but this does work
And off you go. Maybe this will save you some time
Note -- you need to something similar for Reporting Services. Most of the above occurs since VSTS needs WSS (and right now I cannot figure out if VSTS will work if WSS is not on port 80).
VS05 and SQL05 are finally installed and I had a hiccup a 2. The biggest hiccup was a small issue but had lots of dependencies and hence pain.
First thing was that I installed SQL05 first. I do not have much space on my C drive so opted to install on my E drive. Unfortunately there was one component (the dev tools component) that remained at the default of C:\. You need to change either subcomponent explicitly. This caused a problem when I tried to install VS05. VS05 setup complained that as I already had the dev tools component installed in the C: drive I could not change to E: drive. So I had to go off an uninstall the SQL05 tools component. I could then go ahead and install VS05 on my E: drive. I later had some issue when trying to open up the SQL BI project in VS bit a reinstall and making sure I selected the E drive this time made sure this all worked.
LESSON -- if you can install everything on the C: drive. Makes life a lot easier. I regret partitioning my drives now :-)
Above was actually the minor “problem“
During SQL installation an error popped up which I just ignored. This had to do with Reporting Services. I uninstalled Reporting Services and reinstalled an no error came up -- so I assumed all was ok. I happily decided to start the VSTF (the server portions of VSTS) installation. This complained that OLAP and reporting services was not started. OLAP started fine but not RS. Checked the event log and had this error.
Service cannot be started. System.TypeLoadException: Could not load type 'Microsoft.SqlServer.SqlDumper.DumperFlags' from assembly 'ReportingServicesNativeClient, Version=0.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'.
So I reinstalled. Still no luck!!. - could not nothing via Google, MSN or internal searches. Then I thought about this simply. Does this error make sense. I opened up ReportingServicesNativeClient in VS and looked in the obhect browser. The type DumperFlags was there. So next logical thing -- where does the Framework look first -- the GAC. Lo and behold a ReportingServicesNativeClient v0.0.0.0 was in there. How it got there -- who know. Removed it and voila Reporting Services started.
And I thought I was done -- not yet. It turns out then when I reinstalled Reporting Services it does not do the full config in terms of creating the databases and setting the virtual directories etc. I tried to use the RS Config Mgr but after many attempts gave up. I decided to go through the path of least resistance -- a full SQL uninstall and reinstall. I uninstalled all the SQL bits and got an error or 2. I started a SQL reinstall of everything. Just when things looked good an error during installation -- something to the effect that an instance already existed. Did some hunting in the registry and removed the reg key under HKLM/Software/Microsoft/SQL Server/90 (something along this line) and any instance info in reg path.
I removed all the parts that did get installed and started an install again. This time all worked (and you gotta wait since some of the BOLs are big). Ultimately at 10:30PM last evening we had success. (the process above started around 7:30pm). Started a defrag and went to sleep.
We know most of you guys are busy and sometimes find it tough to attend events or browse through the documentation. Check out http://msdn.microsoft.com/elearning/. I first read about this and as the page says “Our contest grabs your attention,Our content will keep you coming back“ I thought I could enter. Having looked at the rules though MS employees cannot win which makes sense. I thought anyone else could until I double checked and I saw that the prizes are only open to developers in the US - pity :-(. I will let them know.
None the less, do what I did and check out the content. It is a nice simple structure and does not try to overwhelm you with content. Spending about 30-60 minutes on the site should be quite fruitful
Yep - the day has come. I have not bothered much with getting the CTP builds etc downloaded and installed (I sometimes got a VPC and played with that) but now the time has come.
The process actually started on Saturday when I dialed, connected to a Terminal Server and started the download (and hoped I was getting the right bits!!). By Sunday it looked like the download was done except it did not seem to have MSDN docs so I started a different download.
I then put in a drive I use for beta stuff. Turns out I think I last used this drive about 6 months ago so could not remember my domain password. Thankfully I remebered by Admin password. The one thing I have learnt over the years of playing (and demo'ing) beta stuff is that you should spend lots of time cleaning the machine -- and as it is beta this is not always a simple thing. Anyone hoping to download just run setup will probably be disappointed. I removed the old stuff including MSDN docs, SQL05, Reporting Services, Integration Services, SQL05 etc etc. I used some blog postings on blogs.msdn.com to help on this (hopefully a follow up post on this) especially the framework did not look like it cleanly uninstalled.
Right now I am installing SQL05 off a mounted ISO image. Hopefully I blog a bit more on the steps I had to take (like removing services that did not get removed on uninstall) through the week.
See http://www.microsoft.com/southafrica/devdays/default.mspx for details on agenda and speakers. We have members from the product team coming out to deliver some sessions