SSIS: Unable to retrieve column information from the data source. - ssis

I know there is similar question, but it didn`t helped me.
When I execute a package data flow task fails with the error:
"Unable to retrieve column information from the data source. Make sure your target table in the database is available."
I refreshed the source component, the destination components also. The table do exist in database. I tried with setting some parameters like "Always Use Default Code Page" to true but didn`t helped.
Connections are also ok.
Any idea?

Sounds like a permissions issue. Try, running Visual Studio as administrator or if that doesn't work, make sure your Windows Account has access to the data you require in SQL Server.

Related

How do I amend shared data source definitions after SSRS migration to a diff node?

Do not seem to be able to find any place in the portal or Report Builder where I can actually edit the connect string & creds.
Report Manager shows the XML, but that really is it.
Disk files (from the looks of it) are no longer present in high versions (using SQL 2016/2017).
Is there a known location anywhere in GUI, or maybe direct edits in the SQL Server repository?
I can't even delete a shared source anymore, only view or test the connection.
If anybody could post a screenshot, it'll be highly appreciated.
EDIT: Just found out - when I create a new Data Source, it's editable; the imported data sources are not.
There are two ways of doing this. You can set the 'overwrite datasource' option in the project properties.
Or, you can got to the report portal , show hidden items in the view menu and there is a folder called "data sources". Open this and you will see all data sources, from there you can edit and save changes. All reports that use that datasource will be affected.

There was an error while loading the package SSIS

I have created one SSIS package for data flow and its perfectly working fine for me (with my credentials). However, when its opened by another person with another login ID (credentials) its showing error:
Please see the below screenshot.Looks like its an access error. How can I give access so that anyone can open it.
The error I'm getting is :
the operation failed because the databse manager failed to access either the databse manager configuration file or the database configuration file.
There ware errors while loading the package. See the error list for details.
Error loading Package.dtsx. Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified satte. You may not be
authorized to access this information. This occurs when there is a cryptographic error. Verify that the correct key is available.
Upon searching on net. I think I can set "DontSaveSensitive". However,unable to find out how to do this? Whats are the steps I need to follow?
Link : https://learn.microsoft.com/en-us/sql/integration-services/security/access-control-for-sensitive-data-in-packages
How to resolve this?
Kudos for pinpointing issue. To solve it:
Open project solution from working credentials.
Right click on project.
Go to properties
Change the security level to DontSaveSensitive.
I've answered your question about unable to find out how to do this
Hope this works. Else come back here and we might suggest different approach.

Set up a Datasource for Tabular Models in SQL Server

I want to go through this tutorial. Unfortunately the author has already set up the datasources
and does not explain how to set them up. First off I installed an separate SSAS Instance in my sql server 2014. Then I tried to add a .mdf file via "Attach" but get the Error "AdventureWorks.detach_log could not be found in the folder". So according to this SO solution I tried this command:
CREATE DATABASE YAFnet ON (FILENAME = N'C:\sql_data\YAFnet.mdf')
FOR ATTACH_REBUILD_LOG;
within my SSAS instance query editor but it looks like the query is not a proper one since it is mdx.
Anyone who can help me to get a datasource (adventureworks dw) for my tabular model so I can follow the tutorial?
I would download the tabular backup from AW samples and recover the .abf file

Report Server - Unable to Change Name of Folder

I am unable to change the name of a folder on the report server. I am trying to do so through the web interface. The name of the folder is Audit_Reports. I want to chanage it to Audit Reports (space instead of underscore). However, when I try to do this I get the following error: "The folder, report, resource, model or data source /Audit_Reports already exists."
I am able to change it to Audit-Reports. Then when I try to change it from Audit-Reports to Audit Reports it give me the same error except it says Audit-Reports already exists. I also changed it to Audit-Report without the s and then to Audit Reports but that did not work either.
This obviously is not a big deal, but it is really bothering me and hopefully someone out there smarter than me knows the solution.
Thanks.

How to fix method saveastext of object failed?

This is Access 2003. From an access database code module, I am opening two outside access databases and then saving the text of two forms that exist in both of the databases. I am executing the statements:
Call app1.SaveAsText(acForm, "MyForm", "c:\MyForm_app1.txt")
Call app2.SaveAsText(acForm, "MyForm", "c:\MyForm_app2.txt")
Both app1 and app2 are of type Access.Application.
I receive the error:
Method 'SaveAsText' of object ' Application' failed
This error only happens on this specific app2 form. Other forms in app2 are saving just fine. I am using Access 2003. There was a trial of Access 2007 installed but now that is removed. I am still getting the same error.
Thanks for your help. I am really puzzled over this one.
Gotta love undocumented options. For kicks and giggles, I'd try renaming one of the two forms. Or, swap the two statements and see if app1 starts erroring. It looks like the forms has identical names, perhaps Access is leaving the first one open and getting confused.
Maybe something is slightly corrupt in app2. You could always try running the /decompile option on app2 (take a backup first of course)
That form is possibly corrupt. See if you can open that form in Access and then save it under a different name. Or import the entire database into a new file.
The problem was that there is a bug in Access 2003 where it cannot handle databases converted from Access 2007 to Access 2003. The fix is to install the latest Service Pack for Office 2003.