Archive for November, 2013

Configure a linked server using the IBM OLE DB data providers on an SQL server

November 27, 2013

This post shows the basic steps to configure a linked server using the IBM OLE DB data providers on an SQL server.

To configure a linked server using the IBM OLE DB data providers on an SQL server, you should do the following:

1, Open the SQL Server Enterprise Manager(SQL Server 2000) or SQL Server Management Studio(SQL Server 2005).
2, Under the Console Root, expand Microsoft SQL Servers > SQL Server Group > Local > Security > Linked Servers for SQL Server 2000. For SQL Server 2005 expand Server Objects > Linked Servers.
3, Right-click on Linked Servers and select New Linked Server.
4. Give your new Linked Server a title in the Linked server: text box.
5. For the Server type, select Other data source and select the desired IBM OLE DB data provider.
To decide which one of our providers would be best to use, you can refer to the following table from the IBM iSeries Access Programmer’s Toolkit:

Database Provider Framework Consideration
IBMDA400 OLE DB Provider Existing applications, applications that want the most flexible OLE DB support, including support for SQL, RLA, Data Queues, and Commands.
IBMDASQL OLE DB Provider SQL-only support, SQL commitment control, and MTS.
Note: IBMDA400 does not support SQL commitment control or MTS; it supports only SELECT statements.
IBMDARLA OLE DB Provider RLA-only support, forward-only cursors and block fetches with RLA.
Note: IBMDA400 does not support forward-only cursors or block fetches with RLA.
IBM.Data.DB2.iSeries .NET Provider Offers the best performance when using the .NET framework.
MSDASQL OLE DB Provider Microsoft’s OLEDB-ODBC bridge, which uses our ODBC driver

Note: Microsoft SQL Server is SQL based. The IBMDASQL OLE DB provider is the provider that should be used with Microsoft SQL Server linked servers.

In the following example, I am using the IBMDASQL provider:

6. Type your Data source. This is the name of your IBM System i server.
7. Optional: Provider string. The Provider string can contain any valid connection properties the provider supports. Connection properties are seperated by a semi-colon. Valid connection properties for the IBM i OLE DB provider can be found in the Programmer’s Toolkit. In the example below the ‘Default Collection’ property is used. This is the default library that you connect to. If nothing is specified, the library of the user profile being used to connect will be used. Catalog. In MIcrosoft’s terminology, Catalog is the relational database name. If your RDB name matches the IBM i server name then you do not need to provide a value. If the RDB name does not match the IBM i server name then the RDB name should be inserted into the Catalog field.

Note: For SQL Server 2005, the Product Name must have a value. It seems that almost any value works, aside from special characters. In the above example, ‘DB2 for i’ is used.

8. Click on the Security tab.
9. Select the Be made using this security context radio button.
10. Click OK. You should now see the linked server in the list.
11. In SQL Server 2000, test the connection by expanding the linked server and double-clicking on Tables. You should see the list of tables in the right pane.

Note: For SQL Server 2005, this test may not show a list of tables. This function seems dependent on what version of SQL Server 2005 is being used. For instance this doesn’t work with Express versions but seems to work with Developer or Enterprise editions.
In SQL Server 2005, you can test your linked server by running a simple query:

1. Click on New Query.
2. Type the syntax of the query.
3. Click Execute.

Note: Some additional configuration steps are often needed to get this working with SQL Server 2005, particularly if this is the first OLEDB provider the SQL Server user has ever tried configuring.
The OLE DB provider must be configured to allow inprocess. Under server Objects -> Linked Servers -> Providers right click on the provider being used (IBMDASQL, IBMDA400, or IBMDARLA) and select properties. Make sure “Allow Inprocess” is checked.
If the user is getting “Msg 7399, Level 16, State 1, Line 1” type errors when attempting to run the sample select statement, this is a problem with the SQL Server service and the rights the user it is running under has. There are two things that can affect this. Note that this is all Microsoft code-related and is as-is at best. Assistance with this should be directed to Microsoft service and support.
o The SQL Server process is likely set to run under something other than the “Local System” account. You can check this in the SQL Server Configuration Manager tool (in the “Configuration Tools” folder in the start menu). This service may be set to run under the built in “Network Service” account or some other account. Change it to the “Local System” account and let Windows restart the service.
o In the SQL Server 2005 Surface Area Configuration tool (also in the “Configuration Tools” folder), select “Surface Area Configuration for Features”. On the new panel, select OLE Automation and make sure the “Enable OLE Automation” option is checked. This change should no longer be needed from V6R1 System i Access and beyond; however, up through V5R4 iSeries Access, there are still some OLE automation objects involved.

Source: IBM Support


Microsoft Dynamics CRM – Quick Add Update

November 18, 2013

The Quick Add/Update interface will allow the CRM users to add or update multiple records for any CRM Entity (including the custom entities)
This interface will enable the CRM users to save lots of their time there by improving their performance. Because of its user-friendliness, the CRM User’s will find it very easy to perform the insert/update multiple entities at a single place.
Another important aspect of this interface is that, it pre-populates the data (Both System and Custom data) for the Pick list data types.

Quick AddUpdate Addin

The Quick Add/Update interface currently supports the following data types:

  • String
  • Memo
  • Pick list
  • Integer
  • Number
  • Float
  • Decimal

