Showing results for 
Search instead for 
Do you mean 
Community Home Request Access Read Blogs Share Your Ideas Search Community View My Settings
Reply
Copper Super Contributor
Posts: 172
Registered: ‎07-06-2010

SDATA 404 Error after upgrading to version 8

[ Edited ]

We are trying to implement our Mobile 3 solution and the out of the box deployment for both SDATA and Mobile are failing. Again, this is straight out of the box, no customizations have been applied. Both the mobile and SDATA implementations are on the same server for testing purposes at the moment, but this is also occuring with remote requests (we have added the appropriate headers to the IIS projects).

 

We are getting a 404 on the following SDATA call from Mobile:

http://sdataserver/sdata/slx/system/-/%24service/getCurrentUser?_includeContent=false&format=json&_t...

 

Our SDATA implementation itself loads correctly. We have confirmed this by visiting the $systems/adapters URL and all the entities appear successfully both locally and remotely.

 

This URL from our Mobile 2.1 implementation pointed at a 7.5.4 database works:

http://sdataserveron754/sdata/slx/system/-/%24service/getCurrentUser?_includeContent=false&format=js... 

 

Again, both instances work correctly when querying the service's adapters. The 8.0 SDATA instance is pointed at .NET 4.0.

 

The event viewer shows the following. I have confirmed that there is a wildcard handler implemented correctly per the documentation for the SDATA project and its pointed to the 32 bit ISAPI handler for .NET Framework 4.0:

2013-12-11 09:37:43,357 [1] ERROR ASP.global_asax - Sage Integration Messaging MessagingService unhandled exception [SalesLogix Error Id=SLX65FC54161C07C6EE]

{

"slxErrorId": "SLX65FC54161C07C6EE",

"mitigation": "AjaxMessagingServiceError (404)",

"date": "2013-12-11T09:37:43",

"utc": "2013-12-11T15:37:43",

"message": "Unable to locate a handler to process the request 'slx/system/-/$service/getCurrentUser'.",

"source": "Sage.Integration.Adapter.AdapterController+RealAdapterController, Sage.Integration.Server, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3f422f0ff54abde1",

"type": "Sage.Common.Syndication.DiagnosesException",

"stackTrace": " at Sage.Integration.Adapter.AdapterController.RealAdapterController.Process(IRequest request)\r\n at Sage.Integration.Adapter.AdapterController.RealAdapterController.ProcessWorker(IProtocolRequest protocolRequest)\r\n at Sage.Integration.Adapter.AdapterController.Process(IProtocolRequest request)\r\n at Sage.Integration.Messaging.MessagingService.Process(IProtocolRequest protocolRequest)",

"targetSite": "Void Process(Sage.Integration.Messaging.Model.IRequest)",

"hashCode": "FA95BF4E-0BF61BCF-51D5A681",

"pid": 4980,

"identity": {

"name": "ADMIN",

"isAuthenticated": true,

"authenticationType": ""

},

"logger": {

"level": "ERROR",

"location": "Sage.Platform.Diagnostics.ErrorHelper.LogException(:0)",

"name": "ASP.global_asax",

"message": "Sage Integration Messaging MessagingService unhandled exception [SalesLogix Error Id=SLX65FC54161C07C6EE]"

},

"request": {

"looksLikeAjax": false,

"isLocal": true,

"method": "GET",

"url": "http://localhost:5697/sdata/slx/system/-/$service/getCurrentUser?_includeContent=false&format=json&_t=1386776163715",

"referrer": "",

"ipAddress": "127.0.0.1",

"userAgent": "Mozilla/5.0 (Windows NT 5.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36",

"userLanguages": "en-US; en;q=0.8"

},

"browser": {

"type": "Chrome31",

"name": "Chrome",

"version": "31.0",

"majorVersion": 31,

"minorVersion": 0.0,

"platform": "WinNT"

},

"server": {

"machineName": "SLX8PREDEV",

"timeZone": "Central Standard Time",

"commandLine": "C:\\WINDOWS\\SysWOW64\\inetsrv\\w3wp.exe -a \\\\.\\pipe\\iisipmbfdfef34-9e75-45ec-9cdd-b6417d40bfc6 -t 20 -ap \"SLX8\"",

"versionString": "Microsoft Windows NT 5.2.3790 Service Pack 2",

"is64BitOperatingSystem": true,

"host": {

"siteName": "SLX8",

"applicationId": "/LM/W3SVC/86299172/Root/sdata",

"applicationPhysicalPath": "E:\\inetpub\\SLX8\\sdata\\",

"applicationVirtualPath": "/sdata",

"isDebuggingEnabled": false,

"isHosted": true,

"maxConcurrentRequestsPerCPU": -1,

"maxConcurrentThreadsPerCPU": -1

},

"logonUser": {

"name": "WebDll",

"authenticationType": "",

"impersonationLevel": "Impersonation",

"isAnonymous": false,

"isGuest": false,

"isSystem": false

}

}

}

 

 

 

Copper Super Contributor
Posts: 172
Registered: ‎07-06-2010

Re: SDATA 404 Error after upgrading to version 8

When comparing the 2 installs, one thing I notice on the working 7.5.4 box is there is an additional ISAPI handler installed called SalesLogix ISAPI that points to an SlxWeb.dll assembly in the webroot AdminScripts folder. That is NOT present on the 8.0 machine. Is this required for SDATA? The error to me potentially jibes with this missing file.
Copper Super Contributor
Posts: 172
Registered: ‎07-06-2010

Re: SDATA 404 Error after upgrading to version 8

So this took pretty much an entire reinstall of SLX 8 to work through. We had a number of issues applying the LAN bundles as well as the Mobile 3 VFS, but after rebuilding everything seems to be working.