Network Automation Software We are currently migrating this forum
over to our HelpSystems domain. Please
post all new threads in our new
HelpSystems Community Portal.
Post to the HelpSystems Forum
You are not currently logged on. You must be logged on in order to post. Log on
Or Create a new account
AutoMate Discussion
Decrease font size
Increase font size
Topic Title: Export 10 -> import 11: SQL issues
Topic Summary: 11.0.2.22
Created On: 12/28/2017 08:32 AM
Status: Read Only
Linear : Threading : Single : Branch
 Export 10 -> import 11: SQL issues   - Edward Hulleman - 12/28/2017 08:32 AM  
 Export 10 -> import 11: SQL issues   - Ricardo Castaneda - 12/28/2017 09:17 AM  
 Export 10 -> import 11: SQL issues   - Edward Hulleman - 12/28/2017 09:42 AM  
 Export 10 -> import 11: SQL issues   - Ricardo Castaneda - 12/28/2017 09:45 AM  
 Export 10 -> import 11: SQL issues   - Edward Hulleman - 12/29/2017 07:25 AM  
 Export 10 -> import 11: SQL issues   - Mary Manzano - 12/29/2017 12:11 PM  
 Export 10 -> import 11: SQL issues   - JamesLankford - 01/03/2018 08:37 AM  
Search Topic Search Topic
Topic Tools Topic Tools
View similar topics View similar topics
View topic in raw text format. Print this topic.
 12/28/2017 08:32 AM
User is offline View Users Profile Print this message

Author Icon
Edward Hulleman
Artisan (200-499)

Posts: 232
Joined: 11/07/2006

I still have some tasks running in version 10 because 11 gave issues.
Today I installed the latest version of 11.
Then in 10 I exported the task to .ampkg and imported the file in 11.

It results in a task with three issues:


1. Connection string

The connection string it uses to connect to an SQL database returns a Login failed for user ''
But there is a user mentioned in the string:

Provider=MSDASQL.1;Password=XXX;Persist Security Info=True;User ID=XXXs;Data Source=GGCCOGSQL;Initial Catalog=CognosTables


2. SQL statements are empty.
It only shows the Session name and the dataset it has to fill, but no query.
To continue testing I copy the query manually.


3. The loop datasets loops while it is empty
The sql returns no data (which is correct), but still Automate enters the 'loop dataset'.
What it should not do because it is empty, so it immediately starts returning errors because fields do not exist.


So it looks like I have to stick to 10 for another while ?
Statistics
18258 users are registered to the AutoMate Discussion forum.
There are currently 0 users logged in.
The most users ever online was 6686 on 11/01/2020 at 01:24 AM.
There are currently 1655 guests browsing this forum, which makes a total of 1655 users using this forum.

FuseTalk Enterprise Edition v4.0 - © 1999-2020 FuseTalk Inc. All rights reserved.

Sitemap Network Automation Software Blog