Friday, 2 August 2013

SSMSE Error: Package 'Microsoft SQL Management Studio Package' failed to load



On Windows 8 (64-bit), after installing SQL Server 2008 R2 SP2 and installing SQL Server Management Studio Express, I could not get SSMSE to start up successfully - the IDE would open up with the following pop-up dialog error:


and then shut down when I click 'OK'


After scouring the web for a solution and unsuccessfully trying various suggestions, I eventually got to here: Duncan Smart's weblog; I was astounded when his very simple solution fixed my problem.

Fix: is to remove or rename this Registry subkey and then restart SSMSE:
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\100\Tools

For example rename the sub-key '100\Tools' to '100\Tools-old' or any other name.
e.g.
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\100\Tools-old

Then re-open SSMSE and it will re-create this sub key and will start up successfully (after it displays a pop-up message about 'initializing the environment for the first time' or something along those lines).  

Wow!

Friday, 21 June 2013

Duplicate emails: Outlook 2010 IMAP email account sending duplicate (2) emails when sending email.



In outlook 2010: 

1) Click the File menu tab then
2) click 'Info', 'Account Settings'


3) on Email Tab, double-click the IMAP account
4) Click 'More Settings'
5) Select the 'Sent Items' tab
6) Un-select the radio button next to 'Save sent items in the following folder on the server'

by selecting the bottom radio button next to 'Save sent Items in the Sent Items folder on this computer'

7) Click 'OK', then click 'Next'

Outlook will then automatically send a test message which can help you verify whether the issue is resolved... 


Confirm by checking that there's now only 1 copy of the test email in your local 'Sent Items' folder.


Sunday, 26 May 2013

Web Application Projects versus Web Site Projects in Visual Studio

In Visual Studio you can create web application projects or web site projects. You create or open a web application project by choosing New Project or Open Project in the Visual Studio File menu. You create or open a web site project by choosing New Web Site or Open Web Site in the File menu.
Each type of project has advantages and disadvantages, and it is helpful to understand the differences between them in order to select the best project type for your needs. You must select the appropriate project type before you create a project, because it is not practical to convert from one project type to the other.

For some scenarios, you do not have a choice. For example, if you want to create an
ASP.NET MVC application, you must use a web application project.

Scenarios in which web application projects are the preferred choice include the following:
  • You want to be able to use the Edit and Continue feature of the Visual Studio debugger.
  • You want to run unit tests on code that is in the class files that are associated with ASP.NET pages.
  • You want to refer to the classes that are associated with pages and user controls from standalone classes.
  • You want to establish project dependencies between multiple web projects.
  • You want the compiler to create a single assembly for the entire site.
  • You want control over the assembly name and version number that is generated for the site.
  • You want to use MSBuild or Team Build to compile the project. For example, you might want to add prebuild and postbuild steps.
  • You want to avoid putting source code on a production server.


Scenarios in which Web site projects are the preferred choice include the following:
  • You want to include both C# and Visual Basic code in a single web project. (By default, a web application is compiled based on language settings in the project file. Exceptions can be made, but it is relatively difficult.)
  • You want to open the production site in Visual Studio and update it in real time by using FTP.
  • You do not want to have to explicitly compile the project in order to deploy it.
  • If you do precompile the site, you want the compiler to create multiple assemblies for the site, which can include one assembly per page or user control, or one or more assemblies per folder.
  • You want to be able to update individual files in production by just copying new versions to the production server, or by editing the files directly on the production server.
  • If you precompile the site, you want to be able to update individual ASP.NET web pages (.aspx files) without having to recompile the entire site.
  • You like to keep your source code on the production server because it can serve as an additional backup copy.

    MSDN: Web Application Projects versus Web Site Projects in Visual Studio

Tuesday, 21 May 2013

Trying to install reporting services for Microsoft SQL server on Windows 7, but the option to install reporting services is disabled in the setup?

Before you install SQL Server 2005 Reporting Services, you must enable Microsoft ASP.NET and Microsoft Internet Information Services (IIS). To enable ASP.NET and IIS, follow these steps:
  1. In Control Panel, click Programs, and then double-click Programs and Features.
  2. In the User Account Control dialog box, click Continue.
  3. Click Turn Windows features on or off.
  4. In the Windows Features dialog box, expand Internet Information Services, expand Web Management Tools, expand IIS 6 Management Compatibility, and then click to select the following check boxes:
    • IIS 6 WMI Compatibility
    • IIS Metabase and IIS 6 configuration compatibility
  5. Expand World Wide Web Services, expand Application Development Features, and then click to select the following check boxes:
    • ASP.NET
    • ISAPI Extensions
    • ISAPI Filters
  6. Expand Common HTTP Features, and then click to select the following check boxes:
    • Default Document
    • Directory Browsing
    • HTTP Errors
    • HTTP Redirection
    • Static Content
  7. Expand Security, and then click to select the Windows Authentication check box.
Note If you do not enable all these features, the Reporting Services option does not appear in the Feature Selection dialog box of the SQL Server Setup program.

support.microsoft.com - kb934164

Wednesday, 8 May 2013

How do I tell if my computer can run a 64-bit version of Windows?



To run a 64-bit version of Windows, your computer must have a 64-bit-capable processor. To find out if your processor is 64-bit-capable in Windows 7 or Windows Vista, do the following:
  1. Open Performance Information and Tools by clicking the Start button Picture of the Start button, and then clicking Control Panel. In the search box, type Performance Information and Tools, and then, in the list of results, click Performance Information and Tools.
  2. Do one of the following:
    • In Windows 7, click View and print detailed performance and system information.
    • In Windows Vista, click View and print details.
  3. In the System section, you can see what type of operating system you're currently running under System type, and whether or not you can run a 64-bit version of Windows under 64-bit capable. (If your computer is already running a 64-bit version of Windows, you won't see the 64-bit capable listing.)
To see whether a computer running Windows XP is capable of running a 64-bit version of Windows, do the following:
  1. Click Start.
  2. Right-click My Computer, and then click Properties.
    • If "x64 Edition" is listed under System, your processor is capable of running a 64-bit version of Windows.
    • If you don't see "x64 Edition" listed, your processor still might be capable of running a 64-bit version of Windows. To find out for sure, download and run the free Windows 7 Upgrade Advisor from the Windows 7 Upgrade Advisor webpage.


32-bit-and-64-bit-windows-frequently-asked-questions