I have had a number of Intellisync issues related to the above error.
This error will appear in the bottom right of the screen, above the Intellisync icon in the system tray.
The only solution i have found to resolve this issue is a uninstall and reinstall of Intellisync. I found that the error appeared even after doing the re-install, but restarting the Intellisync service after the install and re-opening Intellisync did in fact fix it.
Please note that Intellisync will need to be re-configured after the install so take note of the users previous sync settings.
Hope this helps!
Thursday 26 May 2011
Wednesday 25 May 2011
How to change the owner of a group
I have been asked multiple times how to change the owner of a group so it can be shared with other users and edited. To do this you will need access to the server or an administrative workstation as Architect is required.
Login to the Architect as 'Admin'
Go to MANAGE > PLUGINS
Under TYPE, select GROUPS and GROUPS, ACO
Find the plugin (Name of the group) in the list and right click it to select PROPERTIES.
Change the DEVELOPER to the user you would like to be the owner and click OK
Then ask all users to refresh their clients and the owner change should take effect.
Hope this helps!
Login to the Architect as 'Admin'
Go to MANAGE > PLUGINS
Under TYPE, select GROUPS and GROUPS, ACO
Find the plugin (Name of the group) in the list and right click it to select PROPERTIES.
Change the DEVELOPER to the user you would like to be the owner and click OK
Then ask all users to refresh their clients and the owner change should take effect.
Hope this helps!
"Database login failed: Unable to initialize data dictionary"
This error is generic, very common and has multiple possible solutions.
It is received when a user attempts to login.
I will not list all the possible fixes for this error but I will include the most common solutions.
First of all, ensure that the SLXSYSTEM and SQL Instance services are running. To do this, open the RUN command and type 'services.msc' and press enter. Click on the NAME header to organise the services by alphabetical order and confirm that the 2 above services are listed as STARTED.
"In a SQL 2005 or SQL 2008 environment, the SQL Native Client must be installed on every computer running SalesLogix for database connectivity. Because of the similarities between the different versions of SQL connectivity may be possible without the SQL Native Client; however, this is not a recommended configuration."
To ensure the native client is installed, open the Control Panel and go to either ADD/REMOVE PROGRAMS (Windows XP) or PROGRAMS AND FEATURES (Vista/Windows 7). Scroll down the list and confirm that 'Microsoft SQL Server Native Client' is installed.
If using a firewall or antivirus, check to see that the SQL process' and ports are not being blocked as this can cause the error to appear.
Also adding the server name to the hosts file on the local machine has also helped me resolve this error in the past.
Hope this helps!
It is received when a user attempts to login.
I will not list all the possible fixes for this error but I will include the most common solutions.
First of all, ensure that the SLXSYSTEM and SQL Instance services are running. To do this, open the RUN command and type 'services.msc' and press enter. Click on the NAME header to organise the services by alphabetical order and confirm that the 2 above services are listed as STARTED.
"In a SQL 2005 or SQL 2008 environment, the SQL Native Client must be installed on every computer running SalesLogix for database connectivity. Because of the similarities between the different versions of SQL connectivity may be possible without the SQL Native Client; however, this is not a recommended configuration."
To ensure the native client is installed, open the Control Panel and go to either ADD/REMOVE PROGRAMS (Windows XP) or PROGRAMS AND FEATURES (Vista/Windows 7). Scroll down the list and confirm that 'Microsoft SQL Server Native Client' is installed.
If using a firewall or antivirus, check to see that the SQL process' and ports are not being blocked as this can cause the error to appear.
Also adding the server name to the hosts file on the local machine has also helped me resolve this error in the past.
Hope this helps!
Outlook Integration Issues
Outlook Integration issues are one of the most regular issues raised and one of the easiest to troubleshoot/fix.
Saleslogix primarily uses 2 .dll files for it's integration with Microsoft Outlook, slmn.dll and slxab32.dll.
The slmn.dll stands for 'Saleslogix Mail Notification' and is used for recording emails to the Saleslogix history.
The slxab32.dll stands for 'Saleslogix Address Book'. This is the functionality is used for the connection to/ Selection of contacts from Saleslogix for emails.
There are 2 quick ways to tell if Saleslogix is integrated with Outlook. The first indicator is in the SLX client, in the bottom right of the screen there should be a small envelope icon to the right of the Time/Date. If the envelope has a red circle with a line through it, this indicated that SLX is not integrated with Outlook or not logged in.
The second indicator is within Microsoft Outlook. If SLX is successfully integrated there will be a few buttons visible, 'Record to history', 'Go to SLX' and when sending an email, 'Send SLX'.
If you believe that Saleslogix should already be connected to Outlook but the buttons aren't visible in Outlook, the first thing to check is the 'Disabled Items' in Outlook. You can access this by going to Help > About Microsoft office Outlook > Disabled Items. Ensure that neither of the .dll files are mentioned in here and also that there are no references to Saleslogix. If there are no disabled items affecting SLX you can do the following:
Saleslogix primarily uses 2 .dll files for it's integration with Microsoft Outlook, slmn.dll and slxab32.dll.
The slmn.dll stands for 'Saleslogix Mail Notification' and is used for recording emails to the Saleslogix history.
The slxab32.dll stands for 'Saleslogix Address Book'. This is the functionality is used for the connection to/ Selection of contacts from Saleslogix for emails.
There are 2 quick ways to tell if Saleslogix is integrated with Outlook. The first indicator is in the SLX client, in the bottom right of the screen there should be a small envelope icon to the right of the Time/Date. If the envelope has a red circle with a line through it, this indicated that SLX is not integrated with Outlook or not logged in.
The second indicator is within Microsoft Outlook. If SLX is successfully integrated there will be a few buttons visible, 'Record to history', 'Go to SLX' and when sending an email, 'Send SLX'.
If you believe that Saleslogix should already be connected to Outlook but the buttons aren't visible in Outlook, the first thing to check is the 'Disabled Items' in Outlook. You can access this by going to Help > About Microsoft office Outlook > Disabled Items. Ensure that neither of the .dll files are mentioned in here and also that there are no references to Saleslogix. If there are no disabled items affecting SLX you can do the following:
Restart the PC and don't open Outlook
Go to START
RUN
Type in CMD
Type C:\
Type CD PROGRAM FILES
Type CD SALESLOGIX
Type REGSVR32 /U SLXAB32.DLL
Press OK
Type REGSVR32 /U SLMN.DLL
Press OK
Type REGSVR32 SLXAB32.DLL
Press OK
Type REGSVR32 SLMN.DLL
Press OK
Open Saleslogix (You should be prompted to enter your login details to connect SLX to outlook).
This will first unregister the .dll files and then re-register them.
The above will resolve the most common Outlook integration issues. I hope this helps!
Subscribe to:
Posts (Atom)