11/21/2024 11:50:08 AM
slxdeveloper.com
Now Live!
|
|
| |
| Installing v5.2 and v6.0 on the same machine |
|
| Description: |
Although the use of SalesLogix v6.0 and v5.2 are not supported on the same machine, this article will walk you though the steps and workarounds to get both versions working.
|
| Category: |
Miscellaneous SalesLogix Articles
|
| Author: |
Ryan Farley
|
| Submitted: |
11/4/2002
|
| |
|
| Stats: |
Article has been read 13998 times
|
Rating:
 - 5.0 out of 5 by 7 users |
|
|
|
fiogf49gjkf0d
Best Software CRM division has not qualified the use of SalesLogix v5.x and v6.0 on the same machine. The installs will detect the older version of SalesLogix and remove it prior to installing SalesLogix 6.0. The intent of this is to not allow customers to accidentally install both versions. However, this is not very practical from a business partner standpoint since we will be likely supporting customers on both 6.0 and 5.2 for quite some time still. The following will describe the steps to install both versions on the same machine.
The methods described in this article are not supported by Best Software/SalesLogix. I take no responsibility if things get screwed up by doing this - so don't blame me ;-). Use at your own risk, yadda, yadda. That said, I've done this, as well as many employees at Best Software with no known problems to date.
If v5.2 is already installed:
If v5.2 is already installed then you need to change the uninstall keys in the registry before installing v5.0. The v6.0 install looks for these keys to determine if v5.2 is installed or not.
The uninstall key is located at:
HKEY_LOCAL_MACHINE:software\microsoft\windows\currentversion\uninstall
Simply rename all keys located there that begin with SalesLogix to something else. Now you can install v6.0 and it will not detect that v5.2 is installed (since it won't find the uninstall keys).
If v5.2 is NOT already installed:
If v5.2 is not already installed then install v6.0 first. Then install v5.2 after. Make sure you pick a new Program Group to install the shortcuts (so you don't get the v6 and v5 shortcuts in the same directory or overwrite some of the shortcuts). Also, make sure you don't upgrade the existing installation that the v5 install finds (the v5 install will recognize the v6 install as v4).
The get the Advanced Outlook functionality to work, place the v5.2 and v6.0 SLXAB32.dll and the SLMN.dll in their respective install folders and then start the client through the use of a batch file which unregisters the current DLL and registers the proper one for the version being started (ie: you need to switch between which one is registered based on which client you are starting). To silently unregister a DLL you would use "regsvr32 /u /s slxab32.dll" and to silently register a DLL use "regsvr32 /s slxab32.dll".
To get the Intellisync to work, copy the pSLXConnector.dll from a v5.2 install into the Program Files\Common Files\PumaTech Shared folder replacing/renaming the existing. This allows the proper connection dialog to login to a v5.2 database.
Crystal Reports with both versions fails for both versions. Potential problems with SpeedSearch indexes, but generally appears to work correctly.
Sync Server and Sync Client on the same machine may not be reliable. This does work in some cases but it will likely not work. If you need to demo or work with both versions then you should look at using VMWare or something similar.
- The default directory & registry locations for v6.0 are the same as for v4.x. This will make it impossible to run both v6.0 and v4.x on the same machine.
- Content taken from various employees from Best Software and a handout given at the 2002 Business Partner conference (sorry, I forget who put that together but I think Chris Reich deserves some credit).
|
|
|
|
|
|
Rate This Article
|
you must log-in to rate articles. [login here]
|
|
|
|
Please log in to rate article. |
|
|
|
Comments & Discussion
|
you must log-in to add comments. [login here]
|
|
|
- subject is missing.
- comment text is missing.
|
|
|
| Credits...
Posted: 11/14/2002 1:32:54 AM | fiogf49gjkf0d Please note in the 'Notes & Credits' section that this information was taken from a handout from SalesLogix at the Business Partner conference. I wish I knew who put that together so I could credit that person. If someone knows who it was then send me an e-mail. Chris, was it you?
-Ryan | |
|
| Credits
Posted: 11/27/2002 9:56:36 AM | fiogf49gjkf0d I am pretty sure it was Chris Reich that put this together. | |
|
| Don't give credit
Posted: 12/4/2002 11:50:58 PM | fiogf49gjkf0d I know some folks within SLX that are pretty pissed that this info is circulating. It would be in our best interestes to go spouting names at this point in time. | |
|
| I'm sure they are...
Posted: 12/5/2002 4:25:53 PM | fiogf49gjkf0d I am sure they are pissed at the idea of trying to support problems that might occur by having both installed together. BUT, there was a huge concern in the business partner community about not being able to run both - since we will be supporting both for quite some time to come. It is not reasonable to think that we will all use one of the versions via VMware or something. Could you imagine if you had to run a large import in a virtual VMware OS? Not a good scenario, you're already sharing mememory between the two OS's. I could not imagine working that way. I am sure there are issues and it is definately one of those "do at your own risk" kind of thing.
Anyway, I think whoever put this out the info used in this article *should* receive credit, and be commended, for realizing a huge need in the BP community and sticking their neck out for us.
-Ryan | |
|
| Re: Installing v5.2 and v6.0 on the same machine
Posted: 3/22/2007 4:53:47 PM | fiogf49gjkf0d Are there any updates to this for running 5.2 and 7.0 on the same machine?
Thank you ! | |
|
| Re: Installing v5.2 and v6.0 on the same machine
Posted: 3/22/2007 5:02:44 PM | fiogf49gjkf0d Hi Ian,
I'm happy to say I don't any have 5.2 systems I get into enough to have even tried doing this with v7 installed. I would guess that the steps would be the same.
However, the recommended route is to use a virtual environment for one of the systems (VMWare, VirtualPC, etc) | |
|
|
|
|
|
Visit the slxdeveloper.com Community Forums!
Not finding the information you need here? Try the forums! Get help from others in the community, share your expertise, get what you need from the slxdeveloper.com community. Go to the forums...
|
|
|
|
|
|