[go: nahoru, domu]
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

while using Lysine 1.3.0.4300, i am not able to see Available External Column in Advance Editor #48

Open
abhikadamRP opened this issue Feb 15, 2022 · 4 comments
Open

while using Lysine 1.3.0.4300, i am not able to see Available External Column in Advance Editor #48

abhikadamRP opened this issue Feb 15, 2022 · 4 comments

Comments

@abhikadamRP
Copy link

AminoIssue

I have created the connection manager with EBCDIC file. also mentioned all the column with specified width. When i have attached the connection manager to Amino File Source in advance editor, i am not able to see the AVAILABLE EXTERNAL COLUMNS. It are blank. Can any one please help me on the issue.
@benharrell
Copy link
Collaborator

Hi, the external columns are not populated in Lysine. They should be an optional part of SSIS, do you have a need for them?

@abhikadamRP
Copy link
Author

Actualy after mapping the source to OLEDB destination. i am getting below error.

[SSIS.Pipeline] Error: Cannot find the connection manager with ID "{4A43099A-9F32-42A4-9636-40FF5FACF84F}" in the connection manager collection due to error code 0xC0010009. That connection manager is needed by "EBCDIC File Source.Connections[EBCDIC Connection]" in the connection manager collection of "EBCDIC File Source". Verify that a connection manager in the connection manager collection, Connections, has been created with that ID.

So after diging into it i found that the EBCDIC CONNECTION MANAGER columns are not been displaying in EBCDIC file source AVAILABLE EXTERNAL COLUMN.
So i thought it may be compulsury.

Can you please help me with above.

@paltman
Copy link
Member
paltman commented Feb 16, 2022

We have narrowed this down to an installation issue and are currently trying to determine root cause.

@abhikadamRP
Copy link
Author

Ohh, Ok. So after fixing the installation issue, will be able to resolve the above error. ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@paltman @benharrell @abhikadamRP