When installing the new XBar application I found the instructions a little vague so I thought I would pass on a clarification.
Often times a web implementation will have an application server that is used to deploy the web portals to a web host server. When the Saleslogix web client and SData portals are deployed and then tested an Internal Server Error is encountered on the URL, similar to the following: Http://Webserver:3333/slxclient/slxdata.ashx/$app/scheduling/-/executions?
If you see an error like this "The following SData diagnosis occurred: Description=Operation failed. Message=Could not load type 'Sage.Entity.Interfaces.ICollection`1' from assembly 'Sage.Entity.Interfaces'. HTTP status: Internal Server Error (500)." in the web client when opening an entity the issue could be a corrupted group.
If your company is using windows authentication in the SalesLogix Web client then you will want to use Windows Authentication for your mobile clients.
Every so often we hear that a user can no longer add products to an opportunity whether it is a new opportunity or an existing opportunity. The add product plus sign is missing for no apparent reason.
We had a user looking up an opportunity by description so they could attach an email to the Opportunity. This brought the SData feature of SalesLogix into play since it is used by the SLXDesktop integration. However the Opportunity Lookup returned SData 500 error Internal Server Error.
Although these steps are primarily for an application server with a web server to host IIS some of these steps are good checks on any Job Server install. 1. Ensure that the actual executable (SLXJobServer.exe) has been upgraded
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.
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 […]
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.
We were comparing our SalesLogix Mobile Clients yesterday and one of our users could not see the Opportunities and History in his mobile client...
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...
One great thing about Amazon EBS based instances is the ability to stop the instance and retain your settings and data. However you should be aware of a pitfall for those of us using this feature. Amazon public images have a config.xml
What I like about this tool is the new feature that enables chaining of imports. For example, say we have an ERP system churning our 30 imports a night that need to run