Showing posts with label integration. Show all posts
Showing posts with label integration. Show all posts

Friday, March 23, 2012

Remoting timeout when calling SSIS package execute from a windows service

When running an integration services package from a windows service I get the "Object ... has been disconnected or does not exist at the server." exception after aproximately six minutes of execution.

This is *not* my windows service failing. I can loop indefinately while tracing to a log file within the service and it will run forever. While calling the mypackage.execute(...) method however, after six minutes (give or take) the exception is thrown...

my code looks something like this:
<code>
dim foo as Microsoft.SqlServer.Dts.Runtime.Application
mypackage = foo..LoadPackage(strimportPkgFilename, pkgevents)
results = myPackage.Execute(Nothing, Nothing, pkgevents, Nothing, Nothing)
</code>

<error>
A first chance exception of type 'System.Runtime.Remoting.RemotingException' occurred in mscorlib.dll
Exception in: frmMyForm.DoImports
Message: Object '/b76f98a0_5bd9_49d8_a524_eeb49d55b303/bqbhkjnaofq_ifr_cwz+srid_1.rem' has been disconnected or does not exist at the server.
</error>

oddly, this same code works perfectly if I run it within a windows form application no matter how long it takes.

It also runs fine if the package can complete in under six minutes.

Any suggestions?

Mark

To give a little update, I'm still having this problem despite exhausting works around I've come up with.

* I've threaded the call to package.Execute, checking its status in a while loop every 60 seconds until it finishes. Still encounter the exception. This behaves as though it should work. The status and execution appear to work asynchronously.

* I've threaded the call to my service, calling my own status function which tests the status of shared MyPackage, every 60 seconds. Still encounter the remoting exception after ~6 minutes.

Every piece is busy making requests through the whole chain of accessible interactions frequently enough to maintain all known remoting timeout constraints and the problem persists.

It confuses me why the same code works in a windows form, but does not work in a windows service. The exception is defiantly being thrown from within package.Execute. I can loop indefinitely within the service without calling package Execute. I can also catch and disregard the exception and still provide status to the client within the service.

Looking for suggestions...

|||

SSIS does not use remoting. The exception is caused by remoting however, so you need to find out who introduced remoting? My ideas

1) you use remoting as link between client and server - then the exception is between the client and the service, which does not fit with the statement that it is thrown from within package.Execute and you can catch this exception (but did you try?)

2) you create multiple application domains in the service - if you do this, make sure you only use SSIS from default application domain. If you run the package from non-default application domain, some SSIS objects can be created in that app domain, but some in default app domain (a lot of SSIS is native code, and it is not aware of app-domains), which may cause failures like this one.

Remoting timeout when calling SSIS package execute from a windows service

When running an integration services package from a windows service I get the "Object ... has been disconnected or does not exist at the server." exception after aproximately six minutes of execution.

This is *not* my windows service failing. I can loop indefinately while tracing to a log file within the service and it will run forever. While calling the mypackage.execute(...) method however, after six minutes (give or take) the exception is thrown...

my code looks something like this:
<code>
dim foo as Microsoft.SqlServer.Dts.Runtime.Application
mypackage = foo..LoadPackage(strimportPkgFilename, pkgevents)
results = myPackage.Execute(Nothing, Nothing, pkgevents, Nothing, Nothing)
</code>

<error>
A first chance exception of type 'System.Runtime.Remoting.RemotingException' occurred in mscorlib.dll
Exception in: frmMyForm.DoImports
Message: Object '/b76f98a0_5bd9_49d8_a524_eeb49d55b303/bqbhkjnaofq_ifr_cwz+srid_1.rem' has been disconnected or does not exist at the server.
</error>

oddly, this same code works perfectly if I run it within a windows form application no matter how long it takes.

It also runs fine if the package can complete in under six minutes.

Any suggestions?

Mark

To give a little update, I'm still having this problem despite exhausting works around I've come up with.

* I've threaded the call to package.Execute, checking its status in a while loop every 60 seconds until it finishes. Still encounter the exception. This behaves as though it should work. The status and execution appear to work asynchronously.

* I've threaded the call to my service, calling my own status function which tests the status of shared MyPackage, every 60 seconds. Still encounter the remoting exception after ~6 minutes.

Every piece is busy making requests through the whole chain of accessible interactions frequently enough to maintain all known remoting timeout constraints and the problem persists.

It confuses me why the same code works in a windows form, but does not work in a windows service. The exception is defiantly being thrown from within package.Execute. I can loop indefinitely within the service without calling package Execute. I can also catch and disregard the exception and still provide status to the client within the service.

