1

Unable to access Could Services from “Inventory>Cloud Services” menu item

6 Spice ups
2

I’ve had this issue as well. Show an application error.

3

Did you guys use fresh data when installing Beta 4, or did you go over the top of your Beta 3 data?

If you went over the top of your Beta 3 data, and didn’t start fresh, you’ll see this bug.

I noticed this bug yesterday morning, too late to fix it for Beta 4. The cloud services detection feature pulls a list of known services from the community, and during the last server update, we updated those definitions. When the app downloaded those definitions and updated it’s internal list, definitions that were removed didn’t delete their corresponding detections, which is causing the bug you’re seeing.

You’ll be happy to know it’s fixed and will be good to go for RC.

To fix it, you can delete your data and start from fresh, or if you really want to keep that data, you can open the SQLite database with a tool like SQLite Manager and delete all the records in your “scanned_addresses” table. That will let you use cloud services again.

Remember, it’s important to start each beta fresh with new data to prevent errors like this from happening. Betas don’t require compatibility between versions. :slight_smile:

1 Spice up
4

No issues accessing it for me. I did a upgrade from B3

5

The issue will only happen if you’ve detected a service that we deleted.

We deleted Savvis, Comodo Enterprise SSL, CloudFlare, ServerBeach, DynDNS and Amazon S3.

If you had one of those detections on your network, and didn’t install with fresh data, cloud services will go boom.

6

curtismorrow wrote:

Unable to access Could Services from “Inventory>Cloud Services” menu item

It has been renamed “Would Services” (sorry I had to) :wink:

1 Spice up
7

Removed all canned_addresses from the database… still no luck.

8

Before I get dinged for spelling I meant to type “scanned_addresses” instead of “canned_addresses”

9

You cleared the data from the scanned_addresses table, did you restart Spiceworks?

Can you please restart Spiceworks, visit Cloud Services and then send me your log files. I will PM you with instructions on how to do so.

Thanks for helping test the beta.

10

curtismorrow wrote:

Before I get dinged for spelling I meant to type “scanned_addresses” instead of “canned_addresses”

You are so lucky I was out to lunch!!

11

Tim’s suggestion to remove all the scanned_addresses worked for me