2007 Mirosoft Office system RTM install – does not support upgrading from a prerelease version

===== Description =====


After uninstalling all applications related to Microsoft Office 2007 Beta 2 Technical Refresh (B2TR), the following error prompts during the installation of Microsoft Office 2007 RTM.


===== Setup Errors =====


Setup is unable to proceed due to the following error(s):
The 2007 Microsoft Office system does not support upgrading from a prerelease version of the 2007 Microsoft Office system. You must first uninstall any prerelease versions of the 2007 Microsoft Office system products and associated technologies.
Correct the issue(s) listed above and re-run setup.


===== Resolution =====


*** These are for advanced users only. Take your own risk!
*** You have been WARNED!


You will need to uninstall all of the following applications before proceeding to install Office 2007 RTM.
- Microsoft Office Professional 2007 (Beta), Groove, OneNote, InfoPath, Visio, SharePoint Designer, Project, etc…
- Microsoft Office 2003 Web Components
- 2007 Microsoft Office Add-in: Microsoft Save as PDF or XPS (Beta)
- Microsoft Expression Web Designer Beta 1 / CTP1
- Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats (Beta 2 Technical Refresh)
- Microsoft Visual Studio 2005 Office Tools
- Microsoft Compatibility Packs for 2007 (Beta)


- Try to install Office 2007 RTM. If it prompts the same setup errors (of prerelease version), use Windows Installer CleanUp Utility to check whether any of the Office 2007 related products have not been installed, and try to remove the programs using {*** Add or Remove Programs ***} first.
 


- If the RTM setup still prompts the same setup errors, use {*** Windows Installer CleanUp Utility ***} to remove the related products. I have resolved my setup problem using the Windows Installer CleanUp Utility, and thus, do *not* need to proceed to the following step.   [;)]
 


- If the RTM setup still prompts the same setup errors, follow the steps in {manually removing the Office 2007 beta}.


===== Preparation for the installation of Office 2007 RTM =====


After the installation of Office 2007 RTM, you are suggested to install {Windows Desktop Search 3 RTM for Windows XP}, to install {PDF & XPS add-in for Office 2007}, and to fix {Building Blocks issues: to delete the file “%appdata%\Microsoft\Document Building Blocks\Building Blocks.dotx” *only* when you have *not* modified the Building Blocks content (e.g., galleries)}. For more information, please refer to {Office 2007 RTM issues}.


===== For more information =====


- Error messages when you try to install the original release version of a 2007 Office suite or program: “Setup is unable to proceed”
http://support.microsoft.com:80/default.aspx/kb/927222/en-us


- Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/kb/290301


- Unable to install Office 2007 Beta 2 applications – Error 2711. An internal error has occurred. (GraphicsFiltersCDRFilesIntl_1033 )
http://msmvps.com/blogs/martinpoon/archive/2006/11/12/after-applying-office-2007-beta-2-technical-refresh-b2tr-unable-to-install-office-2007-beta-2-applications-error-2711-an-internal-error-has-occurred-graphicsfilterscdrfilesintl-1033.aspx


- Office RTM product key issue update
http://msmvps.com:80/blogs/benwalters/archive/2006/11/17/office-rtm-product-key-issue-update.aspx


- Manually removing the Office 2007 Beta
http://pschmid.net/blog/2006/11/13/79


- Office 2007 RTM Issues
http://pschmid.net/blog/2006/11/13/80


- Windows Desktop Search 3.0 RTW for Windows XP (KB917013)
http://www.microsoft.com:80/downloads/details.aspx?displaylang=en&FamilyID=4982072F-7660-492F-B96C-E42B4F5AB4AA


- 2007 Microsoft Office Add-in: Microsoft Save as PDF or XPS
http://www.microsoft.com/downloads/details.aspx?familyid=4D951911-3E7E-4AE6-B059-A2E79ED87041&displaylang=en

Unable to install Office 2007 Beta 2 applications – Error 2711. An internal error has occurred. (GraphicsFiltersCDRFilesIntl_1033 )

===== Error =====

Microsoft Office Groove 2007 (Beta) encountered an error during setup.
Error 2711. An internal error has occurred. (GraphicsFiltersCDRFilesIntl_1033 )

===== Description =====

After the installation of Office 2007 Beta 2 Technical Refresh (B2TR), error 2711 will occur if you try to install any of the Office 2007 **Beta 2** products. To resolve the problem, you will need to uninstall all Office 2007 applications, uninstall Expression Web Beta 1 (if you have Expression Web installed), and use Windows Installer CleanUp Utility to remove all Office 2007 entries. Here are the steps that you will need to follow.

