The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
SLX v7.0 Implementation
Posted: 18 Apr 07 9:24 AM
|
Help!
I have established a test environment with the SLX 7.0 server connection to the v7.0 copied database by installing the Standard Server Tools. However, I am not able to bring up the Architect or Administrator due to a Windows compatibility error I suppose. It reads:
Architect has encountered a problem and needs to close. We are sorry for the inconvenience.
Then you can send the failure report to Microsoft.
Also, from our virtual environment, the client starts but freezes during the initialization. Any ideas? Did I leave out an important step or am I suffering from purely a Microsoft issue? I loaded the SLX 7.0 Server on a Windows XP Pro computer with all the Standard 7.0 Server options. |
|
|
|
Re: SLX v7.0 Implementation
Posted: 18 Apr 07 11:14 AM
|
| Upgrade to SP1. Likely the problem you're running into is that you have the DST patch from MS applied on the box, which breaks SLX. You can run the SP1 exe's on a 7.0 database just to get everything initially tweaked but I would upgrade to the SP1 bundles ASAP. In fact, I generally do that before I start testing any of my customizations just in case they update a Form (i.e. Account Details) that I have a custom version of. |
|
|
|
Re: SLX v7.0 Implementation
Posted: 18 Apr 07 11:55 AM
|
The server Tools problem is now resolved using the DST fix. Now, my problem solely resides with the following errors on the clients:
Exception EOleException: Invalid object name 'FEATURESECURITY'
Exception Location: [00569CF9]{SalesLogix.exe}
Will the Service Pack 1 possibly fix this? Does anyone have it to send? We lost our old admin and since, I have no updates sent to me. What site do I go, to get this update? I know we pay SLX for updates. |
|
|
|
Re: SLX v7.0 Implementation
Posted: 18 Apr 07 12:16 PM
|
Make sure the conversion bundle is applied using the conversion process in 6.x. This locks it out of being a 6.x database. Once the database has been restored in your 7.0 environment (mine is kept separate) then you must also run the "upgrade x to 7.0" bundle. Missing one or both parts will likely produce similar problems.
Regarding getting SP1, you can use support.saleslogix.com if you stay regular on your maintenance contract. It sounds like you do so unless you have the login credentials, you may have to call someone at Sage to get the information. You'll want the login so you can stay regular with service packs AND hotfixes, not to mention using the knowledgebase and other points of interest. |
|
|
|
Re: SLX v7.0 Implementation
Posted: 20 Apr 07 10:24 AM
|
fiogf49gjkf0d I have implemented v7.0 and Service pk 1 both on the server and client (test environment). At this point, I noticed that my client view is limited to only campaigns. For information sake, I think its best to note that I'm receiving a few initialization errors when starting the client.
1) Startup error: Included script: SYSTEM:SLX LEAD SUPPORT, is missing
2)Starup error: SYSTEM: SLX UTIL, is missing
The first error I thought I resolved with adding "key" to the end of the script within the architect. It seemed to have cleared the same error that I was experiencing with the server computers client. In otherwords, I loaded the client on the server aswell and it fixed the client startup error there.
Do you have any suggestions? |
|
|
|
Re: SLX v7.0 Implementation
Posted: 21 Apr 07 4:57 PM
|
fiogf49gjkf0d Sounds like you did not run in all the bundles.
You need to follow the SalesLogix provided instructions ..
--
rjl |
|
|
|
Re: SLX v7.0 Implementation
Posted: 23 Apr 07 9:12 AM
|
fiogf49gjkf0d Actually, I called myself running all the available v7.0 bundles and serice pack 1 bundles. Now, I excluded the web bundles because we only use SalesLogix internally. The remote users we have utilize Terminal services or straight VPN to their desktops. |
|
|
|