Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Saturday, June 7, 2025 
 
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!
 Web Forums - SalesLogix Web Platform & Application Architect
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to SalesLogix Web Platform & Application Architect | New ThreadView:  Search:  
 Author  Thread: Find out current SLX App Server for a given database
Marcos Orfila
Posts: 40
 
Find out current SLX App Server for a given databaseYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 26 Jul 13 8:21 AM
fiogf49gjkf0d

Hi,


 


For every SalesLogix database, there can only be one Application Server. Given a SalesLogix database, how can I tell what's the Application Server connected to it?


 


Regards,


 


      Marcos


 

[Reply][Quote]
Marcos Orfila
Posts: 40
 
Re: Find out current SLX App Server for a given databaseYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 26 Jul 13 3:23 PM

Got the answer from Mike Spragg in the SalesLogix Community:


Looks in systemino table - the pingserver is the servername



[Reply][Quote]
 Page 1 of 1 
  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!
 

 
 slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.
 This site, and all contents herein, are Copyright © 2025 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 6/7/2025 6:54:43 AM