Showing posts with label runs. Show all posts
Showing posts with label runs. Show all posts

Thursday, March 22, 2012

can't access SQL Server 2005 Cubes, when Integrity firewall runs

Hi,

i'm not able to access the content of the SQL Server Cubes, when i've running the Checkpoint Integrity firewall on the system. I've to shut down the firewall to see the content of the Cubes. Does any one have idea, what could cause this?

best regards

Alfredo

allow traffic to pass thru port 1433 for sql server clients|||

hi,

thx for your answer, traffic for is port 1433 is open. For testing i allowed also any traffic, but it didn't fix the issue, it only works when Integrty doesn't. I had a similar issue with the Ab Initio application, but this Software Company did fix the issue. I don't know how they exactly fixed it, but it was not a Firewall Policy related issue.

|||

kindly post the error text.

|||

Hi,

there are no error messages, the SQL server 2005 Managemnet Studio application just 'hangs', when the Integrity firewall runs. We've the issue, only when we try to accecss the content of the Cubes container, independent if we use the SQL Server toools or f/e Microsoft Excel to access it.

can't access SQL Server 2005 Cubes, when Integrity firewall runs

Hi,

i'm not able to access the content of the SQL Server Cubes, when i've running the Checkpoint Integrity firewall on the system. I've to shut down the firewall to see the content of the Cubes. Does any one have idea, what could cause this?

best regards

Alfredo

allow traffic to pass thru port 1433 for sql server clients|||

hi,

thx for your answer, traffic for is port 1433 is open. For testing i allowed also any traffic, but it didn't fix the issue, it only works when Integrty doesn't. I had a similar issue with the Ab Initio application, but this Software Company did fix the issue. I don't know how they exactly fixed it, but it was not a Firewall Policy related issue.

|||

kindly post the error text.

|||

Hi,

there are no error messages, the SQL server 2005 Managemnet Studio application just 'hangs', when the Integrity firewall runs. We've the issue, only when we try to accecss the content of the Cubes container, independent if we use the SQL Server toools or f/e Microsoft Excel to access it.

sql

Monday, March 19, 2012

cannot write logfile Error 1059 : Circular service dependency