Looking for suggestions...

|||

SSIS does not use remoting. The exception is caused by remoting however, so you need to find out who introduced remoting? My ideas

1) you use remoting as link between client and server - then the exception is between the client and the service, which does not fit with the statement that it is thrown from within package.Execute and you can catch this exception (but did you try?)

2) you create multiple application domains in the service - if you do this, make sure you only use SSIS from default application domain. If you run the package from non-default application domain, some SSIS objects can be created in that app domain, but some in default app domain (a lot of SSIS is native code, and it is not aware of app-domains), which may cause failures like this one.

Wednesday, March 21, 2012

Remote SSIS vs Domain\User: Access is Denied (0x80070005)

What OS permissions do I need to give a domain user to effectively connect to a remote instance of Integration Services?

I keep getting the following message:

Cannot connect to SQLDEV01
Failed to retreive data for this request.
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (Microsoft.SqlServer.ManagedDTS)

I have already performed the Windows 2003 steps outlined in the "Eliminating the Access is Denied" error located at http://msdn2.microsoft.com/en-us/library/aa337083.aspx

I have no problem if the user is a local Administrator (go figure).

The MSDN page lacks another steps needed on W2K3 (not sure about XP) - add the account to Distributed COM Users group. (The page is being updated).|||

Yes, I have done this, and gave the Domain\User the DCOM permissions upon the MsDtsSvr object. The Distributed COM Users step is actually included on ths webpage.

Thanks for responding. Perhaps there is another step missing?

|||

JFoushee wrote:

The Distributed COM Users step is actually included on ths webpage.

