Archive for February, 2014

Failed to decrypt protected XML node “DTS:Password” with error …

February 17, 2014

This issue occurs mainly due to security related issues. Follow the steps below in order to rectify the issue:

In Visual Studio, go to the Control Flow Tab

  • Right-click on an empty area inside the window, select properties.
  • Set Protection Level to EncryptSensitiveWithPassword
  • Set PackagePassword to “myPassword”
  • From the Connection Managers:
  • Double click connection
  • Click “All”
  • Under Security Area:
  • Set Password to your connection’s password
  • Set Persist Security Info to True
  • Save the package
  • Connect to SQL Integration Services in SQL Manager
  • Under Stored Packages:
  • Right-Click MSDB
  • Select Import Package
  • Set Package Location to File System
  • Set Package Path to the location of your dtsx file
  • Leave the rest as defaults
  • Click OK
  • Enter “myPassword” into the Package Password dialog
  • You have now successfully imported the package.
  • In order to create an SQL Job:
  • In the job step:
  • Set the Type as SQL Server Integration Services Package
  • Set the Package Source as SSIS Package Store
  • Set the Server as the database server where you stored your package in the steps above
  • Click the button for the package and choose your package.
  • Click OK
  • Enter “myPassword” into the Package Password dialog
Success. You may now schedule and execute the job.
Advertisements

SSIS Error : Failed to decrypt protected XML node “DTS:Password” with error 0x8009000B “Key not valid for use in specified state.”

February 13, 2014

A SSIS Package Execution Error

Got this when scheduling a SSIS package via SQL Server Agent

Description: Failed to decrypt protected XML node “DTS:Password” with error 0x8009000B “Key not valid for use in specified state.”

The developer had a saved the package with a stricter security level.
I solved by changing the ProtectionLevel property to DontSaveSensitive
(The solution was using SSIS Package configuration files)

http://social.msdn.microsoft.com/forums/en-US/sqlintegrationservices/thread/749bb98a-5317-43bd-a548-e0cdef5a12d9

Read more: http://sqlsolace.blogspot.com/2009/05/ssis-error-failed-to-decrypt-protected.html#ixzz2t9CMho7Q

Advanced Event Viewer download the fully functional unrestricted version

February 12, 2014

Advanced Event Viewer 2 allows you to view all the Event logs of all your servers in a single view. The program is easy to install and use. It works without agents making it the ultimate event viewer for your network.

Click here to download Advanced Event Viewer 2 (Version 2.5, Build 2985, Size 7 MB)Advanced Event Viewer is:

Compatible with Windows 7, 8, XP, Server 2008 (R2), 2012 and 2003

Easy to use and extremely easy to install (agent less!)

The downloadable version is fully functional and not limited, and 100% malware free

Instantly know the status of all event logs from all your servers

Advanced Event Viewer is the only tool that allows you to retrieve event log information from all your Windows Servers quickly and easily, and works without Agents. Making the installation and usage effortless and without risk.

Imagine all Event Logs of all servers in a single short consolidated list. Events that occur hundreds of times are now consolidated. You can select to view only the Errors and Warnings, you can filter your view. Advanced Event Viewer gives you full control. The program also provides direct access to online information regarding the Event Log you selected, including the Microsoft Knowledge base and Google search.

To see what’s new in Advanced Event Viewer 2, click here

Advanced Event Viewer is what the Microsoft Event Viewer (eventvwr.exe) should have been

jqGrid

February 10, 2014

jqGrid is a grid plugin for the JQuery Javascript library. It is free, open source and gets distributed under the MIT license.

  • Works fine under IE, Firefox, Chrome, Safari, Opera
  • CSS customizable with full Themeroller support
    The UI comes in 20+ languages
  • Paging and sorting
  • Search and filtering
  • In-place cell editing or on-the-fly form creation to edit a record
  • Supports subgrids and tree grid for displaying hierarchical data
  • AJAX enabled
  • Accepts XML/JSON/local array data sources

Free wrappers for  PHP and ASP.NET exist.

For more information on jqGrid wrappers, please, check out the other sections of the web site.

MS SQL Server 2012 unable to find the requested .Net framework data provider

February 6, 2014

There are multiple machine.config files in your \Windows\Microsoft.net\Framework\vXXXX\Config directories.  Check both of the v2 and v4 machine.config files for the following (four files total you’re looking at here).
There was an EXTRA, self terminated <DbProviderFactories> tag in two of my files.  I had all four open at once comparing them, and noticed in two of them, the V4 I believe, but check them all.  Essentially it was like this and very easy to miss:

