Cloud Storage

We are running AETL Enterprise 6.3.4.11 and whenever we drop a Cloud Storage object into a package and then try to configure it, we are getting an Access Violation error.

Also, should we see any type of Cloud Storage entry under the Connections in the project to configure? We don't have any Cloud Storage connection types in the left hand palette. We have all the usual connection types (MS SQL Server, FTP, Sales Force, etc) but no Cloud Storage.

Not sure if we should or not?

Yo probably need to patch the repository as described here

www.etl-tools.com/articles/cloud-storage.html

Thanks - that looks like it did the trick. We had everything in the repository except for the following from the patch:

INSERT INTO OBJECTS_TREE
(OBJECT_ID,
PARENT_ID,
NAME,
OBJECT_TYPE
)
Select
OBJECT_ID*-4 as OBJECT_ID,
PARENT_ID,
'Cloud Storage' as NAME,
905 as OBJECT_TYPE
From
OBJECTS_TREE
where OBJECTS_TREE.OBJECT_TYPE=322

Great.

BTW can you see MongoDB in the list of connections?
If not you may need to do more patching

Yes, we have MongoDB. I was pretty diligent about getting all the patching in place and also went through the create table scripts from the installer to compare all the tables and field types. We had everything pretty close and just missed this one for the record entries.

Hopefully we didn't miss anything else.

FWIW, it would have been very helpful if the installer would have alerted us to needing the repository patches or even taken care of them itself.

We were not aware of needing to do all the patching until we fired the new version up and it immediately started complaining about the missing nodes tables.

That lead us to do some digging and found most of the patching details to get the repository up to date.

We did however have an issue where the new version wiped out all of our global variables and email notification settings.

Thankfully we had a backup copy of the variable list available and were able to recreate the global vars without a considerable amount of effort.

We love the product and all the awesome stuff it does and most of the time we don't see any issues at all when upgrading versions - that lead us to be a little loose with our typical upgrade approach (we were a bit sloppy since we are used to the upgrades always being quick, easy and pretty much brainless).

Lesson learned.