Unspecified Error logging into Infor CRM / SalesLogix
Posted By: anoshwadia on June 29th, 2015 in Saleslogix
No Gravatar

If you’ve worked with Infor CRM / SalesLogix for a while, you’ve probably run into the issue where you enter your username and password (correctly!) and all you get is an Unspecified error! Very descriptive, isn’t it?

Cause: Essentially what the error means is that the application is unable to connect successfully with the SQL server database. There are several reasons for this, hence many possible fixes.


1) Correct Native Client Installed – the most common issue (and this affects Windows Client users or any web user who has any of the Windows based tools installed) is that the correct SQL Native Client is not installed.

The SQL Native client is like a “driver”, you can install multiple versions on the same machine (for example SQL 2005 Native Client, SQL 2008 R2 Native Client and SQL 2012 Native Client) without any adverse effects.

However you do need to verify you have the CORRECT one installed. The correct one is the one being used on the Infor CRM / SalesLogix server in the Saleslogix Connection Manager. In the example below you’ll notice that the EVAL81 database is using SQLNCLI10.1



Here’s how the various versions of SQL Native client show up as in the Data Link Properties:



Version Number Product Version
9.x SQL 2005
10.x SQL 2008 (or 2008 R2)
11.x SQL 2012
12.x SQL 2014




So based on the above, this tells us that the database connection is being made using a SQL 2008 (R2) Native client and that’s the version that should be installed to ensure connectivity.

Note that the version of the SQL Native client doesn’t necessarily have to match the version of SQL Server being used, technically a SQL 2005 Native Client could be used to connect to a database on a SQL 2008 platform. However it is recommended that the same version as SQL server is used. Using the wrong version of the SQL Native client causes issues with SQL 2012 databases in particular.


2) Saleslogix Connection Manager – Often the Saleslogix connection manager has not been setup correctly. A quick way to test this is to try connecting from another client machine or from the server itself. Check to ensure that the connection to the database has been setup correctly and for SQL 2008 Native Client and higher, ensure that you click on the Advanced Settings and set the following:

  • Integrated Security  – Click the Reset Button
  • Persist Security Info – Set to True


3) SQL Server Network Access – If none of the clients can connect, you may have an issue with the SQL server itself. By default SQL Express instances do not have TCP/IP protocol enabled so they are accessible via the local machine only. Check the settings in the SQL Server Configuration Manager to ensure TCP/IP protocol is enabled for your SQL instance.


4) Firewall and Network Connectivity – Even though the client connects via the Saleslogix Application Server, it still needs direct access to the SQL server as well. See if you can ping the SQL server from the client machine. You can also try to Telnet to the SQL server at port 1433.


5) Corrupt Connection Settings – occasionally you run into a client machine that has corrupt SalesLogix Connection settings, even though they appear to be correct and pass the connection test. Its recommended that the client connection be deleted and re-created. You may also have to delete all subkeys under:



6) Reboot – When all else fails, maybe all that’s needed is a reboot! Sometimes SQL settings don’t take effect until a reboot is done.


Hope this brings some clarity to this very vague error message! If you need further assistance, call our support line at 1-877-777-9779 and we’ll be happy to help you!

Logging into the Infor CRM Mobile Client with an iPhone / iPad
Posted By: anoshwadia on June 29th, 2015 in Saleslogix, SLX Mobile
No Gravatar

We’re often asked, why can’t I login to the Infor CRM (SalesLogix) mobile client using my iPhone / iPad?

Here are some common things to check on your device:

1) Click on Settings   unnamed


2) Click on Safari –> Under Privacy and Security –> Block Cookies –> Always Allow



3) Go one step back…now scroll down and click on Advanced –> Make sure Javascript is set to ON.



4) Clear your Safari cache. This is done in 2 steps:

a) Click on “Clear History and Website Data”. Tap the Clear button when prompted.

Capture         clear-safari-history-and-website-data

b) Click on Advanced –> Website Data –> Remove All Website Data


Usually these steps should let you login to the mobile client if you try again.


Assuming the above does not resolve your issue, here are some additional things to try:

a) Try logging into the Mobile client using your regular desktop browser on your computer (Chrome / Firefox). If you cannot login there, it indicates either an issue with either the version of the Mobile client being incompatible with your version of iOS, or an issue with your login.

b) Verify your login works by logging into the Infor CRM web client using your credentials. Often a concurrent user is locked out of the system due to several invalid login attempts and is not made aware of this when they login to the mobile client.


If you need further assistance, call our CRM support line at 1-877-777-9779 and we’ll be happy to help you!

Make an editable grid refresh on email Drag & Drop – SalesLogix8
Posted By: Alex.Cottner on November 4th, 2013 in General
No Gravatar

I extended business rules for a customer to automatically create ticket activities when an emailed history record is associated with a ticket. This was done to mirror logic from their old LAN environment. However they pointed out that when they dragged & dropped an email onto a ticket the grid didn’t refresh automatically.

After investigating the NotesHistoryList I quickly discovered that I could inject this into my quickform without any hassle. The injection point here is the contextualCondition property of the editable grid.

this.onHistoryChanges = function (history) {
this.connections = [];
this.connections.push(dojo.subscribe('/entity/history/create', this, this.onHistoryChanges));
this.connections.push(dojo.subscribe('/entity/history/change', this, this.onHistoryChanges));

Now whenever a history record is added or an email is Dragged & Dropped in, the ticket activities grid will automagically refresh for the user (just like the Notes/History grids do).

Allowing users to edit other activities via a Custom Form
Posted By: Alex.Cottner on June 7th, 2011 in General, Saleslogix
No Gravatar

The provided API to Edit, Complete, and Delete activities is as follows…
Application.BasicFunctions.EditActivity activityID
Application.BasicFunctions.CompleteActivity activityID
Application.BasicFunctions.DeleteActivity activityID

Unfortunately, there is a bug that adds the currently logged in user’s UserID to the end of the required query. This means that any time a user tries to edit another user’s activity, those API calls will fail. This happens even if they have full calendar access. (more…)

Web Mailmerge on Vista
Posted By: nicocrm on July 2nd, 2008 in Saleslogix
No Gravatar

Compared to the instructions at http://customerfx.com/pages/crmdeveloper/2008/02/21/solving-thttprequestthread-errors-with-activemail-in-saleslogix-web.aspx there are a few different steps to get the SLX Mailmerge piece to work on a Vista web server (IIS7).

  • Configure the web manager, same as on 2003 or XP (same as the instructions on Ryan’s post)
  • Create the /mmserver virtual directory and point it to C:\PF\SLX\Web Components\mmserver (same as before).  Make sure you create it as an Application and select the correct type of Application Pool (classic pipeline, 32bit enabled if running on Vista64)


  • Under mmserver click "Handler Mappings" and enable "ISAPI-dll":



  • On the server configuration (click on the server name), select "ISAPI and CGI Restrictions" and add an entry for the slxwebmm.dll:



Update (2008-08-23): Same instructions work with Windows Server 2008. We had to make sure that the mmserver and the SlxClient applications were both running in the same application pool for some reason.