"The DataSource service is not available" On Adobe 2016.0.17+325979

[DaveL]

Commandbox updated the Adobe engine last night with the latest version, Adobe 2016.0.17+325979. However, once I started up the server via server start none of my datasources were available. When I attempted to log into the CF administrator, I received the following error message:

Did anyone else encounter the same issue?

I did not have any issue when using the old-fashioned ACF server’s update process on a standalone installation without Commandbox. Perhaps something didn’t transfer correctly when creating the War package for this version?

[kbutterly]

I am having the exact same issue:

Error with new CF Engine

Good morning! I have been using CommandBox for some months and it was working great. I am using CommandBox 5.2.1. When I started one of my sites this morning (I have a .json file for each site), apparently a new CF engine was downloaded. I am now getting this error “The DataSource service is not available.” To be honest, right now I just need to get my sites working. These sites are for a Fortune 100 company. I cannot find the syntax to specify a specific version of CF in my .json file. …

If I get a solution, I’ll try to remember to post it to you.

[DaveL]

@kbutterly,
Assuming you want to use Coldfusion 2016 like me, stop the server using server stop in Commandbox and change this line in your server.json file from:

"app":{
   "cfengine":"adobe@2016"
 }

to

"app":{
   "cfengine":"adobe@2016.0.16.320445"
 }

That change tells Commandbox to use a specific version of Adobe Coldfusion (release 16). When you start the server using server start you should see the last version fire up again.

Note: You can get a list of available versions here:
https://www.forgebox.io/view/adobe#versions

[bdw429s]

Please grab the latest version of CFConfig and see if this fixes your issue. Adobe changed how they parse the datasource XML file in the latest updates.

CommandBox> update --system

[DaveL]

That appears to have done the trick! Thank you @bdw429s!

[Will_Mulder]

Hi, I have exact same issue… would love to fix it however I don’t really use the CommandBox cli so not sure what grabbing ‘the latest version of CFConfig’ will do… I’ve beautiful handrolled cfconfig.json which I’d hate to lose if I did the wrong thing… Perhaps you can point me towards how to fix by modifying the json?
Thanks, Will

[bdw429s]

@Will_Mulder Just run the command I showed above. That is how you get the latest version of CFConfig.

You can read more about how CommandBox CLI handles packages in the docs:

https://commandbox.ortusbooks.com/package-management/installing-packages

https://commandbox.ortusbooks.com/package-management/system-modules