I have looked at the SOAP method of integration as well as the URL method,
and it is just not possible to save report parameters as selected by the
user! The only way you can save them is if you re-invent your own parameter
inputs! And keep in mind that a complete integration solution should be able
to accept any possible combination of report parameters!
I think this is another oversight in the design of this product from
microsoft. They have specially designed ways to cache report data, saving
history, etc... But what about the more common case of wanting fresh data
for the same parameters? I am amazed that they did not think of this...
Is there anything like this in the works for version 2... Yes?
Please tell me yes :-]
MalikLet me also clarify that the difficulty here is getting the parameter input
from the user.
If I already know what parameters I want to run the report for, there is no
problem.
The problem is, the user can change them and then re-run the report, and I
have no idea
what parameters are currently in the report being displayed!
Malik
"Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
news:uL2wf3OiEHA.536@.TK2MSFTNGP11.phx.gbl...
> I have looked at the SOAP method of integration as well as the URL method,
> and it is just not possible to save report parameters as selected by the
> user! The only way you can save them is if you re-invent your own
parameter
> inputs! And keep in mind that a complete integration solution should be
able
> to accept any possible combination of report parameters!
> I think this is another oversight in the design of this product from
> microsoft. They have specially designed ways to cache report data, saving
> history, etc... But what about the more common case of wanting fresh data
> for the same parameters? I am amazed that they did not think of this...
> Is there anything like this in the works for version 2... Yes?
> Please tell me yes :-]
> Malik
>
>|||Donovan,
Thanks very much for your report. This is exactly the kind of solution I
need, although there are still a few problems.
I thought of doing it this way, but I am trying to fully integrate SQL RS
with our Web Application. I don't want to have to explain to our customers
that in order to design reports for use with our application you have to
always have those extra data sources present along with code to retrieve the
parameters. This puts the onus on the report developer to be a coder rather
than me taking care of the whole solution myself.
I suppose I could come up with some kind of template report that our
customers can start with, and that would make this a workable solution for
us. I am going over your report in more detail to see what I can learn from
it.
Your help has been quite valuable for my project, and I really appreciate
you sending the report!
Thank you very much indeed,
Malik
"Donovan R. Smith [MSFT]" <donovans@.online.microsoft.com> wrote in message
news:u8UcIjjiEHA.348@.tk2msftngp13.phx.gbl...
> Take a look at the attached report for help. It goes against the pubs
sample database and requires
> a SQL script to be run on the db prior to use.
> --
> Thanks.
> Donovan R. Smith
> Software Test Lead
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
> news:ekCjdEPiEHA.2848@.TK2MSFTNGP10.phx.gbl...
> > Let me also clarify that the difficulty here is getting the parameter
input
> > from the user.
> >
> > If I already know what parameters I want to run the report for, there is
no
> > problem.
> >
> > The problem is, the user can change them and then re-run the report, and
I
> > have no idea
> > what parameters are currently in the report being displayed!
> >
> > Malik
> >
> > "Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
> > news:uL2wf3OiEHA.536@.TK2MSFTNGP11.phx.gbl...
> > > I have looked at the SOAP method of integration as well as the URL
method,
> > > and it is just not possible to save report parameters as selected by
the
> > > user! The only way you can save them is if you re-invent your own
> > parameter
> > > inputs! And keep in mind that a complete integration solution should
be
> > able
> > > to accept any possible combination of report parameters!
> > >
> > > I think this is another oversight in the design of this product from
> > > microsoft. They have specially designed ways to cache report data,
saving
> > > history, etc... But what about the more common case of wanting fresh
data
> > > for the same parameters? I am amazed that they did not think of
this...
> > >
> > > Is there anything like this in the works for version 2... Yes?
> > >
> > > Please tell me yes :-]
> > >
> > > Malik
> > >
> > >
> > >
> >
> >
>
>|||If the web application provided it's own parameter prompting area and passed along that data to our
Report Viewer then you could build this logic into your web application instead of relying on RS to
do it.
--
Thanks.
Donovan R. Smith
Software Test Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
"Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
news:OBI3I2piEHA.3320@.TK2MSFTNGP11.phx.gbl...
> Donovan,
> Thanks very much for your report. This is exactly the kind of solution I
> need, although there are still a few problems.
> I thought of doing it this way, but I am trying to fully integrate SQL RS
> with our Web Application. I don't want to have to explain to our customers
> that in order to design reports for use with our application you have to
> always have those extra data sources present along with code to retrieve the
> parameters. This puts the onus on the report developer to be a coder rather
> than me taking care of the whole solution myself.
> I suppose I could come up with some kind of template report that our
> customers can start with, and that would make this a workable solution for
> us. I am going over your report in more detail to see what I can learn from
> it.
> Your help has been quite valuable for my project, and I really appreciate
> you sending the report!
> Thank you very much indeed,
> Malik
> "Donovan R. Smith [MSFT]" <donovans@.online.microsoft.com> wrote in message
> news:u8UcIjjiEHA.348@.tk2msftngp13.phx.gbl...
> > Take a look at the attached report for help. It goes against the pubs
> sample database and requires
> > a SQL script to be run on the db prior to use.
> >
> > --
> > Thanks.
> >
> > Donovan R. Smith
> > Software Test Lead
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
> > news:ekCjdEPiEHA.2848@.TK2MSFTNGP10.phx.gbl...
> > > Let me also clarify that the difficulty here is getting the parameter
> input
> > > from the user.
> > >
> > > If I already know what parameters I want to run the report for, there is
> no
> > > problem.
> > >
> > > The problem is, the user can change them and then re-run the report, and
> I
> > > have no idea
> > > what parameters are currently in the report being displayed!
> > >
> > > Malik
> > >
> > > "Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
> > > news:uL2wf3OiEHA.536@.TK2MSFTNGP11.phx.gbl...
> > > > I have looked at the SOAP method of integration as well as the URL
> method,
> > > > and it is just not possible to save report parameters as selected by
> the
> > > > user! The only way you can save them is if you re-invent your own
> > > parameter
> > > > inputs! And keep in mind that a complete integration solution should
> be
> > > able
> > > > to accept any possible combination of report parameters!
> > > >
> > > > I think this is another oversight in the design of this product from
> > > > microsoft. They have specially designed ways to cache report data,
> saving
> > > > history, etc... But what about the more common case of wanting fresh
> data
> > > > for the same parameters? I am amazed that they did not think of
> this...
> > > >
> > > > Is there anything like this in the works for version 2... Yes?
> > > >
> > > > Please tell me yes :-]
> > > >
> > > > Malik
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >
>|||Yes, I could write my own code to take care of parameter input, which would
have to do the following:
- prompt for any combination of parameters
- include default values and available values, with queried available
values in a drop-down list
- validate all parameter data types entered, null and blank values
- correctly take hidden parameters from the URL when they are passed
This would have to be robust enough for any report that my customers can
design to work with my web app.
I don't want to be lazy, but since RS already does all of this, I don't want
to re-invent the wheel.
I think it would be much easier for someone who already knows what
parameters are in the reports. In my scenario, our customers will expect to
just open a SQL RS report from our web app. They may design their own, or
get reports from elsewhere. It is a full integration.
I am still very much in design mode (although I should have finished long
ago :-) so I am quite open to suggestions.
Thanks again for your help.
Malik
"Donovan R. Smith [MSFT]" <donovans@.online.microsoft.com> wrote in message
news:eCLqPftiEHA.3896@.TK2MSFTNGP15.phx.gbl...
> If the web application provided it's own parameter prompting area and
passed along that data to our
> Report Viewer then you could build this logic into your web application
instead of relying on RS to
> do it.
> --
> Thanks.
> Donovan R. Smith
> Software Test Lead
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
> news:OBI3I2piEHA.3320@.TK2MSFTNGP11.phx.gbl...
> > Donovan,
> >
> > Thanks very much for your report. This is exactly the kind of solution I
> > need, although there are still a few problems.
> >
> > I thought of doing it this way, but I am trying to fully integrate SQL
RS
> > with our Web Application. I don't want to have to explain to our
customers
> > that in order to design reports for use with our application you have to
> > always have those extra data sources present along with code to retrieve
the
> > parameters. This puts the onus on the report developer to be a coder
rather
> > than me taking care of the whole solution myself.
> >
> > I suppose I could come up with some kind of template report that our
> > customers can start with, and that would make this a workable solution
for
> > us. I am going over your report in more detail to see what I can learn
from
> > it.
> >
> > Your help has been quite valuable for my project, and I really
appreciate
> > you sending the report!
> >
> > Thank you very much indeed,
> > Malik
> >
> > "Donovan R. Smith [MSFT]" <donovans@.online.microsoft.com> wrote in
message
> > news:u8UcIjjiEHA.348@.tk2msftngp13.phx.gbl...
> > > Take a look at the attached report for help. It goes against the pubs
> > sample database and requires
> > > a SQL script to be run on the db prior to use.
> > >
> > > --
> > > Thanks.
> > >
> > > Donovan R. Smith
> > > Software Test Lead
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > >
> > > "Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
> > > news:ekCjdEPiEHA.2848@.TK2MSFTNGP10.phx.gbl...
> > > > Let me also clarify that the difficulty here is getting the
parameter
> > input
> > > > from the user.
> > > >
> > > > If I already know what parameters I want to run the report for,
there is
> > no
> > > > problem.
> > > >
> > > > The problem is, the user can change them and then re-run the report,
and
> > I
> > > > have no idea
> > > > what parameters are currently in the report being displayed!
> > > >
> > > > Malik
> > > >
> > > > "Abdul Malik Said" <diplacusis@.hotmNOSPAMail.com> wrote in message
> > > > news:uL2wf3OiEHA.536@.TK2MSFTNGP11.phx.gbl...
> > > > > I have looked at the SOAP method of integration as well as the URL
> > method,
> > > > > and it is just not possible to save report parameters as selected
by
> > the
> > > > > user! The only way you can save them is if you re-invent your own
> > > > parameter
> > > > > inputs! And keep in mind that a complete integration solution
should
> > be
> > > > able
> > > > > to accept any possible combination of report parameters!
> > > > >
> > > > > I think this is another oversight in the design of this product
from
> > > > > microsoft. They have specially designed ways to cache report data,
> > saving
> > > > > history, etc... But what about the more common case of wanting
fresh
> > data
> > > > > for the same parameters? I am amazed that they did not think of
> > this...
> > > > >
> > > > > Is there anything like this in the works for version 2... Yes?
> > > > >
> > > > > Please tell me yes :-]
> > > > >
> > > > > Malik
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
>
Showing posts with label integration. Show all posts
Showing posts with label integration. Show all posts
Monday, March 19, 2012
Sunday, March 11, 2012
Can''t run integration services package as a sql server agent task
Hi guys, I 've been trying to run an integration services package as server agent scheduled task so that I dont have to manually execute the package every 2 hours. I was following how to guide in msdn to set up a server agant task for integration services package but I'm kind a lost. First of all when I ran the Management Studio and connected to the integration services the server agent does not show up it only shows me runing and stored packages. I can access to the server agent when I connect to the database engine but when I create a task and try to add a step to open a integration services package it does not give me the choice in type box. I couldn't figure out the problem. Is there a way to enable server agent to run under integration services too (not just under database engine) if databse engine is the only place server agents works , why dont I see the option to open a ssis package at adding a step to tasks? or is there a way to automate the process to run the package automatically without using the server agent at all?
Thanks,
Burak
PS I was following the http://msdn2.microsoft.com/en-us/library/ms139805.aspx article
You will find SQL Server Agent only under the relational DB and that is fine.; You should be able to create a job with an step to run the package you want to.
You have 2 option for the step type; you can use a SSIS package type or a command line (CmdExc) type.
This is a KB article with the most common problems when scheduling a package and their workarounds:
http://support.microsoft.com/kb/918760
BTW, Where is the package stored?
|||The server agent is part of the database engine.
You will need to set up the proxy / credential / etc...
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1955723&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=703968&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1322146&SiteID=1
|||package is stored in the same file system as the sql server.
By the way when I chose the type as CmdExec it gives me sql error #14250 and it says my command is longer than 3200 chars as it tries to run the whole xml file as a command line prompt I guess. I believe if I can find a way to activate SSIS package option at the package type field I might be able to get pass this problem I'm going to try the solution with the proxy account maybe that will help.
|||Ok I tried to follow the tutorials about how to create proxies and credentials unfortunatly when I expand the security tab of the database engine it just shows me logins and server roles no credentials. I do wonder wouldn't be easier if Microsoft just added the functionality to schedule the packages through Business Intelligence. I'm just frusturated following through all those how to's and at the end of the day still having the same problem.
|||You tried the security folder of the overall server, and not the database that you are using? Are you using SQL Server Management Studio? It should be there....
Can''t run integration services package as a sql server agent task
Hi guys, I 've been trying to run an integration services package as server agent scheduled task so that I dont have to manually execute the package every 2 hours. I was following how to guide in msdn to set up a server agant task for integration services package but I'm kind a lost. First of all when I ran the Management Studio and connected to the integration services the server agent does not show up it only shows me runing and stored packages. I can access to the server agent when I connect to the database engine but when I create a task and try to add a step to open a integration services package it does not give me the choice in type box. I couldn't figure out the problem. Is there a way to enable server agent to run under integration services too (not just under database engine) if databse engine is the only place server agents works , why dont I see the option to open a ssis package at adding a step to tasks? or is there a way to automate the process to run the package automatically without using the server agent at all?
Thanks,
Burak
PS I was following the http://msdn2.microsoft.com/en-us/library/ms139805.aspx article
You will find SQL Server Agent only under the relational DB and that is fine.; You should be able to create a job with an step to run the package you want to.
You have 2 option for the step type; you can use a SSIS package type or a command line (CmdExc) type.
This is a KB article with the most common problems when scheduling a package and their workarounds:
http://support.microsoft.com/kb/918760
BTW, Where is the package stored?
|||The server agent is part of the database engine.
You will need to set up the proxy / credential / etc...
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1955723&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=703968&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1322146&SiteID=1
|||package is stored in the same file system as the sql server.
By the way when I chose the type as CmdExec it gives me sql error #14250 and it says my command is longer than 3200 chars as it tries to run the whole xml file as a command line prompt I guess. I believe if I can find a way to activate SSIS package option at the package type field I might be able to get pass this problem I'm going to try the solution with the proxy account maybe that will help.
|||Ok I tried to follow the tutorials about how to create proxies and credentials unfortunatly when I expand the security tab of the database engine it just shows me logins and server roles no credentials. I do wonder wouldn't be easier if Microsoft just added the functionality to schedule the packages through Business Intelligence. I'm just frusturated following through all those how to's and at the end of the day still having the same problem.
|||You tried the security folder of the overall server, and not the database that you are using? Are you using SQL Server Management Studio? It should be there....
Can''t run integration services package as a sql server agent task
Hi guys, I 've been trying to run an integration services package as server agent scheduled task so that I dont have to manually execute the package every 2 hours. I was following how to guide in msdn to set up a server agant task for integration services package but I'm kind a lost. First of all when I ran the Management Studio and connected to the integration services the server agent does not show up it only shows me runing and stored packages. I can access to the server agent when I connect to the database engine but when I create a task and try to add a step to open a integration services package it does not give me the choice in type box. I couldn't figure out the problem. Is there a way to enable server agent to run under integration services too (not just under database engine) if databse engine is the only place server agents works , why dont I see the option to open a ssis package at adding a step to tasks? or is there a way to automate the process to run the package automatically without using the server agent at all?
Thanks,
Burak
PS I was following the http://msdn2.microsoft.com/en-us/library/ms139805.aspx article
You will find SQL Server Agent only under the relational DB and that is fine.; You should be able to create a job with an step to run the package you want to.
You have 2 option for the step type; you can use a SSIS package type or a command line (CmdExc) type.
This is a KB article with the most common problems when scheduling a package and their workarounds:
http://support.microsoft.com/kb/918760
BTW, Where is the package stored?
|||The server agent is part of the database engine.
You will need to set up the proxy / credential / etc...
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1955723&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=703968&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1322146&SiteID=1
|||package is stored in the same file system as the sql server.
By the way when I chose the type as CmdExec it gives me sql error #14250 and it says my command is longer than 3200 chars as it tries to run the whole xml file as a command line prompt I guess. I believe if I can find a way to activate SSIS package option at the package type field I might be able to get pass this problem I'm going to try the solution with the proxy account maybe that will help.
|||Ok I tried to follow the tutorials about how to create proxies and credentials unfortunatly when I expand the security tab of the database engine it just shows me logins and server roles no credentials. I do wonder wouldn't be easier if Microsoft just added the functionality to schedule the packages through Business Intelligence. I'm just frusturated following through all those how to's and at the end of the day still having the same problem.
|||You tried the security folder of the overall server, and not the database that you are using? Are you using SQL Server Management Studio? It should be there....
Can''t run integration services package as a sql server agent task
Hi guys, I 've been trying to run an integration services package as server agent scheduled task so that I dont have to manually execute the package every 2 hours. I was following how to guide in msdn to set up a server agant task for integration services package but I'm kind a lost. First of all when I ran the Management Studio and connected to the integration services the server agent does not show up it only shows me runing and stored packages. I can access to the server agent when I connect to the database engine but when I create a task and try to add a step to open a integration services package it does not give me the choice in type box. I couldn't figure out the problem. Is there a way to enable server agent to run under integration services too (not just under database engine) if databse engine is the only place server agents works , why dont I see the option to open a ssis package at adding a step to tasks? or is there a way to automate the process to run the package automatically without using the server agent at all?
Thanks,
Burak
PS I was following the http://msdn2.microsoft.com/en-us/library/ms139805.aspx article
You will find SQL Server Agent only under the relational DB and that is fine.; You should be able to create a job with an step to run the package you want to.
You have 2 option for the step type; you can use a SSIS package type or a command line (CmdExc) type.
This is a KB article with the most common problems when scheduling a package and their workarounds:
http://support.microsoft.com/kb/918760
BTW, Where is the package stored?
|||The server agent is part of the database engine.
You will need to set up the proxy / credential / etc...
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1955723&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=703968&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1322146&SiteID=1
|||package is stored in the same file system as the sql server.
By the way when I chose the type as CmdExec it gives me sql error #14250 and it says my command is longer than 3200 chars as it tries to run the whole xml file as a command line prompt I guess. I believe if I can find a way to activate SSIS package option at the package type field I might be able to get pass this problem I'm going to try the solution with the proxy account maybe that will help.
|||Ok I tried to follow the tutorials about how to create proxies and credentials unfortunatly when I expand the security tab of the database engine it just shows me logins and server roles no credentials. I do wonder wouldn't be easier if Microsoft just added the functionality to schedule the packages through Business Intelligence. I'm just frusturated following through all those how to's and at the end of the day still having the same problem.
|||You tried the security folder of the overall server, and not the database that you are using? Are you using SQL Server Management Studio? It should be there....
Can''t run integration services package as a sql server agent task
Hi guys, I 've been trying to run an integration services package as server agent scheduled task so that I dont have to manually execute the package every 2 hours. I was following how to guide in msdn to set up a server agant task for integration services package but I'm kind a lost. First of all when I ran the Management Studio and connected to the integration services the server agent does not show up it only shows me runing and stored packages. I can access to the server agent when I connect to the database engine but when I create a task and try to add a step to open a integration services package it does not give me the choice in type box. I couldn't figure out the problem. Is there a way to enable server agent to run under integration services too (not just under database engine) if databse engine is the only place server agents works , why dont I see the option to open a ssis package at adding a step to tasks? or is there a way to automate the process to run the package automatically without using the server agent at all?
Thanks,
Burak
PS I was following the http://msdn2.microsoft.com/en-us/library/ms139805.aspx article
You will find SQL Server Agent only under the relational DB and that is fine.; You should be able to create a job with an step to run the package you want to.
You have 2 option for the step type; you can use a SSIS package type or a command line (CmdExc) type.
This is a KB article with the most common problems when scheduling a package and their workarounds:
http://support.microsoft.com/kb/918760
BTW, Where is the package stored?
|||The server agent is part of the database engine.
You will need to set up the proxy / credential / etc...
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1955723&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=703968&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1322146&SiteID=1
|||package is stored in the same file system as the sql server.
By the way when I chose the type as CmdExec it gives me sql error #14250 and it says my command is longer than 3200 chars as it tries to run the whole xml file as a command line prompt I guess. I believe if I can find a way to activate SSIS package option at the package type field I might be able to get pass this problem I'm going to try the solution with the proxy account maybe that will help.
|||Ok I tried to follow the tutorials about how to create proxies and credentials unfortunatly when I expand the security tab of the database engine it just shows me logins and server roles no credentials. I do wonder wouldn't be easier if Microsoft just added the functionality to schedule the packages through Business Intelligence. I'm just frusturated following through all those how to's and at the end of the day still having the same problem.
|||You tried the security folder of the overall server, and not the database that you are using? Are you using SQL Server Management Studio? It should be there....
Can''t run integration services package as a sql server agent task
Hi guys, I 've been trying to run an integration services package as server agent scheduled task so that I dont have to manually execute the package every 2 hours. I was following how to guide in msdn to set up a server agant task for integration services package but I'm kind a lost. First of all when I ran the Management Studio and connected to the integration services the server agent does not show up it only shows me runing and stored packages. I can access to the server agent when I connect to the database engine but when I create a task and try to add a step to open a integration services package it does not give me the choice in type box. I couldn't figure out the problem. Is there a way to enable server agent to run under integration services too (not just under database engine) if databse engine is the only place server agents works , why dont I see the option to open a ssis package at adding a step to tasks? or is there a way to automate the process to run the package automatically without using the server agent at all?
Thanks,
Burak
PS I was following the http://msdn2.microsoft.com/en-us/library/ms139805.aspx article
You will find SQL Server Agent only under the relational DB and that is fine.; You should be able to create a job with an step to run the package you want to.
You have 2 option for the step type; you can use a SSIS package type or a command line (CmdExc) type.
This is a KB article with the most common problems when scheduling a package and their workarounds:
http://support.microsoft.com/kb/918760
BTW, Where is the package stored?
|||The server agent is part of the database engine.
You will need to set up the proxy / credential / etc...
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1955723&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=703968&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1322146&SiteID=1
|||package is stored in the same file system as the sql server.
By the way when I chose the type as CmdExec it gives me sql error #14250 and it says my command is longer than 3200 chars as it tries to run the whole xml file as a command line prompt I guess. I believe if I can find a way to activate SSIS package option at the package type field I might be able to get pass this problem I'm going to try the solution with the proxy account maybe that will help.
|||Ok I tried to follow the tutorials about how to create proxies and credentials unfortunatly when I expand the security tab of the database engine it just shows me logins and server roles no credentials. I do wonder wouldn't be easier if Microsoft just added the functionality to schedule the packages through Business Intelligence. I'm just frusturated following through all those how to's and at the end of the day still having the same problem.
|||You tried the security folder of the overall server, and not the database that you are using? Are you using SQL Server Management Studio? It should be there....
Sunday, February 19, 2012
can't load SSIS dtsx package
hi there,
when i start SQL Server business intelligence developer and create new Integration Service project, i will see following error:
Error loading 'Package.dtsx' : Object reference not set to an instance of an object.. C:\Sairi\My Documents\Visual Studio 2005\Projects\Integration Services Project12\Integration Services Project12\Package.dtsx
this error occures just on my PC and i reinstalled VS2005 and SQL2005 again and unfotunately the problem existes.
please someone helps me (just don't tell me to format my PC!!!)
tnx
It looks like BIDS is trying to open a project/package that does not exists anymore. The weird thing is that when that happens BIDS prompts you to remove the invalid references and the error goes away. Don't you see that message?
Can you do File->Close solution/project ?
BTW, that error should not prevent you from using BIDS.
as a good practice always use close solution/project before closing BIDS. This is because BIDS always tries to re-open all projects and packages that were opend at the time of exiting.
|||Dear Rafael,Many thanks for your response.
but my i want to Create/Edit DTS packages in BIDS and i cant.
my VS Net 2005 works properly.
my problem is creating or editing SSIS packages in BIDS.
even in new SSIS project when i add new SSIS packages or existing packages (dtsx) my BIDS doesn't show its designer and shows same error.
i think it cant find SSIS DTS base class or its references for showing SSIS designer.|||It looks like an installation issue to me. Try re-installing the client tools to see if BIDS gets fixed.|||
I second that, it's likely a setup issue. Pls try to confirm for example whether "dts.dll" is under your \Program Files\Microsoft SQL Server\90\DTS\Binn to see whether you did encounter a setup issue and if yes, reinstall Integration Service from SQL Server Work Station Components to see whether that helps.
Thanks
|||Pejman - do you any have third party Visual Studio add-ins installed?
Also, try installing SQL Server 2005 SP2.
|||dear , thanks for your responses.i agree with you.its an installation problem but after re-installing the problem was exist.
i think my its because of Windows Registry!!|||Dear Friend,
"dts.dll" file exist in the SQL path as you said.
also i reinstaling SSIS and some workstation components.
but the same problem !!!
also it can't open SSIS samples.|||Dear Michael,
yes, i had some VS add-ins and i remove them.
and again reinstalling SQL server developer and the problem exist.
soon i will download SQL2005 SP2 and inform you.
TNX|||Hello Dear All,
finally i solved the problem.
i installed MSSQL 2000 Personal Edition on my computer then my SSIS problem is now solved.
thanks all of you.
Tuesday, February 14, 2012
Can't Install Integration Services on SQL 2005 (Windows Server 2003)
Hello - We have been unable to successfully install Integration Services with an instance of SQL 2005 running on a Windows Small Business Server 2003. Installation proceeds with no errors, but when you attempt to connect to the Integrations Services and browse to where it apparently exists, the SQL Server Managment Studio returns the following error:
TITLE: Connect to Server
Cannot connect to ABDI04.
ADDITIONAL INFORMATION:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
Connect to SSIS Service on machine "ABDI04" failed:
The specified service does not exist as an installed service.
.
Connect to SSIS Service on machine "ABDI04" failed:
The specified service does not exist as an installed service.
.
BUTTONS:
OK
We have tried uninstalling the Integration Services, then reinstalling it and again applying SP2 with the same results.
Thank you.
did you check in the sql server configuration manager? were you able to view the SSIS service there?if yes, is the service started ? ? ?if not just start the services and try to logon
also did you check in C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt file if the installation was successful ? ? ?
|||Hello Deepak -
I am not able to view SSIS in configuration manager and the service is not present with the other system services. Using your suggestion, I also verified the Summary txt file:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Microsoft Windows Server 2003 family, Service Pack 2 (Build 3790)
Time : Sat Jul 14 15:57:47 2007
ABDI04 : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
Machine : ABDI04
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_ABDI04_SQLSupport_1.log
--
Machine : ABDI04
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_ABDI04_SQLNCLI_1.log
--
Machine : ABDI04
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_ABDI04_OWC11_1.log
--
Machine : ABDI04
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.2004
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_ABDI04_BackwardsCompat_1.log
--
Machine : ABDI04
Product : MSXML 6.0 Parser
Product Version : 6.10.1129.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_ABDI04_MSXML6_1.log
--
Machine : ABDI04
Product : Microsoft SQL Server 2005 Integration Services
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_ABDI04_DTS.log
--
Setup succeeded with the installation, inspect the log file completely for status on all the components.Time : Sat Jul 14 16:03:43 2007
and it seems to confirm that the installation proceeded to a successful conclusion.
Do you have any other suggestions? Thank you very much - Bryan
|||Hi,look if the "SQL Server Integration Services" is installed. If not, which version of SQL Server are you running on the machine (Therefore examine the "SQL Server (InstanceNamehere)" services mentioned in the SCM.
Jens K. Suessmeyer.
-
http:://www.sqlserver2005.de
-|||Hello,
we have exactly the same problem. We installed completely new installation of SQL 2005 Server to a new installation of Small Business 2003. We ensured that the "Integration Services" option in the installation was set to "install entirely" mark. After no error reported installation we found out that the "SSIS Service" is not present among the system services, not even in the SQL configuration manager services.
However, the installation log file reports:
Product : Microsoft SQL Server 2005 Integration Services
Product Version : 9.00.1399.06
Install : Successful
Of course, we are not able to connect or using the Integration services. So, the question is, how can we install the Integration Service into the system?
Can anyone help?
|||Is the service started ? Can be found in the Service control manager (SCM) in Windows.
Jens K. Suessmeyer
http://www.sqlserver2005.de
|||Well, as I said, the service did NOT install into the system. (We checked both the Windows System Services and SQL Service control manager). So the answer is NO, the service is not started (because is not installed).
Jonas
|||One more thing: could anyone provide us the information, what executable file is related to SSIS servise to launch (with the the proper command line switches, if any)?
We would like to locate this executable on the drive and try to launch it manually.
thanks
Subscribe to:
Posts (Atom)