I have a problem that looks like it has not been discussed before in
these groups.
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.
On Feb 13, 6:33 pm, donn...@.fastmail.fm wrote:
> I have a problem that looks like it has not been discussed before in
> these groups.
> I have a simple SQLAgent job that runs sp_who (could be anything, but
> let's just say sp_who for this example). I have set the jobstep to
> write to an output file "T:\out.txt". If the job is owned by an
> admin, it runs fine and writes the output file. If it is owned by a
> non-admin user, it gets the following error msg:
> Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
> service dependency was specified. The step failed.
> I know about setting up the SQLAgent CMDExec proxy account, and have
> done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
> the same domain account, which is in the administrator group of the
> local server. So, I know that security is not the issue.
> When a simple job runs and writes to an output file, what service or
> service group could it be trying to start or modify? I looked through
> the list of Services, and could not find any circular dependencies.
> Is there a utility to detect this? Why would running under one
> context (as an admin) be ok while the other context (non-admin on SQL,
> but using the same admin domain service account) fails?
> Thanks in advance for any info you might have.
Googling it returns:
Circular service dependency was specified.
Explanation:
An application tried to change the service dependency list for a
service. A check of the other service dependency lists in the service
database reveals at least one circular relationship between the
proposed new list and existing lists. For instance, service A must
start before service B in one list, but service B must start before
service A in another list. Your computer has not been configured
properly.
Do both accounts have the same permissions to the directory the file
is output to?
|||There is really only one account, because both SQLAgent and SQLAgent
cmdexec proxy (which is what is used when a non-admin runs a job)
both use this account, which is an admin on the local server. So,
yes, they both have the same permissions. SQLAgent seems to be trying
to start or modify some other service. I looked through services, and
could not find any circular dependencies.
On Feb 13, 9:48 pm, "Steve" <morrisz...@.hotmail.com> wrote:
> Googling it returns:
> Circular service dependency was specified.
> Explanation:
> An application tried to change the service dependency list for a
> service. A check of the other service dependency lists in the service
> database reveals at least one circular relationship between the
> proposed new list and existing lists. For instance, service A must
> start before service B in one list, but service B must start before
> service A in another list. Your computer has not been configured
> properly.
> Do both accounts have the same permissions to the directory the file
> is output to?>
|||Has anyone run into this problem?
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy
use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked
through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on
SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.

cannot write logfile Error 1059 : Circular service dependency

I have a problem that looks like it has not been discussed before in
these groups.
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.On Feb 13, 6:33 pm, donn...@.fastmail.fm wrote:
> I have a problem that looks like it has not been discussed before in
> these groups.
> I have a simple SQLAgent job that runs sp_who (could be anything, but
> let's just say sp_who for this example). I have set the jobstep to
> write to an output file "T:\out.txt". If the job is owned by an
> admin, it runs fine and writes the output file. If it is owned by a
> non-admin user, it gets the following error msg:
> Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
> service dependency was specified. The step failed.
> I know about setting up the SQLAgent CMDExec proxy account, and have
> done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
> the same domain account, which is in the administrator group of the
> local server. So, I know that security is not the issue.
> When a simple job runs and writes to an output file, what service or
> service group could it be trying to start or modify? I looked through
> the list of Services, and could not find any circular dependencies.
> Is there a utility to detect this? Why would running under one
> context (as an admin) be ok while the other context (non-admin on SQL,
> but using the same admin domain service account) fails?
> Thanks in advance for any info you might have.
Googling it returns:
Circular service dependency was specified.
Explanation:
An application tried to change the service dependency list for a
service. A check of the other service dependency lists in the service
database reveals at least one circular relationship between the
proposed new list and existing lists. For instance, service A must
start before service B in one list, but service B must start before
service A in another list. Your computer has not been configured
properly.
Do both accounts have the same permissions to the directory the file
is output to?|||There is really only one account, because both SQLAgent and SQLAgent
cmdexec proxy (which is what is used when a non-admin runs a job)
both use this account, which is an admin on the local server. So,
yes, they both have the same permissions. SQLAgent seems to be trying
to start or modify some other service. I looked through services, and
could not find any circular dependencies.
On Feb 13, 9:48 pm, "Steve" <morrisz...@.hotmail.com> wrote:
> Googling it returns:
> Circular service dependency was specified.
> Explanation:
> An application tried to change the service dependency list for a
> service. A check of the other service dependency lists in the service
> database reveals at least one circular relationship between the
> proposed new list and existing lists. For instance, service A must
> start before service B in one list, but service B must start before
> service A in another list. Your computer has not been configured
> properly.
> Do both accounts have the same permissions to the directory the file
> is output to?>|||Has anyone run into this problem'
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy
use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked
through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on
SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.

cannot write logfile Error 1059 : Circular service dependency

I have a problem that looks like it has not been discussed before in
these groups.

I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:

Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.

I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.

When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on SQL,
but using the same admin domain service account) fails?

Thanks in advance for any info you might have.On Feb 13, 6:33 pm, donn...@.fastmail.fm wrote:

Quote:

Originally Posted by

I have a problem that looks like it has not been discussed before in
these groups.
>
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
>
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
>
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
>
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on SQL,
but using the same admin domain service account) fails?
>
Thanks in advance for any info you might have.


Googling it returns:
Circular service dependency was specified.
Explanation:
An application tried to change the service dependency list for a
service. A check of the other service dependency lists in the service
database reveals at least one circular relationship between the
proposed new list and existing lists. For instance, service A must
start before service B in one list, but service B must start before
service A in another list. Your computer has not been configured
properly.

Do both accounts have the same permissions to the directory the file
is output to?|||There is really only one account, because both SQLAgent and SQLAgent
cmdexec proxy (which is what is used when a non-admin runs a job)
both use this account, which is an admin on the local server. So,
yes, they both have the same permissions. SQLAgent seems to be trying
to start or modify some other service. I looked through services, and
could not find any circular dependencies.

