08-21-2014 05:03 AM
A - Did normal upgrade - portal (Serverhost) woudl not "work" (getting invalid table error)
B - Uninstalled just the SData portal part - rebooted - re-installed (including SNC03 patch) - rebooted - same error as "A"
C - Attempted to debug issue vis FF browser w/firebug running:
http://localhost:8087/sdata/slx/dynamic/-/userInfo same invalid table problem
D - tried other SData "queries" - all fail
.. at a dead end...
I'd assume the SData portal on a remote should respond like a normal SData portal.. and tried several approaches (ex: ..sdata/$system/adapters) - no joy.. dead end again.
Oh yes.. did a detach remote db.. complete un-install of remote.. rebooted - complete re-install - reattached db - same error - same dead-end. Looking at the logs provides no additional info (either Windows or the portal)
Anyone else seen this or have an idea as to how to fix?.. or have we found another day 0 bug?
Solved! Go to Solution.
08-21-2014 09:03 AM
08-21-2014 09:31 AM - edited 08-21-2014 09:32 AM
What table does it say is missing? What does the application event log say?
Keep in mind that when a query is run from the web browser, the browser will return the cached version of the response if there is one. When testing in the browser it is always a good idea to add a parameter such as t=N where N is a number that increases each time:
Alternatively, you can clear your cache before retesting.
08-21-2014 10:03 AM
I made sure there was a "clean cache".. and it make no difference as to which table you test on.. all fail.
The UserInfo is the on ethat is initially "touched" when you click on test in the Options connection setup in Outlook.
The other thing that turns out to be bogus.. is when you bring up the Properties window of the Saleslogix Personal Web Server and click on Manage.. it tells you you successfully connected to teh database.. NOPE.. all you did was successfully authenticate w/the web server :-) .. mis-leading feel-good message.
There's an open ticket on this: 801 022 4837
I did a session (over an hour) w/support this am.. no joy - so far. Could be something in SNC03 that broke it.. nobody knows at the moment.
08-21-2014 10:13 AM
Ok, thanks for the info.
Also, the SData query in question accesses the following tables:
08-21-2014 10:22 AM
Yep.. it does..
So what should the appidmapping record look like??.. the same as the "main" SData portal except:
08-21-2014 10:27 AM - edited 08-21-2014 10:38 AM
I'm not really sure what it should look like, but if it is empty...then that may be the issue. Looks like the AppIdMapping table is defined to sync from the Host to the Remote. You should also check the host database. The following is what the eval database has:
QSYST0000000 Saleslogix http://<server>:<port>/sdata/slx/gcrm/-/ ADMIN NULL ADMIN 2013-12-19 09:54:36.000 ADMIN 2013-12-19 09:54:36.000 T NULL NULL NULL NULL T NULL F NULL NULL
08-21-2014 11:55 AM
I was just looking at that (record).. and see the template/placeholders and wondering what a "new" remote cut off an 8.1 db looks like in this area. I'll probably run a test cut later today to see.
.. just made sure the endpointurl (field) was set like the template you posted.. and after attempting to "hit it" from Outlook/options/config.. it tosses back the same error (Invalid Table).. and does NOT change the appidmapping record. I was fairly sure it would not ;-)
a- The Saleslogix Personal Web Server is working just fine
b - "something is broken" in handling SData requests in general in the remote.. and I have no idea as to what it is..
08-21-2014 12:04 PM
I'm sure you've already done this, but you might check the connection.config for the SData portal to make sure it's correct. You may also be able to see the invaild table being queried in SLX Profiler.
08-21-2014 12:40 PM - edited 08-21-2014 01:09 PM
Here's what teh SLXProfiler is "unhappy" about:
Invalid table name. (SQL: "select COLUMN_NAME, DATA_TYPE, CHARACTER_MAXIMUM_LENGTH, DOMAIN_NAME from ORMCOLUMN where TABLE_NAME = ?")
So what this comes down to is.. we are missing SQL views in the remote db. The upgrade process is not creating the needed views and we end up with a "broken" SLX Remote DB.
IMHO - The upgrade process for Saleslogix Remote (Windows/LAN) is broken.
Here's a list of SQL views present in a main db and NOT in the (upgraded) Remote:
I'm sure we don't need all of these in the remote.. BUT from what I see at http://developer.saleslogix.com on teh DB.. it sure looks like we have to have the "ORM" ones!
I am also concerned about upgrading Remote Office Servers.. I've a customer w/5.. and my gut says they will "break" too.