08-20-2014 11:58 AM
Here's the scenario:
Main upgraded from 754 to 81
Remote upgraded from 754 to 81
..oops.. Intellisync was NOT un-installed first.. and now we have a sticky issue - BOTH SData nd Intellisync portal show up on remote on port 8087 and NOT having good resulte gettiing Isync out! - WIndows 7 system.
08-20-2014 02:04 PM
OK.. FINALLY got it ripped out....
BUT got an internal server error:500 on the SData portal (on the remote) - tried KB 1407604323 - did not fix it.. still error 500.
Getting ready to "nuke and pave" this remote.. any ideas out there?
08-20-2014 03:19 PM
OK.. so we un-iinstalled the SData portal on teh remote.. and re-installed it..
Now we get:
Personal Web Server stops responding or an error is returned for Serverhost
No matter what I do.. cannot get it to stay running.. and the contents of the SData "portal" is identical to another system :-(
08-20-2014 04:58 PM
OK.. Deteached Remote db.. completely un-install everything Saleslogix..
Did a NEW Remote Image install (includes SNC3)/reboot.... Serverhost will still not run. - Houston - we have a problem..
08-20-2014 05:15 PM
Here is the error info from the SERVERHOST failure on the Win 7 Remote..:
Application: ServerHost.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Exception Stack: at Sage.Web.Server.Configuration.WebSiteConfigurator.ConfigureServerList(System.String, Sage.Web.Server.Configuration.WebSiteList) at Sage.Web.Server.ServerHost.ConfigurationHost.GetServerList() at Sage.Web.Server.ServerHost.ConfigurationHost.Sage.Web.Server.ServerHost.IWebSiteHost.BeginHosting() at Sage.Web.Server.ServerHost.Program.Main(System.String)
Seems to indicate a problem w/ the (or some) .config file(s).. no closer..
08-20-2014 06:15 PM
Full circle.. got the ServerHost config issue fixed.. and back to an:
Internal server error: 500 - Invalid table name (again) on attempting a config inside Outlook
OK..I've been able to prove (using a browser window) ANY SData "query" to ANY table ON the remote to it's "local" SData portal (on 8087) will FAIL w/an Invalid Table Name error.
FYI - I can connect to the main SData portal and get data.. and mobility runs..
So calling all SLX dev.. what's broken here (on the remote)?