4/30/2024 4:30:25 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
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!
Forum to discuss networking and miscelleanous technical topics. View the code of conduct for posting guidelines.
|
|
|
|
SlxSearchTrigger.dll
Posted: 09 Jun 07 5:49 PM
|
Has anyone seen this error:
The description for Event ID ( 4 ) in Source ( SlxSearchTrigger ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Execute Method: WriteToDB procedure: LoadDBIndexes procedure: Access violation at address 0A0A1E01 in module 'SlxSearchTrigger.dll'. Write of address 4974656B.
It's occurring on a 7.0.1 installation. The SlxSearchTrigger.dll version is 7.0.0 and according to the version map, that's up to date (I couldn't find it on the version map, actually, leading me to believe that it's not been updated since 7.0.0).
I'm also encountering an error that says "Failed to connect to SLXServer. Check if server is running and is compatible with the current provider version". The slxserver.exe is at 7.0.1, the slxoledb.dll is 7.0.1. I've tried to install the slxsystem.exe and have it run as a service (following Sage's instructions), but it never installs itself as a service (i.e., it never shows up in services". When I run the slxserver manually, I get one entry: "E-Failed to start accepting clients at port xxxxx", where xxxxx is the port number which changes. To top it all off, everything is running on a windows 2003 x64 server, which I can't find docs to say it is or isn't supported by Sage. But I have my suspicions it's related. Unless, of course, someone can give me some insight into something! 
Thanks,
Jeff
|
|
|
|
Re: SlxSearchTrigger.dll
Posted: 02 Jul 07 1:26 AM
|
Jeff - did you ever track down the source of the "E-Failed to start accepting clients at port xxxxx" error?
We have a client with a Citrix installation that is getting the same error on startup of SLXSystem as a service. For some users only...
Cheers
Phil |
|
|
|
Re: SlxSearchTrigger.dll
Posted: 03 Jul 07 3:16 AM
|
Jeff - if it's not installing as a service this typically means it's already running. To completely eradicate this you need to do this (reboots are v.important).
1) Kill any slxsystem.exe's that are running using task manager
2) Start | Run | c:\program files\saleslogix\slxsystem.exe /Uninstall
3) Reboot
4) Check no slxsystem.exe is running via task mgr (if there are, kill them)
5) Start | Run | c:\program files\saleslogix\slxsystem.exe /Install
6) Reboot
|
|
|
|
Re: SlxSearchTrigger.dll
Posted: 04 Jul 07 4:01 AM
|
@Phil: Nope, never found the solution. I ended up handing the project off to someone else, so I'm not sure if they've found a solution or not.
@Mike: I was going from memory, and forgot step 1.  I sent that to my contact the next day. Just never posted the follow up on that part. Thanks for your follow-up, though.
Jeff
|
|
|
|
Re: SlxSearchTrigger.dll
Posted: 24 Aug 08 11:30 PM
|
I also found this kind of trouble (E-Failed to start accepting clients at port...) when using SLX 6.2.x in one of our Terminal Server.
I realized that after some time if there is no activity related with SalesLogix, the SLXSystem will shuttingdown. And if any ordinary terminal server user using SalesLogix Client after the SLXSystem shutdown, the SLXSystem will woke up but with the credential of that user. That's why, the SalesLogix Client won't responding.
And here is the remedy:
Make sure that no other user logon to the server, except the Admin (local or domain).
Add the registry key HKEY_LOCAL_MACHINE\SOFTWARE\SalesLogix\ShutdownDelay(DWORD). The key accepts values 1 through 1440, where the value indicates the number of minutes the service will run before shutting down (after it detects no activity). Setting the value to 0 indicates the service never shuts down.
Start the SLXSystem service. Voila it works, because the SLXSystem never shutdowns and ready to accept any SalesLogix client request. 
Hope it helps,
*fajar |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|