On Feb 13, 9:48 pm, "Steve" <morrisz...@.hotmail.comwrote:

Quote:

Originally Posted by

Googling it returns:
Circular service dependency was specified.
Explanation:
An application tried to change the service dependency list for a
service. A check of the other service dependency lists in the service
database reveals at least one circular relationship between the
proposed new list and existing lists. For instance, service A must
start before service B in one list, but service B must start before
service A in another list. Your computer has not been configured
properly.
>
Do both accounts have the same permissions to the directory the file
is output to?>

|||Has anyone run into this problem??

I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:

Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.

I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy
use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.

When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked
through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on
SQL,
but using the same admin domain service account) fails?

Thanks in advance for any info you might have.

cannot write logfile Error 1059 : Circular service dependency

I have a problem that looks like it has not been discussed before in
these groups.
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.On Feb 13, 6:33 pm, donn...@.fastmail.fm wrote:
> I have a problem that looks like it has not been discussed before in
> these groups.
> I have a simple SQLAgent job that runs sp_who (could be anything, but
> let's just say sp_who for this example). I have set the jobstep to
> write to an output file "T:\out.txt". If the job is owned by an
> admin, it runs fine and writes the output file. If it is owned by a
> non-admin user, it gets the following error msg:
> Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
> service dependency was specified. The step failed.
> I know about setting up the SQLAgent CMDExec proxy account, and have
> done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
> the same domain account, which is in the administrator group of the
> local server. So, I know that security is not the issue.
> When a simple job runs and writes to an output file, what service or
> service group could it be trying to start or modify? I looked through
> the list of Services, and could not find any circular dependencies.
> Is there a utility to detect this? Why would running under one
> context (as an admin) be ok while the other context (non-admin on SQL,
> but using the same admin domain service account) fails?
> Thanks in advance for any info you might have.
Googling it returns:
Circular service dependency was specified.
Explanation:
An application tried to change the service dependency list for a
service. A check of the other service dependency lists in the service
database reveals at least one circular relationship between the
proposed new list and existing lists. For instance, service A must
start before service B in one list, but service B must start before
service A in another list. Your computer has not been configured
properly.
Do both accounts have the same permissions to the directory the file
is output to?|||There is really only one account, because both SQLAgent and SQLAgent
cmdexec proxy (which is what is used when a non-admin runs a job)
both use this account, which is an admin on the local server. So,
yes, they both have the same permissions. SQLAgent seems to be trying
to start or modify some other service. I looked through services, and
could not find any circular dependencies.
On Feb 13, 9:48 pm, "Steve" <morrisz...@.hotmail.com> wrote:
> Googling it returns:
> Circular service dependency was specified.
> Explanation:
> An application tried to change the service dependency list for a
> service. A check of the other service dependency lists in the service
> database reveals at least one circular relationship between the
> proposed new list and existing lists. For instance, service A must
> start before service B in one list, but service B must start before
> service A in another list. Your computer has not been configured
> properly.
> Do both accounts have the same permissions to the directory the file
> is output to?>|||Has anyone run into this problem'
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy
use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked
through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on
SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.

Tuesday, February 14, 2012

Cannot see data in database table

Hi all,

I am having a problem viewing data in a database table.

The data is entered into the database with a web service and it runs without problems. However, when I open the table with the management tool, I cannot see the data I just sent to it.

Also, when I try adding data directly to the table, the id column shows that there is data in the table. That is lets say the id for the 1st item is "1", after sending 4 records to the database with the webservice, when I try to enter data in the table directly, the next available key is 5. This indicates that there is some data in the table that I cannot see.

Does anyone know how I can reslove this?

Thanks!


Hi,
perhaps the transactions has beend rolled back again, or the data was deleted by another rpocedure / database call again. To find out what wiped out the data from the database, run the profiler, tracing all action concerned to your database.

HTH; Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

Hi Hugo,

Is this in a productiong system? When working in debug it is common for data to disappear because of a fluke in how VS works. Check out the FAQ at the top of this forum. Just the fact that the id is 5 doesn't mean that other records exist in the table. As Jens points out, if the record was created, but then rolled back, the id value has been burned already and won't be reused.

How are you trying to view the data?

Mike

Cannot see data in database table

Hi all,

I am having a problem viewing data in a database table.

The data is entered into the database with a web service and it runs without problems. However, when I open the table with the management tool, I cannot see the data I just sent to it.

Also, when I try adding data directly to the table, the id column shows that there is data in the table. That is lets say the id for the 1st item is "1", after sending 4 records to the database with the webservice, when I try to enter data in the table directly, the next available key is 5. This indicates that there is some data in the table that I cannot see.

Does anyone know how I can reslove this?

Thanks!


Hi,
perhaps the transactions has beend rolled back again, or the data was deleted by another rpocedure / database call again. To find out what wiped out the data from the database, run the profiler, tracing all action concerned to your database.

HTH; Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

Hi Hugo,

Is this in a productiong system? When working in debug it is common for data to disappear because of a fluke in how VS works. Check out the FAQ at the top of this forum. Just the fact that the id is 5 doesn't mean that other records exist in the table. As Jens points out, if the record was created, but then rolled back, the id value has been burned already and won't be reused.

How are you trying to view the data?

Mike

Sunday, February 12, 2012

Cannot run report on the report server with ssis as a datasource

Helo All,


I have report which uses an ssis package as a datasource. when I develop the report on the visual studio seems like it runs fine. But when I deployed the same report on to the server (report server 64 bit machine) it is throwing me an error:

An error has occurred during report processing.

  • Cannot create a connection to data source 'DataSource1'.

  • is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)
  • I have both sql sever and reporting server on the same machine and using windows credentials for both the servers(sql and reporting).Then I believe there is no credential issue.

    My connection string looks something like this:

    ="/FILE C:\NTSDW\KPI\KPI_SSIS\NTSKPICCA_DATA_RECON_DELIVERY.dtsx /SET \Package.Variables[User::V_SSRS_PARAM].Properties[Value];" & """" & Parameters!V_SETT_DATE.Value & """"

    Could any please help me out of this?

    Note: SSIS is parameterized here!

    Regards,

    Raju

    Does it work if you remove the parameter?

    Also, enable logging in the package so you can tell if SSRS is actually executing it.

    |||

    Hi,

    I am using ssis logging and found there is a connectivity issue. I am able to connect to the source systems but not able to connect to the target(dwh) system. But I am able to run the package with the same configuration( configurations stored in xml file on the drive ) . I am using windows authentication to connect to the target systems.

    The report manager also runs on the windows authentication mode. I am not sure where exctly the issue is. I think there is some authentication(ASP NET user) issue with report manager connecting to the target system.

    |||

    Yes, it is likely that account that SSRS is running under can't access the database. Can you change to use a SQL Server login to connect to the data source?

    |||

    Yes, it worked with SQL login, but with direct XML configuration type. It did not work with Indirect configuration using the environment variable. What could be the reason? Any solution for this? This will cause our build/deployment to QA and Prod difficult.

    Thanks for your help...

    |||Did you restart all the services (SSIS, SSRS, etc)? You have to restart the services for them to pick up new env. variables.|||

    I did start the SSRS and SSIS services, the issue is the report server is not able to call the package itself.I found that the package is not invoked as i have enabled the logging. No log file is wirtten.It gives me the same old error "Not a valid win32 application" .

    Note: The same package is running fine on all the 32 bit machines , but not on the 64 bit machines.

    |||What data source are you using? Does it have a 64-bit driver?|||

    Hello All,

    The issue got resolved. I was having windows sp2 and sql sevrer sp1 on my server. After installing sp2 sql server the issue got resolved and seems to be running fine.

    Thanks to you all.

    Raju

  • Cannot run report on the report server with ssis as a datasource

    Helo All,


    I have report which uses an ssis package as a datasource. when I develop the report on the visual studio seems like it runs fine. But when I deployed the same report on to the server (report server 64 bit machine) it is throwing me an error:

    An error has occurred during report processing.

  • Cannot create a connection to data source 'DataSource1'.

  • is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)
  • I have both sql sever and reporting server on the same machine and using windows credentials for both the servers(sql and reporting).Then I believe there is no credential issue.

    My connection string looks something like this:

    ="/FILE C:\NTSDW\KPI\KPI_SSIS\NTSKPICCA_DATA_RECON_DELIVERY.dtsx /SET \Package.Variables[User::V_SSRS_PARAM].Properties[Value];" & """" & Parameters!V_SETT_DATE.Value & """"

    Could any please help me out of this?

    Note: SSIS is parameterized here!

    Regards,

    Raju

    Does it work if you remove the parameter?

    Also, enable logging in the package so you can tell if SSRS is actually executing it.

    |||

    Hi,

    I am using ssis logging and found there is a connectivity issue. I am able to connect to the source systems but not able to connect to the target(dwh) system. But I am able to run the package with the same configuration( configurations stored in xml file on the drive ) . I am using windows authentication to connect to the target systems.

    The report manager also runs on the windows authentication mode. I am not sure where exctly the issue is. I think there is some authentication(ASP NET user) issue with report manager connecting to the target system.

    |||

    Yes, it is likely that account that SSRS is running under can't access the database. Can you change to use a SQL Server login to connect to the data source?

    |||

    Yes, it worked with SQL login, but with direct XML configuration type. It did not work with Indirect configuration using the environment variable. What could be the reason? Any solution for this? This will cause our build/deployment to QA and Prod difficult.

    Thanks for your help...

    |||Did you restart all the services (SSIS, SSRS, etc)? You have to restart the services for them to pick up new env. variables.|||

    I did start the SSRS and SSIS services, the issue is the report server is not able to call the package itself.I found that the package is not invoked as i have enabled the logging. No log file is wirtten.It gives me the same old error "Not a valid win32 application" .

    Note: The same package is running fine on all the 32 bit machines , but not on the 64 bit machines.

    |||What data source are you using? Does it have a 64-bit driver?|||

    Hello All,

    The issue got resolved. I was having windows sp2 and sql sevrer sp1 on my server. After installing sp2 sql server the issue got resolved and seems to be running fine.

    Thanks to you all.

    Raju

  • Cannot run report on the report server with ssis as a datasource

    Helo All,


    I have report which uses an ssis package as a datasource. when I develop the report on the visual studio seems like it runs fine. But when I deployed the same report on to the server (report server 64 bit machine) it is throwing me an error:

    An error has occurred during report processing.

  • Cannot create a connection to data source 'DataSource1'.

  • is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)
  • I have both sql sever and reporting server on the same machine and using windows credentials for both the servers(sql and reporting).Then I believe there is no credential issue.

    My connection string looks something like this:

    ="/FILE C:\NTSDW\KPI\KPI_SSIS\NTSKPICCA_DATA_RECON_DELIVERY.dtsx /SET \Package.Variables[User::V_SSRS_PARAM].Properties[Value];" & """" & Parameters!V_SETT_DATE.Value & """"

    Could any please help me out of this?

    Note: SSIS is parameterized here!

    Regards,

    Raju

    Does it work if you remove the parameter?

    Also, enable logging in the package so you can tell if SSRS is actually executing it.

    |||

    Hi,

    I am using ssis logging and found there is a connectivity issue. I am able to connect to the source systems but not able to connect to the target(dwh) system. But I am able to run the package with the same configuration( configurations stored in xml file on the drive ) . I am using windows authentication to connect to the target systems.

    The report manager also runs on the windows authentication mode. I am not sure where exctly the issue is. I think there is some authentication(ASP NET user) issue with report manager connecting to the target system.

    |||

    Yes, it is likely that account that SSRS is running under can't access the database. Can you change to use a SQL Server login to connect to the data source?

    |||

    Yes, it worked with SQL login, but with direct XML configuration type. It did not work with Indirect configuration using the environment variable. What could be the reason? Any solution for this? This will cause our build/deployment to QA and Prod difficult.

    Thanks for your help...

    |||Did you restart all the services (SSIS, SSRS, etc)? You have to restart the services for them to pick up new env. variables.|||

    I did start the SSRS and SSIS services, the issue is the report server is not able to call the package itself.I found that the package is not invoked as i have enabled the logging. No log file is wirtten.It gives me the same old error "Not a valid win32 application" .

    Note: The same package is running fine on all the 32 bit machines , but not on the 64 bit machines.

    |||What data source are you using? Does it have a 64-bit driver?|||

    Hello All,

    The issue got resolved. I was having windows sp2 and sql sevrer sp1 on my server. After installing sp2 sql server the issue got resolved and seems to be running fine.

    Thanks to you all.

    Raju

  • Cannot run report on the report server with ssis as a datasource

    Helo All,


    I have report which uses an ssis package as a datasource. when I develop the report on the visual studio seems like it runs fine. But when I deployed the same report on to the server (report server 64 bit machine) it is throwing me an error:

    An error has occurred during report processing.

  • Cannot create a connection to data source 'DataSource1'.

  • is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)
  • I have both sql sever and reporting server on the same machine and using windows credentials for both the servers(sql and reporting).Then I believe there is no credential issue.

    My connection string looks something like this:

    ="/FILE C:\NTSDW\KPI\KPI_SSIS\NTSKPICCA_DATA_RECON_DELIVERY.dtsx /SET \Package.Variables[User::V_SSRS_PARAM].Properties[Value];" & """" & Parameters!V_SETT_DATE.Value & """"

    Could any please help me out of this?

    Note: SSIS is parameterized here!

    Regards,

    Raju

    Does it work if you remove the parameter?

    Also, enable logging in the package so you can tell if SSRS is actually executing it.

    |||

    Hi,

    I am using ssis logging and found there is a connectivity issue. I am able to connect to the source systems but not able to connect to the target(dwh) system. But I am able to run the package with the same configuration( configurations stored in xml file on the drive ) . I am using windows authentication to connect to the target systems.

    The report manager also runs on the windows authentication mode. I am not sure where exctly the issue is. I think there is some authentication(ASP NET user) issue with report manager connecting to the target system.

    |||

    Yes, it is likely that account that SSRS is running under can't access the database. Can you change to use a SQL Server login to connect to the data source?

    |||

    Yes, it worked with SQL login, but with direct XML configuration type. It did not work with Indirect configuration using the environment variable. What could be the reason? Any solution for this? This will cause our build/deployment to QA and Prod difficult.

    Thanks for your help...

    |||Did you restart all the services (SSIS, SSRS, etc)? You have to restart the services for them to pick up new env. variables.|||

    I did start the SSRS and SSIS services, the issue is the report server is not able to call the package itself.I found that the package is not invoked as i have enabled the logging. No log file is wirtten.It gives me the same old error "Not a valid win32 application" .

    Note: The same package is running fine on all the 32 bit machines , but not on the 64 bit machines.

    |||What data source are you using? Does it have a 64-bit driver?|||

    Hello All,

    The issue got resolved. I was having windows sp2 and sql sevrer sp1 on my server. After installing sp2 sql server the issue got resolved and seems to be running fine.

    Thanks to you all.

    Raju

  • Cannot run report on the report server with ssis as a datasource

    Helo All,


    I have report which uses an ssis package as a datasource. when I develop the report on the visual studio seems like it runs fine. But when I deployed the same report on to the server (report server 64 bit machine) it is throwing me an error:

    An error has occurred during report processing.

  • Cannot create a connection to data source 'DataSource1'.

  • is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)
  • I have both sql sever and reporting server on the same machine and using windows credentials for both the servers(sql and reporting).Then I believe there is no credential issue.

    My connection string looks something like this:

    ="/FILE C:\NTSDW\KPI\KPI_SSIS\NTSKPICCA_DATA_RECON_DELIVERY.dtsx /SET \Package.Variables[User::V_SSRS_PARAM].Properties[Value];" & """" & Parameters!V_SETT_DATE.Value & """"

    Could any please help me out of this?

    Note: SSIS is parameterized here!

    Regards,

    Raju

    Does it work if you remove the parameter?

    Also, enable logging in the package so you can tell if SSRS is actually executing it.

    |||

    Hi,

    I am using ssis logging and found there is a connectivity issue. I am able to connect to the source systems but not able to connect to the target(dwh) system. But I am able to run the package with the same configuration( configurations stored in xml file on the drive ) . I am using windows authentication to connect to the target systems.

    The report manager also runs on the windows authentication mode. I am not sure where exctly the issue is. I think there is some authentication(ASP NET user) issue with report manager connecting to the target system.

    |||

    Yes, it is likely that account that SSRS is running under can't access the database. Can you change to use a SQL Server login to connect to the data source?

    |||

    Yes, it worked with SQL login, but with direct XML configuration type. It did not work with Indirect configuration using the environment variable. What could be the reason? Any solution for this? This will cause our build/deployment to QA and Prod difficult.

    Thanks for your help...

    |||Did you restart all the services (SSIS, SSRS, etc)? You have to restart the services for them to pick up new env. variables.|||

    I did start the SSRS and SSIS services, the issue is the report server is not able to call the package itself.I found that the package is not invoked as i have enabled the logging. No log file is wirtten.It gives me the same old error "Not a valid win32 application" .

    Note: The same package is running fine on all the 32 bit machines , but not on the 64 bit machines.

    |||What data source are you using? Does it have a 64-bit driver?|||

    Hello All,

    The issue got resolved. I was having windows sp2 and sql sevrer sp1 on my server. After installing sp2 sql server the issue got resolved and seems to be running fine.

    Thanks to you all.

    Raju

  • Cannot run report on the report server with ssis as a datasource

    Helo All,


    I have report which uses an ssis package as a datasource. when I develop the report on the visual studio seems like it runs fine. But when I deployed the same report on to the server (report server 64 bit machine) it is throwing me an error:

    An error has occurred during report processing.

  • Cannot create a connection to data source 'DataSource1'.

  • is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)
  • I have both sql sever and reporting server on the same machine and using windows credentials for both the servers(sql and reporting).Then I believe there is no credential issue.

    My connection string looks something like this:

    ="/FILE C:\NTSDW\KPI\KPI_SSIS\NTSKPICCA_DATA_RECON_DELIVERY.dtsx /SET \Package.Variables[User::V_SSRS_PARAM].Properties[Value];" & """" & Parameters!V_SETT_DATE.Value & """"

    Could any please help me out of this?

    Note: SSIS is parameterized here!

    Regards,

    Raju

    Does it work if you remove the parameter?

    Also, enable logging in the package so you can tell if SSRS is actually executing it.

    |||

    Hi,

    I am using ssis logging and found there is a connectivity issue. I am able to connect to the source systems but not able to connect to the target(dwh) system. But I am able to run the package with the same configuration( configurations stored in xml file on the drive ) . I am using windows authentication to connect to the target systems.

    The report manager also runs on the windows authentication mode. I am not sure where exctly the issue is. I think there is some authentication(ASP NET user) issue with report manager connecting to the target system.

    |||

    Yes, it is likely that account that SSRS is running under can't access the database. Can you change to use a SQL Server login to connect to the data source?

    |||

    Yes, it worked with SQL login, but with direct XML configuration type. It did not work with Indirect configuration using the environment variable. What could be the reason? Any solution for this? This will cause our build/deployment to QA and Prod difficult.

    Thanks for your help...

    |||Did you restart all the services (SSIS, SSRS, etc)? You have to restart the services for them to pick up new env. variables.|||

    I did start the SSRS and SSIS services, the issue is the report server is not able to call the package itself.I found that the package is not invoked as i have enabled the logging. No log file is wirtten.It gives me the same old error "Not a valid win32 application" .

    Note: The same package is running fine on all the 32 bit machines , but not on the 64 bit machines.

    |||What data source are you using? Does it have a 64-bit driver?|||

    Hello All,

    The issue got resolved. I was having windows sp2 and sql sevrer sp1 on my server. After installing sp2 sql server the issue got resolved and seems to be running fine.

    Thanks to you all.

    Raju

  •