~ Uninstall **all** Office 2007 applications (Access, Excel, InfoPath, Outlook, PowerPoint, Publisher, Word, SharePoint Designer, Visio, Project, OneNote, Groove).

~ Uninstall Expression Web Beta 1 (if you have installed this application).

~ (If you cannot install Office 2007 Beta 2) use Windows Installer Cleanup Utility to clean-up all Office related entries.

~ Install **all** of the Office 2007 Beta 2 products.

~ Install B2TR for your Office products. Make sure that you install all Office **Beta 2** products before applying Beta 2 Technical Refresh (B2TR). You will *not* be able to install Beta 2 products after applying B2TR.

===== For more information =====

- Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/kb/290301

-
Download 2007 Microsoft Office system Beta 2 Technical Refresh (494.7 MB)

-
Download Project 2007 Beta 2 Technical Refresh (186.1 MB)

-
Download Groove 2007 Beta 2 Technical Refresh (185.4 MB)

-
Download Visio 2007 Beta 2 Technical Refresh (261.2 MB)

-
Download SharePoint Designer 2007 Beta 2 Technical Refresh (211.4 MB)


- Download Expression Web Beta 1 (196.5 MB)

Chance for a free trip to Mix07 in Las Vegas and USD 2500 by building Add-ons for Internet Explorer 7 (Deadline: 2007-02-09)

Develop your own Add-ons for IE7, and submit it on or before February 9th 2007. Grip the chance to win a free trip to Mix07 in Las Vegas, plus USD 2500 travelling allowance!

This IE Add-on contest is open to the entire world (with exception). Judging criteria is based on creativity, productivity, practical use, performance, difficulty of problem solved, cool factor, footprint, ease of use, application design / architecture and widespread interest / use.

Here comes the list of the attractive prizes.

- Grand prize: a trip for the winner and guest to attend Mix07 conference in Las Vegas that worth USD 1195 each, plus USD 2500

- First prize: USD 2000

- Second prize: USD 1000

- Third prize: USD 500

- Four honorable mention: Zune MP3 player

===== For more information =====

