Sdata has not been included as part of Sage 50 Accounts for several versions, as it was removed in v28. To use Sdata, you must download and install it separately from this link: https://github.com/Sage/sdata-downloads.

I can confirm that Sdata is compatible with the 32-bit & 64-bit version of v30.

If you wish to install the 32-bit version of v30, you can do so, but you'll need to uninstall the 64-bit version first. You can find the download link here: https://gb-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=231221103548697.

Ian

Thanks Ian.  I rolled back to 32bit by uninstall and reinstalling as suggested and this now works with SDATA.

I already knew SDATA was separate as have been using it live for v29 without issue.   The moment I rolled back to 32bit all works and I can see sdata under the Tools->Internet Options without doing anything more. When I install 64bit, this vanishes and the endpoints dont work.  I have removed and reinstalled sdata using the above link and get the same behaviour.  When I check the sdata service is running without issue and nothing in the logs - so dont have much to share identify the cause.

Is there actually any benefit to running the 64bit version?

Very much appreciate your quick response.

Hi,

On the 64-bit version, the option won't show in Tools > Internet Options but 3rd party apps should continue to work.

I've asked Darron Cockram  to respond and give a bit more insight and collect any errors you may have captured.

The main benefit is compatibility with 64-bit Office and additional memory. The 32-bit version can only use 4gb of your computer's memory, even if your PC has 32gb as an example. It also brings the application architecture up-to-date with Microsoft, giving us greater flexibility with development.

Ian

The reason why nothing shows in Tools -> Internet Options is because the addin that the Sdata installer registers is 32 bit and the 64 bit version of Accounts cannot load it. The 32-bit version of Accounts can of course load it, which is why you see it in that version. There is no 64 bit version of Sdata and no current plans to produce one I'm afraid , so there is no workaround for this issue. However this is not the reason why the feeds do not work.

The Sdata feeds are in fact working but the reason why you get nothing returned is because a registry key that Sdata uses to determine where Accounts data can be located uses a 32-bit location as it is a 32-bit application, but the 64-bit version of Accounts writes to the 64-bit location in the registry. In this case there is a workaround though. After installing the 64-bit version of Accounts open a command line and run the following

reg add "HKLM\SOFTWARE\WOW6432Node\Sage\Line 50\SettingsFolder" /d C:\ProgramData\Sage\Accounts\2024

Then restart the Sdata service and your Sdata feeds will work as normal.

Hope that helps

Hi Doram

We have 64-bit v30 installed and also downloaded the sdata as per the link. Restarted the service. I assume the URL remains the same.

But when we enter the url to test it continously asking for username and password.

Also what is the best way to find the UUID etc for correct url?

Appreciaate your help in advance.

Hemal Jadav said:

I assume the URL remains the sam

The Sdata URL would be unchanged across versions

Hemal Jadav said:

But when we enter the url to test it continously asking for username and password.

Suggests credentials are being provided or that the dataset is in an invalid state.

Hemal Jadav said:

Also what is the best way to find the UUID etc for correct url?

You can query the endpoints URL. See here for more info: https://sage.github.io/SData-2.0/pages/core/1405/

Hope that helps

Hi Dokram

credentials are correct. I assuem since it is asking for the credentials url is also correct.

How do we check the dataset state?

Kind regards

Hemal

Hi Dokram

I found the enpoint url as http://servername:5495/sdata/accounts50/GCRM/{6447298A-F14B-48EA-9EAC-A3955968B321}-1

do you think that is where the problem is and how to resolve

Kind regards

Hemal

The URL is not the issue if Sdata reports this as the correct endpoint in the registry. Given you are being prompted for credentials the URL is a valid one. The problem is that the credentials you are supplying are not valid for the dataset, or the dataset is in a state that it cannot be used for some reason. Confirm that the dataset is available in the Accounts UI and that you can log on to that with the credentials you are trying to use.

HI Dokram

I have been able to logon to sage on the same machine with same credentials

Kind regards

Hemal

 In that case the most likely problem is that the dataset you are trying to connect to via Sdata is not the same one as you are connecting to in the UI.

 In that case the most likely problem is that the dataset you are trying to connect to via Sdata is not the same one as you are connecting to in the UI.

HI Darron

sorry for misspellling your name so far.

All we did is update the sage from version 28 to version 30 with 64 bit. Prior to upgrade the sage was on 32 bit.

Also I did install the sdata on top of the upgrade as suggested in very first point on this discussion. Restarted the data service. Also updated the registry.

As there is only one company in sage and it does list the url as I mentioned above. If that is not correct then how do i get the correct url for upgraded version 30?

Kind regards

Hemal

Hemal Jadav said:

As there is only one company in sage and it does list the url as I mentioned above. If that is not correct then how do i get the correct url for upgraded version 30?

Sdata must be seeing more than 1 dataset otherwise you'd never see a -1 in the dataset URL so I'm guessing that you aren't looking at the same thing in the Accounts UI as Sdata is configured to use.

Is 'servername' in your URL the same machine you are using the Accounts UI on?

On the server PC open a command prompt and run the following:

reg query "HKLM\SOFTWARE\WOW6432Node\Sage\Line 50\SettingsFolder"

That will tell you the folder that Sdata is using to detect datasets

Hi Darron

Below is the result of command prompt run

reg query "HKLM\SOFTWARE\WOW6432Node\Sage\Line 50\SettingsFolder"

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Sage\Line 50\SettingsFolder
    (Default)    REG_SZ    C:\ProgramData\Sage\Accounts\2024

In that case this command will tell you which paths are registered for that version of Accounts (to be run on the server PC):

type "C:\ProgramData\Sage\Accounts\2024\company"

C:\PROGRAMDATA\SAGE\ACCOUNTS\2016\COMPANY.001

which is the correct path i use with the same credentials and able to logon successfully but with url it is going on loop of username and password

We must be missing something as the only way for an Sdata URL to end up with a '-1' suffix is if there is more than one dataset as the suffix is used to disambiguate when there are two or more datasets that share the same internal identifier.

Worth going back to basics. On the server PC stop the Sdata service. Whilst stopped delete all of the files in C:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\SDOAdapterLogsV2 and start the service again. Query the Sdata registry feed and confirm the URL(s) shown in there. Query a resource under your dataset endpoint.

If you are still seeing the same issue if you could share the logs from the above path as well as the raw results from the Sdata registry query and the exact resource URL you are attempting to use please.

Hi Darron

thanks for update. but while waiting for your update. I tried few things.

1. i have unistalled teh sdata adapter and since then i am not being able to reinstall it gives me an error

2. i created one more company from the backup data and check if it works but even on that also it keeps on going circle for username and password

Please advise

Kind regards

Heaml

That's the location for x86.

I would check your install location, If you're using 64 bit of Sage the program directory is likely C:\ProgramFiles\Sage\Accounts

1. You need to provide a folder that has the installation of 50 Accounts in it. As Ian says it looks like you are specifying the 32 bit location but have likely installed in to the 64 bit program files folder.

2. I'm a bit confused. If you have not be en able to complete the installation of Sdata how are there any feeds or endpoint available ?