<system.data>
<DbProviderFactories>
<add name=”Odbc Data Provider” invariant=”System.Data.Odbc” … />
<add name=”OleDb Data Provider” invariant=”System.Data.OleDb” … />
<add name=”OracleClient Data Provider” invariant=”System.Data … />
<add name=”SqlClient Data Provider” invariant=”System.Data … />
<add name=”IBM DB2 for i .NET Provider” invariant=”IBM.Data … />
<add name=”Microsoft SQL Server Compact Data Provider” … /></DbProviderFactories>
<DbProviderFactories/>
</system.data>

Notice the CLOSING tag at end of the <DProviderFactories> last item, in this case the “Microsoft SQL Server Compact Data Provider”, and then there’s another SELF CLOSING <DBProviderFactories> tag.  Clean this up by keeping the one after the last item and deleting the self closing one at the end.
I rebooted, walked away, came back and it worked . . . so be SURE to reboot, walk away and come back or might not work.

The SharePoint Diagnostic Studio 2010 (SPDiag 3.0)

February 5, 2014

Microsoft seems to have snuck in a new tool to help diagnose/troubleshoot issues in SharePoint.  It is part of the Microsoft SharePoint 2010 Administration Toolkit v2.0 and provides SharePoint administrators with a unified interface that can be used to gather relevant information from a farm, display the results in a meaningful way, identify performance issues, and share or export the collected data and reports for analysis by Microsoft support personnel.

image

In the example above I installed it on a WFE server in the SharePoint farm

image

Selecting “New Project” and accepting the server will give you a dashboard.similar to above and access to reports in the following categories: Base, Capacity, Performance, Availability and Usage.  NOTE: Make sure you launch SPDiag 3.0 as “Administrator” if you are running it on one of the SharePoint Servers, you can also run it from a client workstation provided some additional configuration has been performed.

SharePoint Diagnostic Studio 2010: Can be installed on any computer running 64-bit Windows 7, or on any server running a 64-bit Windows operating system. Requires Windows PowerShell 2.0.

To find out more about SPDiag 3.0 including: What’s new, Installing and Configuring, and Using it please check out the link here on TechNet.

The Microsoft SharePoint Team Blog has a great article detailing the features of SharePoint Diagnostic Studio.

SharePoint Diagnostic Studio in combination with SharePoint Health Analyzer and System Center Operations Manager gives an unprecedented view into your SharePoint Farm.

Important Links:

Using Microsoft Dynamics CRM 2011 for Microsoft Office Outlook with multiple eMail accounts

February 4, 2014

Let’s say your are using MS CRM 2011 inside of Outlook and you need to manage email from more than one email account.  You have your primary email account (you@yourcompany.com) and then you have an email account assigned to you by your largest client (you@yourclient.com).  You want to use MS CRM to manage both accounts, but you discovered that email that goes into the you@yourclient.com inbox can’t be tracked in MS CRM.  You get the “Only items in the default Microsoft Outlook store can be promoted to Microsoft Dynamics CRM” message when you try to track a message.

hs no track

You are able to manage multiple accounts pretty easily in MS CRM by using an Outlook rule to move messages from the you@yourclient.com inbox to the you@yourcompany.com.  If you are familiar with creating rules, you setup a rule to run when you receive messages through a specified account.  Here are the steps:

  1. Open Rules and choose Manage Rules & Alerts.
  2. Choose New Rule.
  3. Choose “Start from a blank rules” and pick “Apply rule on messages I receive”.  Click next.
  4. Select the condition “through the specified account” and put a check in the box.
  5. Click on the hyperlink in the rule description and choose the you@yourclient.com email address.  Click next.
  6. Put a check next to “move it to the specified folder” AND a check next to the “delete it” option.
  7. Click the “specified folder” hyperlink and choose the inbox for inbox associated with the you@yourcompany.com email account.  Click next.
  8. If you have exceptions to this rule, enter them on this panel.  Click next.
  9. Name your rule “Move messages from you@yourclient.com to you@yourcompany.com“.
  10. Make sure the check box to turn on the rule is checked.  Click finish.

This is a client-side rule and runs whenever Outlook is open.  When Outlook is running, the messages sent to the you@yourclient.com will be moved to the you@yourcompany.com inbox and be deleted from the you@yourclient.com inbox.  You can now use MS CRM 2011 track in CRM to record your communications from your client.

When you reply to a message sent to the you@yourclient.com Outlook will default to sending the message from the you@yourclient.com email address.  If you are in your you@yourcompany.com inbox and compose a new message it will use your default email account to send the message.  If you need to send the message from you@yourclient.com you need to click from button on the email message and choose the correct from address.

Change From Address

You can manage any number of accounts in this fashion.  You simply setup an Outlook rule for each account.  Since the messages are deleted by the rule, you don’t have any messages remaining in the you@yourclient.com inbox, unless you set some exception rules.

Source