November 2011 Entries

The full error in Microsoft Visual Studio on a compile looks like this:

error CS1548: Cryptographic failure while signing assembly 'C:\Program Files\Microsoft SQL Server\100\Samples\Analysis Services\Programmability\AMO\AMOAdventureWorks\CS\StoredProcedures\obj\Debug\StoredProcedures.dll'

This is likely due to a missing strong key pair value file. The easiest way to solve this problem is to create a new one. Navigate to: 

Microsoft Visual Studio 2010>Visual Studio Tools>Visual Studio x64 Win64 Command Prompt (2010)  [if you aren't on an x64 box, pick another command prompt option that fits]

Once the MS-Dos window displays, type in this statement:

sn -k c:\SampleKey.snk

Then copy the output *.snk file to project directory, or the *referenced directory.

Remove the old reference to the *.snk file from the project.

Add the paired key back to the project as an existing item.

When you add back the *.snk file to the project, you will see that the *.snk file is no longer missing.

Our work is done!  

*referenced directory: Pay attention to the original error message on compile. The *.snk file that is referenced may be in a directory path you aren't expecting--so you will still get the error unless you change the directory path or write the file to the directory the program is expecting to find the *.snk file.


If you are on a desktop version of Ubuntu, you can right-click on the file icon, click the permissions tab and click on "allow execution". If you are on a server copy without the desktop bells and whistles (or you would rather work with a command line in a terminal window), then do the following:

sudo chmod +x myProgram.bin

after you enter your password and get the prompt back type:



I recently needed to work with SSIS on my laptop with an existing SQL Server 2008 Express instance. I did not setup the service accounts correctly on the SQL Server 2008 Development install--so needed to remove the corrupt install.

There doesn't appear to be much documentation on this—well, if there is, then I didn't key in the best search criteria! Anyway, the removal of a named 2008 instance is an easy set of steps, although nervous-making--since you'll be uninstalling Microsoft SQL Server 2008 without any initial guidance.

Here are the steps you will need to take:

1. Navigate to Control Panel->Add/Remove Programs

2. Select Microsoft SQL Server 2008

3. Select Change/Remove

4. Select Remove

You will be asked for a specific instance. This is where you type in the name of the instance you want to remove. DON'T get click happy on what to de-install. Click ONLY on the items that specify your named instance. LEAVE all the SHARED features. If you delete them, you'll corrupt your other installations on that server.