Not really (if we get the same copy of http://msdn2.microsoft.com/en-us/library/aa337083.aspx).

The page talks about configuring security for MsDtsServer application, but on Windows 2003 Server and 64-bit XP machine there is another global per-machine setting: in DCOMCNFG right click My Computer, select Properties, find COM Security page and inspect both Edit Limits settings: they should allow the user to access the machine. The simplest way to do it is to add user to Distributed COM Users user group.

|||

I believe I got it to work...

One the webpage http://msdn2.microsoft.com/en-us/library/aa337083.aspx, under "To configure rights for remote users on Windows Server 2003"...

replace step 9 with "Click OK to close the dialog box."

Add a step 9.1 with the following text: "On the same Security tab, under Access Permissions, select Customize, then click Edit to open the Access Permission dialog box."

Add a step 9.2 with the following text: "In the Access Permission dialog box, add or delete users, and assign the appropriate permissions to the appropriate users and groups. The available permissions are Local Access, and Remote Access. The easiest is to add the local DCOM Distributed Users group. "

Add a step 9.3 with the following text: "Click OK to close the dialog box. Close the MMC snap-in."

Step 10 stays as-is: "Restart the Integration Services service."

|||

Thanks a lot.

Finally I can connect to SSIS.

Remote SSIS vs Domain\User: Access is Denied (0x80070005)

What OS permissions do I need to give a domain user to effectively connect to a remote instance of Integration Services?

I keep getting the following message:

Cannot connect to SQLDEV01
Failed to retreive data for this request.
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (Microsoft.SqlServer.ManagedDTS)

I have already performed the Windows 2003 steps outlined in the "Eliminating the Access is Denied" error located at http://msdn2.microsoft.com/en-us/library/aa337083.aspx

I have no problem if the user is a local Administrator (go figure).

The MSDN page lacks another steps needed on W2K3 (not sure about XP) - add the account to Distributed COM Users group. (The page is being updated).|||

Yes, I have done this, and gave the Domain\User the DCOM permissions upon the MsDtsSvr object. The Distributed COM Users step is actually included on ths webpage.

Thanks for responding. Perhaps there is another step missing?

|||

JFoushee wrote:

The Distributed COM Users step is actually included on ths webpage.

Not really (if we get the same copy of http://msdn2.microsoft.com/en-us/library/aa337083.aspx).

The page talks about configuring security for MsDtsServer application, but on Windows 2003 Server and 64-bit XP machine there is another global per-machine setting: in DCOMCNFG right click My Computer, select Properties, find COM Security page and inspect both Edit Limits settings: they should allow the user to access the machine. The simplest way to do it is to add user to Distributed COM Users user group.

|||

I believe I got it to work...

One the webpage http://msdn2.microsoft.com/en-us/library/aa337083.aspx, under "To configure rights for remote users on Windows Server 2003"...

replace step 9 with "Click OK to close the dialog box."

Add a step 9.1 with the following text: "On the same Security tab, under Access Permissions, select Customize, then click Edit to open the Access Permission dialog box."

Add a step 9.2 with the following text: "In the Access Permission dialog box, add or delete users, and assign the appropriate permissions to the appropriate users and groups. The available permissions are Local Access, and Remote Access. The easiest is to add the local DCOM Distributed Users group. "

Add a step 9.3 with the following text: "Click OK to close the dialog box. Close the MMC snap-in."

Step 10 stays as-is: "Restart the Integration Services service."

|||

Thanks alot.

Finally I can connect to SSIS.

Remote SSIS vs Domain\User: Access is Denied (0x80070005)

What OS permissions do I need to give a domain user to effectively connect to a remote instance of Integration Services?

I keep getting the following message:

Cannot connect to SQLDEV01
Failed to retreive data for this request.
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (Microsoft.SqlServer.ManagedDTS)

I have already performed the Windows 2003 steps outlined in the "Eliminating the Access is Denied" error located at http://msdn2.microsoft.com/en-us/library/aa337083.aspx

I have no problem if the user is a local Administrator (go figure).

The MSDN page lacks another steps needed on W2K3 (not sure about XP) - add the account to Distributed COM Users group. (The page is being updated).|||

Yes, I have done this, and gave the Domain\User the DCOM permissions upon the MsDtsSvr object. The Distributed COM Users step is actually included on ths webpage.

Thanks for responding. Perhaps there is another step missing?

|||

JFoushee wrote:

The Distributed COM Users step is actually included on ths webpage.

Not really (if we get the same copy of http://msdn2.microsoft.com/en-us/library/aa337083.aspx).

The page talks about configuring security for MsDtsServer application, but on Windows 2003 Server and 64-bit XP machine there is another global per-machine setting: in DCOMCNFG right click My Computer, select Properties, find COM Security page and inspect both Edit Limits settings: they should allow the user to access the machine. The simplest way to do it is to add user to Distributed COM Users user group.

|||

I believe I got it to work...

One the webpage http://msdn2.microsoft.com/en-us/library/aa337083.aspx, under "To configure rights for remote users on Windows Server 2003"...

replace step 9 with "Click OK to close the dialog box."

Add a step 9.1 with the following text: "On the same Security tab, under Access Permissions, select Customize, then click Edit to open the Access Permission dialog box."

Add a step 9.2 with the following text: "In the Access Permission dialog box, add or delete users, and assign the appropriate permissions to the appropriate users and groups. The available permissions are Local Access, and Remote Access. The easiest is to add the local DCOM Distributed Users group. "

Add a step 9.3 with the following text: "Click OK to close the dialog box. Close the MMC snap-in."

Step 10 stays as-is: "Restart the Integration Services service."

|||

Thanks a lot.

Finally I can connect to SSIS.

sql

Wednesday, March 7, 2012

Remote Error Problem

Hi all,
I created a report that uses resultset generated from integration service. I managed to run the report on BIDS and also by command prompt on both server pc and remote pc. (I created the report from remote pc and deploy the report from remote pc also). When I try to run the report from report server, the following error came up (I already enable remote errors):
  • An error has occurred during report processing.
  • Cannot create a connection to data source 'SSIS'.
  • 5 Anyone have any idea how to solve it? or anywhere that I can find the meaning of the 5 below the error message? Thanks in advance.
    Daren
    Hi all,
    Sorry to post another message here. Just to touch up on my question above. I create a custom data source to SSIS in Report Server and use Windows Integrated Security. Then the error occurs.
    Daren
    |||Nobody knows about this error?
    Daren
    |||Have you looked at the logfiles?
    \Program Files\Microsoft SQL Server\MSSQL.[x]\Reporting Services\LogFiles
    The logfiles get really big and complex, so the best way is to stop IIS and Reporting Services, move or delete the old logfiles, restart the IIS and Reporting Services, run your report and look into the logfiles. Usually you can find a bit more verbose Errormessages there.

    |||Hi BenniG,
    Sorry I took so long to reply, I managed to browse through the log and found the following content:
    w3wp!processing!7!5/18/2006-09:27:24:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'., ;
    Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
    at MgdParser.CreatePackage(Boolean bNeutral, Boolean bRemote)
    at Microsoft.SqlServer.Dts.DtsClient.DtsConnection.Open()
    at Microsoft.ReportingServices.DataExtensions.ConnectionWrapper.Open()
    at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource dataSourceObj, ReportProcessingContext pc)
    End of inner exception stack trace
    w3wp!processing!7!5/18/2006-09:27:25:: e ERROR: Data source 'SSIS': An error has occurred. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
    w3wp!processing!7!5/18/2006-09:27:25:: e ERROR: An exception has occurred in data source 'SSIS'. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
    w3wp!processing!7!5/18/2006-09:27:25:: i INFO: Merge abort handler called for ID=-1. Aborting data sources ...
    w3wp!processing!7!5/18/2006-09:27:25:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing., ;
    Info: Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. > Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
    End of inner exception stack trace
    w3wp!webserver!7!05/18/2006-09:27:25:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error has occurred during report processing. > Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. > Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
    But I still do not get what does System.ApplicationException: 5 means. Do you know anywhere that I can find the description of error #5 stated in the log or report server?
    Daren
    |||Can you post these messages to the SSIS forum? You should be able to get a better response there.|||ok. Thanks Tudor.
    Daren

  • Remote Error Problem

    Hi all,
    I created a report that uses resultset generated from integration service. I managed to run the report on BIDS and also by command prompt on both server pc and remote pc. (I created the report from remote pc and deploy the report from remote pc also). When I try to run the report from report server, the following error came up (I already enable remote errors):
  • An error has occurred during report processing.
  • Cannot create a connection to data source 'SSIS'.
  • 5 Anyone have any idea how to solve it? or anywhere that I can find the meaning of the 5 below the error message? Thanks in advance.
    Darenanyone know the solution to it?
    Daren
  • Remote Error Problem

    Hi all,
    I created a report that uses resultset generated from integration service. I managed to run the report on BIDS and also by command prompt on both server pc and remote pc. (I created the report from remote pc and deploy the report from remote pc also). When I try to run the report from report server, the following error came up (I already enable remote errors):
  • An error has occurred during report processing.
  • Cannot create a connection to data source 'SSIS'.
  • 5 Anyone have any idea how to solve it? or anywhere that I can find the meaning of the 5 below the error message? Thanks in advance.
    Daren
    Hi all,
    Sorry to post another message here. Just to touch up on my question above. I create a custom data source to SSIS in Report Server and use Windows Integrated Security. Then the error occurs.
    Daren
    |||Nobody knows about this error?
    Daren
    |||Have you looked at the logfiles?
    \Program Files\Microsoft SQL Server\MSSQL.[x]\Reporting Services\LogFiles
    The logfiles get really big and complex, so the best way is to stop IIS and Reporting Services, move or delete the old logfiles, restart the IIS and Reporting Services, run your report and look into the logfiles. Usually you can find a bit more verbose Errormessages there.

    |||Hi BenniG,
    Sorry I took so long to reply, I managed to browse through the log and found the following content:
    w3wp!processing!7!5/18/2006-09:27:24:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'., ;
    Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
    at MgdParser.CreatePackage(Boolean bNeutral, Boolean bRemote)
    at Microsoft.SqlServer.Dts.DtsClient.DtsConnection.Open()
    at Microsoft.ReportingServices.DataExtensions.ConnectionWrapper.Open()
    at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource dataSourceObj, ReportProcessingContext pc)
    End of inner exception stack trace
    w3wp!processing!7!5/18/2006-09:27:25:: e ERROR: Data source 'SSIS': An error has occurred. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
    w3wp!processing!7!5/18/2006-09:27:25:: e ERROR: An exception has occurred in data source 'SSIS'. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
    w3wp!processing!7!5/18/2006-09:27:25:: i INFO: Merge abort handler called for ID=-1. Aborting data sources ...
    w3wp!processing!7!5/18/2006-09:27:25:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing., ;
    Info: Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. > Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
    End of inner exception stack trace
    w3wp!webserver!7!05/18/2006-09:27:25:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error has occurred during report processing. > Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. > Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
    But I still do not get what does System.ApplicationException: 5 means. Do you know anywhere that I can find the description of error #5 stated in the log or report server?
    Daren
    |||Can you post these messages to the SSIS forum? You should be able to get a better response there.|||ok. Thanks Tudor.
    Daren

  • Monday, February 20, 2012

    Remote Connection Issue

    Hello, I have a leb setup to install and test Microsoft Identity Integration Feature Pack. I have two servers running in two different forests and SQL running on one of the servers. I must connect to the SQL server from the othere machine but when I try connecting I get an error message that says "The service account cannot access SQL server. Ensure that the server is accessible, the service account is not a local account being used with a remote SQL server, and that the account doesn't already have a SQL login."

    Any ideas what i could be doing wrong?

    Hi,

    Which Account is used to start the server is it domain account with proper privilege ?

    refer the links http://support.microsoft.com/kb/555585 and http://msdn2.microsoft.com/en-us/library/ms143691.aspx for workaround.

    Hemantgiri S. Goswami