in

DotNetDeveloper

Bits o this Bits o that

SharePoint

August 2009 - Posts

  • cryptographic failure while signing assembly

    The problem is that you cannot delete a key and you cannot add the key as you do not have access to the key to delete it and the .NET framework cannot add it because of constraints on the StrongName data store.

    The solution is to give yourself access to C:\Documents and Settings\AllUsers\ApplicationData\Microsoft\Crypto\RSA\MachineKeys\

    1. Browse to c:\Documents and Settings\AllUsers\ApplicationData\Microsoft\Crypto\RSA\MachineKeys
    2. Grant rights to Adminstrators, or whatever group you are in
    3. Take Ownership of this folder (click Advanced under Security, and then click the Ownership tab at the top)

    This worked all fine for me see how you get along. 

     

  • How to connect to MICROSOFT##SSEE

     if your struggling with this connecting to Microsoft##SSEE I followed the steps below and hey presto all working.

    • Open SQL Server Configuration Manager
    • Click on protocols for Microsoft##SSEE > Properties
    • Set Hide Instance to "No"
    • Enable Named Pipes
    • Finally Reset the SQL Server 2005 Embedded Edition (Microsoft##SSEE) service

    now all being well you will be able to access this server

DotNetDeveloper.co.uk
Powered by Community Server (Non-Commercial Edition), by Telligent Systems