ComboFix, a third party malware utility, will alter the Operating system so .qts and .que files will no longer process and complete the sync cycle. To check for ComboFix look for the following dir "C:QooBox". Once it is determined ComboFix was run on this workstation here are the steps you will need to take. 1. Backup the registry. 2. Open Registry Editor. 3. Find HKEY_LOCAL_MACHINESystemControlSet001ControlFileSystem and in the righ...
With all the browser updates it's tough to keep SalesLogix web client running as it should with the mail merge functionality working and stable. Here's a step by step method to set up Firefox v10.x (you can download v10 at www.oldapps.com) with mail merge.
In the SalesLogix web client there is code to handle parsing phone numbers in the SalesLogix phone web control for numbers using “x” to denote the start of an extension (i.e. 6515551111×123). There is also code in place to handle phone numbers using “ext” as the extension designator however this code has a syntax error. […]
In the SalesLogix web client, there is a SalesLogix currency control that can be used to enter and display currency values in the web client. In 7.5x this control used to display the currency symbol. In v8, the currency symbol no longer displays. Version 7.5x shown above. Version 8 shown above. […]
Just a heads up on something I ran into that was causing me some problems. The format of the way the connection string is stored in the connection.config file of the SalesLogix deployed slxclient website has changed between versions 7.5 and 8. In 7.5x the format of the connection.config file looked like: <?xml version=”1.0″?><ConString>Provider=SLXOLEDB.1;Persist […]
Watch this video to learn multiple ways to improve the performance of your SalesLogix on-premise Web and Cloud system. We share our 15+ years of experience and recommendations on how to get your implementation performing at its best.
On one of our test servers I received the following message when attempting to build the SalesLogix web platform on a v7.5.3 system with Hot Fixes 1 through 4. An application Exception has occurred. Failed to build Sage.Integration.Entity.Feeds.dll. (Sage.Platform.Orm.CodeGen). What finally fixed the issue was a complete uninstall and reinstall. Then a pack and rebuild […]
In the SalesLogix web client, the Area Category Issue list at Tickets is a SalesLogix control called the DependencyLookupControl. This control is contained in the Sage.SalesLogix.Web.Controls.dll assembly file. There is also some external client side scripting that works in conjunction with the server code to control the behavior of the lookup. The way the control […]
With the SalesLogix Desktop Integration and the Outlook integration web client users have great tools to integrate emails and history into SalesLogix. But what happens when there is an email that fails to send when selecting SendSLX?
When running SpeedSearch on a new SalesLogix Web installation I received the following error when searching with the Web client.
I recently assisted a number of users that were unable to get Intellisync to configure or sync correctly. Here are some of the issues and fixes we used.
n the earlier versions of 7.5 the Sdata deployment used the SalesLogix application pool. But since 7.5.3 Sage has used a separate application pool for Sdata. I would recommend adding a separate application pool for Sdata for anyone on version 7.5.1 or 7.5.2.
A recent Microsoft automatic update has added new security to IE8 that prevents some users from logging into the SLX Client.
The Sage Desktop Manager application that runs in your taskbar can be restarted from your Start, Programs, Startup, SalesLogix Desktop Manager. This location, while not obvious, does allow those users without the SalesLogix LAN client install to start the app from the Programs.
With the revision of Intellisync in version 7.5 the new requirement is a deployment of the SLXIntellisync portal. What you will need to do is go through all of the same steps you would take to deploy the slxclient. On your web server add the Webdll user to the local administrators group, the IIS_WPG or (IIS_IUSRS in Windows Server 2008
The standard SalesLogix 7.5.x “SLX Web Reporting” site can only be used for one database because it contains a Connect.Config file that points to a single database. You can switch between databases by re-deploying the “SLX Web Reporting” site, but in a development environment it is more convenient to set up multiple reporting sites, one for each database. The below procedure explains how to setup reporting dedicated to one database. (The...
I recently had a client that was using the SalesLogix LAN client and had upgraded from 6.2 to 7.5.2 During the upgrade a problem arose that exhibited itself by crashing the SalesLogix client with no error messages of any kind. After looking into it I discovered the problem was a custom form they had was […]
At times I have been asked how can I increase the performance of SalesLogix. For systems using SQL2005 or SQL2008 the slowdown may be corrected by adding an index to the table that the SalesLogix script queries. The trick is finding where the bottleneck resides.
Last week I blogged on the deployment of the Disconnected Web Client. Today's post discusses the issues that could arise on the Installation of the Disconnected Web Client. If you have deployed in Application Architect and ran the sync server then the remote users should be able to run sync, apply the changes, and open the personal web server and then the SLXClient.
If someone has deleted an existing SalesProcess and you need to restore it you can follow this guide.