I went to move a db from a sql 2000 to a sql 2005 developer edition database yesterday. I detached the database from enterprise manager then attached it using the new do it all app whose name I forget right now. Next time I opened the configuration app I got an XML related error with the message “Object reference not set to an instance of an object”. Some searching on the net only found solutions related to visual studio. I noticed some recommendations to run “aspnet_regiis.exe -i” in the %windir%\Microsoft.NET\Framework\v2.0.50727 folder, but that didn’t do much. There were a ton of .NET results though. I checked windows update and saw that automatic updates hadn’t been installing because windows installer 3.1 wasn’t installed (this is a bad, bad thing), ran through updates which included a .net update, a reboot, and everything was fine again.
Recent Posts
- Dependant Paradigms
- Amazon ELB requires CRLF for HTTP Requests
- an evening with Munin graph aggregation
- Setting a permanent Windows Hostname on EC2
- Configuration Management vs Meatcloud: 5 reasons CM wins
- Moar unofficial chef 0.7.16.2
- Got recursion not available and Cisco SSL VPN
- Chef 0.7.16wt1 fork and more 0.8 alpha notes
- knife, or, my tool is actually a library
- Error 80070005 accessing SSIS/DTS on SQL 2008 and Server 2008
Archives
What I'm Doing...
- I know its nice out, but if I take @SoundTransit Link to Beacon Hill to water for @Alleycat_Acres, I get bike AND transit! 10 hrs ago
- @seabikeblog @seatransitblog good start: http://seattletimes.nwsource.com/html/localnews/2011916843_bikehazard21m.html @MikeLindblom 11 hrs ago
- @seabikeblog http://thepapernoose.blogspot.com/2010/07/waiting-for-train-at-lucile.html AWS over Argo Yard detour 16 hrs ago
- More updates...
Posting tweet...
Powered by Twitter Tools.
0 Responses to “stupid sql 2005 notes”