-
Posted
by
Nino
-
Last week, I attempted to install the SQL Server 2005 Compact Edition Tools for Visual Studio 2005 Service Pack 1 and received the following error message:
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.
How did I work through this issue? I did a repair on my Visual Studio 2005 [Team Suite] installation and then re-installed Visual Studio 2005 Service Pack 1. After this, I attempted the SQLce VS tools install (SSCE31VSTools-ENU.exe) again. Success!
Of course, performing a repair install on Visual Studio is something we would all rather avoid (and the SP1 re-install). By the time I went to perform the install on a second dev box, I found a better way:
From the original Visual Studio installation media, locate the \WCU folder and install SQL Mobile from there. After that is complete, retry the SQLce 2005 VS tools install. (credit to Amit Chopra from the Visual Studio for Devices team for the tip). For more, check out this thread from the sqlce newsgroup in which fellow MVP Ginny Caughey answers questions.
If you want the download links for all the SQL Server Compact Edition 2005 bits, check out my prior blog post where I list all the downloads.
-
Posted
by
Nino
-
I recently had a reader of my SlingBox review from last spring inquire about my ISA Server configuration to allow me to remotely access it the Slingbox. Here's what I did:
On the ISA Server:
Note: I am running Microsoft ISA Server 2006; these instructions should also work on Microsoft ISA Server 2004. I am also assuming that you are comfortable with creating new protocols and firewall access rules.
- Create a new protocol (I called it 'Sling') with:
- Protocol type of TCP
- Direction of Inbound
- Port range of 5001.
- Create a new access rule (called it 'Remote Slingbox') with:
- Action of 'Allow'
- Traffic using the previously created 'Sling' protocol
- From External
- Tto your Slingbox's IP (I also have 'requests appear to come from the original client' selected, but the use of this option somewhat depends on how you have things set up)
- Networks for the listener of 'External'
- Schedule set to your preferences (I'm using 'Always').
- Apply the access rule and ensure it is enabled.
On the Slingbox:
- Connect to your SlingBox via SlingPlayer on your PC, then navigate to Slingbox > Properties in the menu.
- Select the Slingbox Configuration tab.
- Location the 'Network Settings' section. Click the Change button, this will launch the Slingbox Setup Wizard.
- Enter in the administrator password as prompted, hit next.
- Check the "I'm ready to setup remote viewing for my Slingbox" box. Also check the "A do-it-yourself kind of person?" box (since we won't be using UPnP to configure ISA) Click Next.
- Enter in the IP Address of your Slingbox, the subnet mask, and the default gateway (which, if it is your gateway, is the internal IP address of your ISA Server). Also enter in the port number you want your Slingbox to listen on (I'm using the default of 5001). Click Next.
- Select the 'Manually configure your router' radio button (again, as we're using ISA Server...). Click Next.
- Click Next on the 'Manual setup' dialog without making any selections.
- If you have your ISA Server already configured (see above), you might want to test your connection now, otherwise, select 'I want to skip this for now'. Click Next.
- Click Finish, which returns you back to the Slingbox Configuration tab. Click OK.
At this point, you're ready to test. Fire up your Slingbox client (I tested using my Windows Mobile Smartphone).
Something else that may be useful here is a dynamic DNS service to make it easier to find access your system remotely (which, if you're running ISA Server at home, you very well already have). I'd like to toss out a recommendation for DynDNS (http://www.dyndns.com).
-
Posted
by
Nino
-
Catching up on blogs I just saw Ryan's post about fellow MVP Doug Reilly. Doug lost his battle with cancer on December 23 (Here's Jean's post). Scott Watermasysk posts, too.
As both Scott and Ryan noted, Doug was a great guy. Admittedly, I didn't know him well (mostly virtually), but I can say that he was one of the nicest, most helpful guys out there.
Why not spare a few dollars and make a donation to the LiveStrong foundation?
-
Posted
by
Nino
-
I upgraded nino.net tonight to Community Server 2.1, SP2 from CS 2.0. I was already running on ASP.NET 2.0, so that saved me a few steps.
I did my upgrade something like this:
- Download and unpack CS 2.1 SP2 (ASP.NET 2.0) bits.
- Get my host to back up my database.
- FTP down my database backup.
- FTP down my web bits and diff against what I have under version control in TFS.
- Update my web.config and CommunityServer.config files.
- Take a large drink of water (really, water) and a deep breath.
- Uploaded my App_Offline.htm file.
- Connect to my hosted SQL Server 2005 database via SQL Management Studio
- Ran cs_2.x_to_2.1_upgrade.sql via SQL MS.
- Waited (for disaster).
- Saw the [happy] green circle with the white checkmark and the words "Query completed successfuly". </gasp>
- Ran through the output in the message window. Hot damn! It really worked.
- Connected to my website with FileZilla and deleted all the CS 2.0 bits.
- Uploaded the CS 2.1 SP2 bits.
- Uploaded the assemblies for Scott Watermasysk's CS Modules
- (feeling optimistic at this point) Renamed App_Offline.htm to App_Offline.htm.foo
- Fired up IE and hit the site.
- w00t!
My first CS upgrade that has been completely painless. Nice. :-)