If anyone is thinking of installing Vista, but would like to still be able to use Virtual Server, I can confirm that Virtual Server R2 SP1 Beta 2 runs great on the RC1 build under IIS 7. I am running on a dual-core AMD x64, and it currently only has 1GB of RAM while I wait for an upgrade to arrive. This is a great way to use Vista, but maintain assured compatability with existing solutions/software via virtual machines.
The last two times that I have installed Virtual Server R2, it has been SP1 Beta 1 and then Beta 2. Each time the install was simple, but when I first attempted to navigate to the Admin homepage, I recieved a login prompt. Very frustrating, to say the least. Each time I have resolved it by Googling and it was a pain to find the (simple) answer. The answer is easy: Add the address of the panel to your "Intranet Zone" in IE. This is an IE issue, not a Virtual Server issue from what I can tell. Here is the link
that helped me out and that explains the problem. I am putting this blog out here so that when I look for it again, it will be right here waiting for me.
I have had this error twice now with SQL 2005. Each time has been after I had to reload windows (laptop is getting flaky. . . ). I am basically posting this for my own future reference, but if anyone ever gets an error similar to the one below which indicates that OLEDB is not a valid connection manager type, there is a fix for it:
Error 1 Error loading ETL - MyPackage.dtsx: The connection type "OLEDB" specified for connection manager "My DB" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type.
It is all explained in this SQL 2005 forum post (scroll down and find the post made Dec 24 2005 at 3:58 am by Micahel Entin from the SSIS team). Essentially what happens is that some program other than SQL 05 changes permissions on registry keys that SQL depends on being able to access internally from a low-privelege account. Michael provides a script that can be compiled as a command line program in .NET that will identify the keys for which the permissions have changed so that you can change them back.
New updates to SQL Server 05 samples, plus now a blog about them here: http://blogs.msdn.com/bonniefe/default.aspx Here are the samples: http://www.microsoft.com/downloads/details.aspx?familyid=E719ECF7-9F46-4312-AF89-6AD8702E4E6E&displaylang=en
My buddy Dave has been building sites based on Community Server 2.0 like it was going out of style. He loves the power and flexibility. A couple of his sites are Xbox 360 Poker and 360 Deals. He's actually having a Gamer Score Whore contest over at 360 Deals for a free game (apparently that's a term from within Microsoft according to Major Nelson). If you are interested in seeing how your Gamer Score stacks up against everyone else, there is a cool site written in .NET that will tell you (they must pull in gamertag info from a web service?) called Top 360 Tag. Here is a link to my gamer tag stats.
I recently had to reload Windows XP on top of my existing XP install due to a corrupt hard disk. Just when I thought that everything was fixed, I realized that both Virtual PC and Virtual Server had stopped connecting to my physical wireless network card. Unless I wanted to run a 25 foot cable, I had to figure it out. The error that I received from Virtual Server was not much help:
Unexpected error (0x80004005). The virtual network’s configuration information could not be retrieved. Microsoft Virtual Server could not complete the operation due to an unexpected error (0x80004005).
The one thing that I gathered from this error was that somehow Virtual Server could not get the information for my physical wireless NIC. When I booted any virtual machine, I wasn't getting any errors other than the fact that none of my virtual NICs could get an IP address. After find this post on a blog, and this post on a newsgroup, it sounded like all I needed to do was uninstall-reboot-reinstall-reboot and everything would be fixed. That worked fine for VPC, but not the case with Virtual Server 2005 R2.
I finally figured out after numerous uninstalls that the problem was that during my reload of Windows XP, I had removed and reinstalled the physical device for my NIC card. Apparently that had given it a different ID under the hood, and the old WirelessNICCard.vnc file that Virtual Server 2005 was using to reference that physical wireless NIC was pointing in the wrong place now.
The final solution was to remove the old .vnc file from underneath the Virtual Networks config on Virtual Server and Create a new one - my updated wireless NIC was in there, I easily created the file and assigned it to virtual machines and everything worked fine. I wonder if that would have solved the problem for the people in the posts above as well? It sounds like when you change a physical NIC for another of the same name or model but re-install the drivers, the .vnc file doesn't always point to the new one since the ID changes under the hood? At any rate, I hope that this post helps someone else with the same problem down the road.
This is a very handy add-in that helps IE become a better tool for developers. This is the kind of thing that Firefox is known for, I'm glad to see that IE has an add-ins like this.
Here are some of the features in this release:
The Internet Explorer Developer Toolbar provides several features for exploring and understanding Web pages. These features enable you to:
-- Explore and modify the document object model (DOM) of a Web page.
-- Locate and select specific elements on a Web page through a variety of techniques.
-- Selectively disable Internet Explorer settings.
-- View HTML object class names, ID's, and details such as link paths, tab index values, and access keys.
-- Outline tables, table cells, images, or selected tags.
-- Validate HTML, CSS, WAI, and RSS Web feed links.
-- Display image dimensions, file sizes, path information, and alternate (ALT) text.
-- Immediately resize the browser window to a new resolution.
-- Selectively clear the browser cache and saved cookies. Choose from all objects or those associated with a given domain.
-- Choose direct links to W3C specification references, the Internet Explorer team weblog (blog), and other resources.
-- Display a fully featured design ruler to help accurately align and measure objects on your pages.
The Developer Toolbar can be pinned to the Internet Explorer browser window or floated separately.
This Beta 2 version of the toolbar contains functionality and stability enhancements over previous versions and includes the following improvements.
-- You can now selectively enable and disable CSS parsing.
-- The Misc menu contains a color picker.
-- Several link reports are available.
-- When you select an element in the DOM element tree list, the selected element scrolls into view if it is not already visible in the browser window.
In case you need to run a sample that relies on Northwind or Pubs yet you are using SQL 2005, you can download those classic sample databases directly from Microsoft here:
I had to re-install Windows on my laptop today due to some disk errors. Once I was back up and running, I found that 99% of SQL 2005 worked fine, but SQL Server Configuration Manager had stopped working and gave the following error in a dialog box:
Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 servers with SQL Server Configuration Manager.
Invalid class [0x80041010]
Unfortunately that error does not tell you what to fix. Fortunately Eric Charran does tell you what to fix. You can find the answer on his blog here: http://blogs.msdn.com/echarran/archive/2006/01/03/509061.aspx. I had not dealt with .mof files before now, but his fix did the trick in about 2 seconds. Thanks Eric!
If you are working with SQL 2005 and/or .NET 2.0, you should definitely check out the December update for SQL 2005 Books Online and the update for the Samples that come with SQL 2005. Here are a few of the new things that come with the updated samples: CLR, SMO, Integration Services, Replication, and Reporting Services.
The SQL 2005 Feature Pack was released in late November and contains tools and utilities that weren't ready in time to ship with the SQL release, a lot of them add the ability to work with SQL 2000 components from within SQL 2005, such as DTS.
More Posts Next page »