- Building Add-ons for Internet Explorer could net you a trip to Mix07 and $2500! { http://msdn2.microsoft.com/en-us/ie/aa904644.aspx }

- MIX07 conference { http://visitmix.com }

- Add-ons for Internet Explorer { http://www.ieaddons.com/default.aspx?cid=home&scid=0 }

Configuring the RSS news channel on the *start page* of Visual Studio 2005

In Visual Studio 2005, I do really like the feature of showing RSS feeds on the start page. Originally, the start page is used to display the product news but you can change it to show your favorite RSS feeds. I need to use Visual Studio 2005 every day, and I can get a glance at my favorite blog every time when Visual Studio 2005 starts.

Following is my current news channel settings in Visual Studio 2005.
–> Visual Studio 2005
   –> Tools
      –> Options
         –> (+) Environment
            –> Startup
               –> At startup: Show Start Page
               –> Start Page news channel: http://blogs.msdn.com/MainFeed.aspx?Type=AllBlogs
               –> (Y) Download content every: 7 minutes

===== for more information =====

- Visual Studio Startup, Environment, Options Dialog Box
http://msdn2.microsoft.com/en-us/library/ms165469(VS.80).aspx

Microsoft .NET Framework 3.0 Redistributable Package

The Microsoft .NET Framework version 3.0 redistributable package has been released! It combines .NET Framework version 2.0, Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), Windows Workflow Foundation (WWF), and Windows CardSpace. For those who are already working with .NET Framework version 2.0, only the new Windows Vista components are installed.

For those who have installed any pre-release versions of .NET Framework 3.0 (Beta 2, RC1, CTP), you will need to uninstall these versions using Add/Remove Program in Control Panel, before installing this final release version.

===== for more information =====
- Microsoft .NET Framework 3.0 Redistributable Package

http://www.microsoft.com/downloads/details.aspx?FamilyId=10CC340B-F857-4A14-83F5-25634C3BF043&displaylang=en

Database snapshot

Database snapshot is new in SQL Server 2005, and is available only in Enterprise Edition. Database snapshot is a static, read-only view of a source database at the time the snapshot is created, excluding all uncommitted transactions.

Snapshots should be placed on the same server instance as the source database, and that multiple snapshots can be created on a database. Though snapshots can be created and dropped without affecting the data of the source database and other snapshots, I do not recommend keeping the snapshot(s) for a long time as the performance of the system will be affected, especially on databases that require frequent updates. Also, back up and restore of snapshots are not supported, and the snapshots are gone when the source database and/or the snapshot are having problems. Therefore, when a persistent and reliable read-only copy of a source database is required, do *not* use database snapshots.

Following are some of the practical uses of database snapshots.
- To maintain historical data for report generation.
- To offload reporting when combined with mirror database.
- To safeguard data against administrative errors.
- To safeguard data against user errors.
- To manage a test database.

Creation of a database snapshot only requires a few seconds, as SQL Server uses a copy-on-write mechanism that does *not* copy the data from the source database immediately. All data is kept in the original database (source database), while a sparse file on the NTFS file system is created for holding the *old data* that have been *changed since* the creation of the snapshot. Before writing any committed transactions to the source database, the original data is copied to all snapshots, and is stored in the sparse files (and thus the term 'copy-on-write'). Upon accessing the data of a snapshot, unchanged data will be extracted from the source database, while changed data will be extracted from the sparse file.

Note that database snapshots are *not* related to snapshot backups, snapshot isolation of transactions, or snapshot replication.

===== to create a database snapshot =====

Creation of database snapshot is *not* supported in SQL Server Management Studio! To create a database snapshot, execute the following Transact-SQL.

CREATE DATABASE AdventureWorks_dbss200611022200 ON
(NAME = AdventureWorks_Data, FILENAME =
'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\AdventureWorks_Data200611022200.snapshot')
AS SNAPSHOT OF AdventureWorks;

Following are some recommendations for managing the snapshots.
- Name of the database snapshot is AdventureWorks_dbss200611022200. It is a good practice to specify the name of the source database (AdventureWorks), an indication for database snapshot (dbss), the create date (20061102) and time (2200).
- Limit the number of database snapshots as all database snapshots continue to grow when the source pages are updated.
- Give a meaningful file extension name for the physical snapshot file (e.g., *.snapshot).

===== to drop a database snapshot =====

The following Transact-SQL can be used to drop a database snapshot. All user connections to the database snapshot will be terminated. All sparse files that are used by the database snapshot will also be removed.

DROP DATABASE AdventureWorks_dbss200611022200

===== to revert a database snapshot =====

Before reverting a database snapshot, all other database snapshots of the same source database should be dropped. The following Transact-SQL can be used to revert the AdventureWorks database to the database snapshot AdventureWorks_dbss200611022200.

USE master;
– Drop AdventureWorks_dbss200611022345 if it exists.
IF EXISTS (SELECT dbid FROM sys.databases
                WHERE NAME = 'AdventureWorks_dbss200611022345')
        DROP DATABASE AdventureWorks_dbss200611022345;
– Reverting AdventureWorks to AdventureWorks_dbss200611022200
RESTORE DATABASE AdventureWorks
        FROM DATABASE_SNAPSHOT = 'AdventureWorks_dbss200611022200';

===== limitations on the source database =====

- The source database cannot be dropped, detached, or restored.
- I/O is increased resulting from the copy-on-write operation.
- Files cannot be dropped from the source database or from any snapshots.
- The source database cannot be configured as a scalable shared database.
- The source database should be online, unless the database is a mirror database within a database mirroring session.
- To create a database snapshot on a mirror database, the database must be in the synchronized mirroring state.

===== limitations on the database snapshots =====

- Back up, restore, attach, detach, full-text indexing are not supported for database snapshots.
- Security constraints of a database snapshot inherits from the source database at the time of snapshot creation. The inherited permissions cannot be changed and permission changes made to the source database will *not* be reflected in the database snapshots.
- Database snapshots must be placed on the same server instance as the source database.
- Database snapshots works on an entire database.
- When a snapshot runs out of disk space, the snapshot becomes suspect and must be deleted.
- Snapshots are read-only.
- Snapshots cannot be created on the model, master, and tempdb databases.
- Files cannot be dropped from a database snapshot.
- Database snapshots can only be created on NTFS file systems.
- A snapshot always reflects the state of filegroups at the time of snapshot creation: online filegroups remain online, while offline filegroups remain offline.
- Database snapshots depend on source database. When the source database becomes RECOVERY_PENDING, the database snapshots may become inaccessible.
- Reverting is unsupported for read-only filegroups or compressed filegroups.
- In a log shipping configuration, database snapshots can be created only on the primary database, and *not* on a secondary database. Database snapshots will need to be dropped when the roles of the primary and secondary server instances need to be switched.
- The database snapshot cannot be configured as a scalable shared database.

===== restrictions on reverting =====

- The source database should not contain any read-only or compressed filegroups.
- The online status of the files should be the same as when the snapshot was created.
- Only one snapshot can exist.

===== for more information =====

- Database Snapshots (SQL Server 2005 Books Online)
http://msdn2.microsoft.com/en-us/library/ms175158.aspx