"Execute on main package thread" (dts2000) still available on ssis ?

Hello

The Navision 4.0 ODBC-driver gives following error when connecting in ssis :
"Internal error 182 in module 1."
The driver doesn't like multi-threading behavior . In DTS2000, this issue could be solved by turning on the workflow-option "Execute on main package thread" !
I was wondering... is there a way to do this also in SSIS ?

Kind regards

Geert G.Interesting issue, for which I have no sure answer. Looking at the properties we have you may like to try the MaxConcurrentExecutables property at the package level, and the EngineThreads property for the Data Flow. These would I assume limit you to one thread, but if that is the main one, I have no idea.|||

Thank you for your reply

Unfortunately when I try to change the 'EngineThreads' to 1, following error occurs:
"Could not set the property value: Error at Data Flow Task [DTS.Pipeline]: The EngineThreads property of the Data Flow task must be between 2 and 60. An attempt was made to set the property to a value that is too small."

Even changing MaxConcurrentExecutables to 1 or 0 doesn't solve the problem

|||Sorry I didn't test this. Better ask someone who knows what they are talking about. Product Team over to you....

"...report server cannot access internal information..."

I've been unsuccessful getting Reporting Services 2005 to work after reinstalling SQL 2005. The RS service cannot connect to its database, as reported in the Event Log. If I visit http://localhost/Reports, I get the error "Key not valid for use in specified state. (Exception from HRESULT: 0x8009000B) (rsRPCError)"

I've used the RS Config Mgr to create a fresh database for it named SSRS (and SSRSTembDB), and it is set to use Service Credentials in the db connection. The RS service is running using the same admin account as MSSQL, .\SQLExec. I have confirmed that .\SQLExec is in the RSExecRole role in the SSRS database.

When I created the SSRS database, the Config Mgr had a green check for every step except the last. For "Setting Connection Info for the Reporting Server" there was a yellow '!', with the explanation, "Although saving the database connection succeeded, the report server cannot access internal information about this deployment to determine if the current configuration is valid for this edition. ..."

I examined rsreportserver.config to look for any issues. The <dsn> element has an encrypted string, the <ConnectionType> element says "Default", and the logon elements are empty. I could not find the db names, SSRS and SSRSTempDB, anywhere in the file. Where are these kept? I don't know what else to look for.

Also, in RS Config Mgr, the 'Encryption Keys' page has a blue '!', and only the 'Restore' and 'Delete' buttons are enabled. The 'Initialization' page has a red 'X'. The local RS is not listed (the grid is empty), and clicking the 'Initialize' button does nothing.

How can I diagnose and fix this installation?
Check and see if you had changed your password on your Administrator account for your server after installing Reporting Services. This will cause the problem if you have.|||I posted the solution in another thread. See:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1258874&SiteID=1

"...report server cannot access internal information..."

I've been unsuccessful getting Reporting Services 2005 to work after reinstalling SQL 2005. The RS service cannot connect to its database, as reported in the Event Log. If I visit http://localhost/Reports, I get the error "Key not valid for use in specified state. (Exception from HRESULT: 0x8009000B)

(rsRPCError)"

I've used the RS Config Mgr to create a fresh database for it named SSRS (and SSRSTembDB), and it is set to use Service Credentials in the db connection. The RS service is running using the same admin account as MSSQL, .\SQLExec. I have confirmed that .\SQLExec is in the RSExecRole role in the SSRS database.

When I created the SSRS database, the Config Mgr had a green check for every step except the last. For "Setting Connection Info for the Reporting Server" there was a yellow '!', with the explanation, "Although saving the database connection succeeded, the report server cannot access internal information about this deployment to determine if the current configuration is valid for this edition. ..."

I examined rsreportserver.config to look for any issues. The <dsn> element has an encrypted string, the <ConnectionType> element says "Default", and the logon elements are empty. I could not find the db names, SSRS and SSRSTempDB, anywhere in the file. Where are these kept? I don't know what else to look for.

Also, in RS Config Mgr, the 'Encryption Keys' page has a blue '!', and only the 'Restore' and 'Delete' buttons are enabled. The 'Initialization' page has a red 'X'. The local RS is not listed (the grid is empty), and clicking the 'Initialize' button does nothing.

How can I diagnose and fix this installation?Check and see if you had changed your password on your Administrator account for your server after installing Reporting Services. This will cause the problem if you have.|||I posted the solution in another thread. See:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1258874&SiteID=1

"...report server cannot access internal information..."

I've been unsuccessful getting Reporting Services 2005 to work after reinstalling SQL 2005. The RS service cannot connect to its database, as reported in the Event Log. If I visit http://localhost/Reports, I get the error "Key not valid for use in specified state. (Exception from HRESULT: 0x8009000B) (rsRPCError)"

I've used the RS Config Mgr to create a fresh database for it named SSRS (and SSRSTembDB), and it is set to use Service Credentials in the db connection. The RS service is running using the same admin account as MSSQL, .\SQLExec. I have confirmed that .\SQLExec is in the RSExecRole role in the SSRS database.

When I created the SSRS database, the Config Mgr had a green check for every step except the last. For "Setting Connection Info for the Reporting Server" there was a yellow '!', with the explanation, "Although saving the database connection succeeded, the report server cannot access internal information about this deployment to determine if the current configuration is valid for this edition. ..."

I examined rsreportserver.config to look for any issues. The <dsn> element has an encrypted string, the <ConnectionType> element says "Default", and the logon elements are empty. I could not find the db names, SSRS and SSRSTempDB, anywhere in the file. Where are these kept? I don't know what else to look for.

Also, in RS Config Mgr, the 'Encryption Keys' page has a blue '!', and only the 'Restore' and 'Delete' buttons are enabled. The 'Initialization' page has a red 'X'. The local RS is not listed (the grid is empty), and clicking the 'Initialize' button does nothing.

How can I diagnose and fix this installation?
Check and see if you had changed your password on your Administrator account for your server after installing Reporting Services. This will cause the problem if you have.|||I posted the solution in another thread. See:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1258874&SiteID=1

<ReportServerExternalUrl> with SSRS 2005

When we were on SSRS 2000, I had to add a line in my RSWebApplication.config
file in order for people outside our firewall to access our internal report
server. It looked like
<ReportServerExternalUrl>http://xxx.mydomain.com</ReportServerExternalUrl>
We just upgraded to SSRS 2005 and I wonder if I have to add this line back
into the config file to get/keep this capability.
Thanks.I tried accessing my report server after I got home and had no problems so
the answer must be that I don't need to insert this extra line manually into
the config file. That's nice since it seemed an unnecessary step in SSRS
2000.
Jon