Some salient Feature Quick Add Update:

  • Quick Add Update add-in is compatible with MS CRM 3.0/4.0
  • The interface supports two modes i.e Add Mode and Edit Mode
  • Custom Entities and Custom Attributes are supported.
  • Picklist’s data are pre-populated.

The Quick Add Update add-in is FREE.


  • Save lots of time while performing multiple insert/update operation
  • Easy to use.

Please click here to download Quick Add Update add-in Please click here to download User Guide document
Mindfire Solutions has deep experience in Customizing Microsoft Dynamics CRM application. We will be glad to share our expertise in detail with you. To learn about our Microsoft Dynamics CRM expertise and services please visit our Microsoft Dynamics CRM Consulting Development skills page.

How to delete the default SSP in SharePoint 2007

November 10, 2013

If you attempt to delete the default SSP from within Shared Services Administration, the Delete link will be greyed out. That’s because it’s the default SSP and SharePoint doesn’t allow you to delete the default SSP via the GUI.

One option to get around this is to create a new SSP and change associations to point to that new SSP. Once you do that, the Delete link for the original SSP becomes available because it no longer has any shared services associated with it.

If you’re like me however, and you don’t want to go to all that effort, then there’s a little trick to get around this.

stsadm -o deletessp -title SharedServices -force

The help for the deletessp command won’t actually indicate that -force is a valid switch, but without it, the command may fail. If you run into errors, try running it with -force.

The deletessp command will force the removal of the default SSP. If you receive an error after running the command, that’s fine. Sign back into Shared Services Administration and the delete link for the default SSP should no longer be greyed out.

Once you click Delete, you will be prompted to delete the associated databases, but in my experience, this generally doesn’t work. As a secondary step, I often find myself doing a bit of clean up. Within the database server, I remove all the default SSP databases and within IIS, I remove the SSP web site and application pool.

That should do it! You should now be able to create a new SSP. If you have any problems, or encounted an issue I did not cover here, please contact me or post a comment, I’d be happy to help.

You shouldn’t have to recreate your My Sites web app or any other web app that was associated with that SSP. You should be able to just re-configure those associations. Any search, profile or audience data will be lost and will have to be re-configured.


Update Rollup 15 for Microsoft Dynamics CRM 2011 (KB 2843571)

November 7, 2013

Microsoft has released Update Rollup 15 for Microsoft Dynamics CRM 2011 Server, Microsoft Dynamics CRM for Microsoft Office Outlook, Microsoft Dynamics CRM 2011 Language Packs, and Microsoft Dynamics CRM 2011 Email Router.

For more information about this release, see Microsoft Knowledge Base article 2843571:

Update Rollup 15 is available for Microsoft Dynamics CRM 2011

To maintain parity between the application components of Microsoft Dynamics CRM 2011, this update rollup includes packages for Microsoft Dynamics CRM Server, Microsoft Dynamics CRM for Outlook, Microsoft Dynamics CRM Language Packs, and Microsoft Dynamics CRM Email Router.

Supported Operating System

                            Windows 7, Windows 8, Windows Server 2008, Windows Server 2012, Windows Vista, Windows XP


    • This update must be installed on a computer that is running Microsoft Dynamics CRM 2011 Update Rollup 6 or a later Microsoft Dynamics CRM 2011 update rollup.
    • This update requires Microsoft .NET Framework 4.

Click the file you want to download from the list below.
Important: The language pack must be installed before you can apply the update rollup for that language pack. Download and install a language pack at Microsoft Dynamics CRM 2011 Language Pack.
To install this update rollup, do one of the following:

  • To start the installation immediately, click Run.
  • To save the download to your computer for installation later, click Save.
  • To cancel the installation, click Cancel.

Components also installed with this update rollup The following components, if not already installed, will be installed when you apply this update rollup:

  • Visual C++ 2010 runtime
  • ReportViewer 2010 control

Hotfixes and updates that you have to manually enable or configure
This Microsoft Dynamics CRM 2011 Update Rollup contains hotfixes and updates that you must manually enable or configure. To enable or configure these hotfixes on the server that is running Microsoft Dynamics CRM 2011, see the “Hotfixes and updates that you have to manually enable or configure” section of the following Microsoft Knowledge Base article:
Update Rollup 15 is available for Microsoft Dynamics CRM 2011

Microsoft Dynamics CRM 2011 Change Help Server URL

November 5, 2013

Find the table ConfigSettings in the MSCRM_Config database. Set the HelpServerURL value to blank (or your CRM domainname). Then recycle the CRM application pool in IIS to update the changes.

Trace Reader for Microsoft Dynamics CRM

November 4, 2013

Trace reader for Microsoft Dynamics CRM helps you reading the trace files generated by Microsoft Dynamics CRM (4.0, 2011 and 2013) on a graphical interface. Filters help you to display only relevant information.


More over, when the trace contains XML, you can display it formatted to improve readability.



Microsoft Dynamics CRM Server 2013 RTM downloads

November 1, 2013

Here is a list of the current Microsoft Dynamics CRM Server 2013 downloads.

Microsoft Dynamics CRM Server 2013:…

Microsoft Dynamics CRM 2013 for Microsoft Office Outlook (Outlook Client):…

Microsoft Dynamics CRM 2013 Email Router:…

Microsoft Dynamics CRM 2013 Language Packs:…

Microsoft Dynamics CRM for Windows 8:…

Microsoft Dynamics CRM for iPad:…

Report Authoring Extensions:

SharePoint List Component: