cannot create job steps in 2005

I have a feeling this might be a security problem so I posting the question
in the security group as well. Sorry for the double post, I'll paste any
answers over there as well.
Here's the problem;
I'm trying to do some prototyping with SQL 2005 Standard - Full Text Search
in preparation for moving away from SQL 2000. I setup a FTS index and tried
to create a job to rebuild the index nightly. This job build feature is
built right into the
FTS wizard. The job is created but it fails to create the steps and just
says "Failed to connect to server...blah blah blah....Naped Pipes Provider,
Error 40, Could not open connection"
At first I thought it was something with FTS not configured right but then I
just tried to create simple maintenance plan job and the same thing
happened. It
couldn't create the job step. The message from that was even more helpful.
It said "Job failed" I'm doing all this from SSMS logged in with SA.
Anyone have any idea why I can't create job steps on a newly installed SQL
2005 using SA?
Thanks in advance
--
MazSome of the things to check for:
- Make sure that the 'shared memory' prtocol is enabled on the server and
has order=1
- Make sure that sql server is configured to listen on the shared memory net
lib
You can check the settings using the SQL Server Configuration Manager.
hth
--
Vikram Vamshi
Database Engineer
Eclipsys Corporation
"Spicy Mikey" <Maz@.newsgroups.nospam> wrote in message
news:A993F690-0AC3-4FA6-9760-85C2F24523C8@.microsoft.com...
>I have a feeling this might be a security problem so I posting the question
> in the security group as well. Sorry for the double post, I'll paste any
> answers over there as well.
> Here's the problem;
> I'm trying to do some prototyping with SQL 2005 Standard - Full Text
> Search
> in preparation for moving away from SQL 2000. I setup a FTS index and
> tried
> to create a job to rebuild the index nightly. This job build feature is
> built right into the
> FTS wizard. The job is created but it fails to create the steps and just
> says "Failed to connect to server...blah blah blah....Naped Pipes
> Provider,
> Error 40, Could not open connection"
> At first I thought it was something with FTS not configured right but then
> I
> just tried to create simple maintenance plan job and the same thing
> happened. It
> couldn't create the job step. The message from that was even more
> helpful.
> It said "Job failed" I'm doing all this from SSMS logged in with SA.
> Anyone have any idea why I can't create job steps on a newly installed SQL
> 2005 using SA?
> Thanks in advance
> --
> Maz
>|||Thanks Vikran
I have everything enabled except VIA. Don't know what that is so I left it
alone.
I think there's something wrong with this FTS product in SQL Server. I'm
logged into SQL as the system adminstrator (sa). I'm also logged onto
windows as a domain admin. It can't be security. it doesn't seem to be a
config problem. I'm stumped
--
Maz
"Vikram Vamshi" wrote:

> Some of the things to check for:
> - Make sure that the 'shared memory' prtocol is enabled on the server and
> has order=1
> - Make sure that sql server is configured to listen on the shared memory n
et
> lib
> You can check the settings using the SQL Server Configuration Manager.
> hth
> --
> Vikram Vamshi
> Database Engineer
> Eclipsys Corporation
> "Spicy Mikey" <Maz@.newsgroups.nospam> wrote in message
> news:A993F690-0AC3-4FA6-9760-85C2F24523C8@.microsoft.com...
>
>|||Did you ever get this resolved? I'm having the same problem. I'm using
the sa account and logged in as domain admin and yet I cannot create a
job step for any maintenance plan. We're running SQL 2005 Standard
with noe fancy bells or whistles. Even the "Wizard" craps out every
time. Can anyone offer any advice?
E
On Feb 5, 8:34 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
> Thanks Vikran
> I have everything enabled except VIA. Don't know what that is so I left i
t
> alone.
> I think there's something wrong with this FTS product inSQLServer. I'm
> logged intoSQLas the system adminstrator (sa). I'm also logged onto
> windows as a domain admin. It can't be security. it doesn't seem to be a
> config problem. I'm stumped
> --
> Maz
>
> "Vikram Vamshi" wrote:
>
>
>
>
>
>
> - Show quoted text -|||No, I never got it resolved. For the time being I've tabled the issue and
moved on to the rest of the project development. However, I will need an
answer in a few weeks.
Doesn anyone understand what has changed with permissions in SQL 2005 OR is
this a hard bug and no one (except a few of us) seem to care
Thanks anyone
--
Maz
"Elroyskimms" wrote:

> Did you ever get this resolved? I'm having the same problem. I'm using
> the sa account and logged in as domain admin and yet I cannot create a
> job step for any maintenance plan. We're running SQL 2005 Standard
> with noe fancy bells or whistles. Even the "Wizard" craps out every
> time. Can anyone offer any advice?
> E
>
> On Feb 5, 8:34 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
>
>|||SP2 was released a couple of weeks ago. I read a bug report where
someone mentioned an issue similar to this and the MS tech linked to
the SP2 download site. Of course, it is always MS's policy to say
"install the service pack" as a standard answer to all of your
questions (about as useful as using 42 as the answer). I will try and
run the install of SP2 over the weekend and see if that resolves the
issue. I'll report back here with the results.
-E
On Mar 5, 6:16 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
> No, I never got it resolved. For the time being I've tabled the issue and
> moved on to the rest of the project development. However, I will need an
> answer in a few weeks.
> Doesn anyone understand what has changed with permissions in SQL 2005 OR i
s
> this a hard bug and no one (except a few of us) seem to care
> Thanks anyone
> --
> Maz
>
> "Elroyskimms" wrote:
>
>
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -|||Theh machine I'm running this on is Windows 2003 Server. It has all the
latest security updates, sp's, etc. It's totally clean
Give it a shot but don't hold your breath until it works.
MICROSOFT TECHS MONITORING THIS BOARD: Any suggestions?
Maz
"Elroyskimms" wrote:

> SP2 was released a couple of weeks ago. I read a bug report where
> someone mentioned an issue similar to this and the MS tech linked to
> the SP2 download site. Of course, it is always MS's policy to say
> "install the service pack" as a standard answer to all of your
> questions (about as useful as using 42 as the answer). I will try and
> run the install of SP2 over the weekend and see if that resolves the
> issue. I'll report back here with the results.
> -E
> On Mar 5, 6:16 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
>
>

cannot create job steps in 2005

I have a feeling this might be a security problem so I posting the question
in the security group as well. Sorry for the double post, I'll paste any
answers over there as well.
Here's the problem;
I'm trying to do some prototyping with SQL 2005 Standard - Full Text Search
in preparation for moving away from SQL 2000. I setup a FTS index and tried
to create a job to rebuild the index nightly. This job build feature is
built right into the
FTS wizard. The job is created but it fails to create the steps and just
says "Failed to connect to server...blah blah blah....Naped Pipes Provider,
Error 40, Could not open connection"
At first I thought it was something with FTS not configured right but then I
just tried to create simple maintenance plan job and the same thing
happened. It
couldn't create the job step. The message from that was even more helpful.
It said "Job failed" I'm doing all this from SSMS logged in with SA.
Anyone have any idea why I can't create job steps on a newly installed SQL
2005 using SA?
Thanks in advance
Maz
Some of the things to check for:
- Make sure that the 'shared memory' prtocol is enabled on the server and
has order=1
- Make sure that sql server is configured to listen on the shared memory net
lib
You can check the settings using the SQL Server Configuration Manager.
hth
Vikram Vamshi
Database Engineer
Eclipsys Corporation
"Spicy Mikey" <Maz@.newsgroups.nospam> wrote in message
news:A993F690-0AC3-4FA6-9760-85C2F24523C8@.microsoft.com...
>I have a feeling this might be a security problem so I posting the question
> in the security group as well. Sorry for the double post, I'll paste any
> answers over there as well.
> Here's the problem;
> I'm trying to do some prototyping with SQL 2005 Standard - Full Text
> Search
> in preparation for moving away from SQL 2000. I setup a FTS index and
> tried
> to create a job to rebuild the index nightly. This job build feature is
> built right into the
> FTS wizard. The job is created but it fails to create the steps and just
> says "Failed to connect to server...blah blah blah....Naped Pipes
> Provider,
> Error 40, Could not open connection"
> At first I thought it was something with FTS not configured right but then
> I
> just tried to create simple maintenance plan job and the same thing
> happened. It
> couldn't create the job step. The message from that was even more
> helpful.
> It said "Job failed" I'm doing all this from SSMS logged in with SA.
> Anyone have any idea why I can't create job steps on a newly installed SQL
> 2005 using SA?
> Thanks in advance
> --
> Maz
>
|||Thanks Vikran
I have everything enabled except VIA. Don't know what that is so I left it
alone.
I think there's something wrong with this FTS product in SQL Server. I'm
logged into SQL as the system adminstrator (sa). I'm also logged onto
windows as a domain admin. It can't be security. it doesn't seem to be a
config problem. I'm stumped
Maz
"Vikram Vamshi" wrote:

> Some of the things to check for:
> - Make sure that the 'shared memory' prtocol is enabled on the server and
> has order=1
> - Make sure that sql server is configured to listen on the shared memory net
> lib
> You can check the settings using the SQL Server Configuration Manager.
> hth
> --
> Vikram Vamshi
> Database Engineer
> Eclipsys Corporation
> "Spicy Mikey" <Maz@.newsgroups.nospam> wrote in message
> news:A993F690-0AC3-4FA6-9760-85C2F24523C8@.microsoft.com...
>
>
|||Did you ever get this resolved? I'm having the same problem. I'm using
the sa account and logged in as domain admin and yet I cannot create a
job step for any maintenance plan. We're running SQL 2005 Standard
with noe fancy bells or whistles. Even the "Wizard" craps out every
time. Can anyone offer any advice?
E
On Feb 5, 8:34 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
> Thanks Vikran
> I have everything enabled except VIA. Don't know what that is so I left it
> alone.
> I think there's something wrong with this FTS product inSQLServer. I'm
> logged intoSQLas the system adminstrator (sa). I'm also logged onto
> windows as a domain admin. It can't be security. it doesn't seem to be a
> config problem. I'm stumped
> --
> Maz
>
> "Vikram Vamshi" wrote:
>
>
>
> - Show quoted text -
|||No, I never got it resolved. For the time being I've tabled the issue and
moved on to the rest of the project development. However, I will need an
answer in a few weeks.
Doesn anyone understand what has changed with permissions in SQL 2005 OR is
this a hard bug and no one (except a few of us) seem to care
Thanks anyone
Maz
"Elroyskimms" wrote:

> Did you ever get this resolved? I'm having the same problem. I'm using
> the sa account and logged in as domain admin and yet I cannot create a
> job step for any maintenance plan. We're running SQL 2005 Standard
> with noe fancy bells or whistles. Even the "Wizard" craps out every
> time. Can anyone offer any advice?
> E
>
> On Feb 5, 8:34 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
>
>
|||SP2 was released a couple of weeks ago. I read a bug report where
someone mentioned an issue similar to this and the MS tech linked to
the SP2 download site. Of course, it is always MS's policy to say
"install the service pack" as a standard answer to all of your
questions (about as useful as using 42 as the answer). I will try and
run the install of SP2 over the weekend and see if that resolves the
issue. I'll report back here with the results.
-E
On Mar 5, 6:16 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
> No, I never got it resolved. For the time being I've tabled the issue and
> moved on to the rest of the project development. However, I will need an
> answer in a few weeks.
> Doesn anyone understand what has changed with permissions in SQL 2005 OR is
> this a hard bug and no one (except a few of us) seem to care
> Thanks anyone
> --
> Maz
>
> "Elroyskimms" wrote:
>
>
>
>
>
>
> - Show quoted text -
|||Theh machine I'm running this on is Windows 2003 Server. It has all the
latest security updates, sp's, etc. It's totally clean
Give it a shot but don't hold your breath until it works.
MICROSOFT TECHS MONITORING THIS BOARD: Any suggestions?
Maz
"Elroyskimms" wrote:

> SP2 was released a couple of weeks ago. I read a bug report where
> someone mentioned an issue similar to this and the MS tech linked to
> the SP2 download site. Of course, it is always MS's policy to say
> "install the service pack" as a standard answer to all of your
> questions (about as useful as using 42 as the answer). I will try and
> run the install of SP2 over the weekend and see if that resolves the
> issue. I'll report back here with the results.
> -E
> On Mar 5, 6:16 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
>
>

Cannot create a custom task

I've gone through all the steps, and when I finally drag the custom task I've made into the control flow, I get the error

"Failed to create the task. ... Cannot create a task with the name "SSISExportToExcel.ExcelExport.ExcelExport, SSISExcelExport, ... Verify the name is correct"

Here's the beginning of my class... any help would be appreciated...

Namespace ExcelExport
<DtsTask(DisplayName:="Excel Export Task", _
Description:="Exports a SQL query results to an Excel Document")> _
Public Class ExcelExport
Inherits Task
....
It looks like either your namespace or your assembly name does not match what you have specified. The error message indicates that it is looking for "SSISExportToExcel.ExcelExport.ExcelExport" as the type name, and "SSISExcelExport" as the assembly name.|||ok, so how would I resolve this? I kind of copied an example when it came to the namespace, etc... so I'm not sure I have that right. How would I change the type name?|||by the way, I've removed the namespace, and made sure it's named correctly, and the two names are now "SSISExcelExport.ExcelExport, SSISExcelExport". It looks like the difference in names is caused by the "public class excelexport" in my assembly.

How do I change the assembly name or type name to get these to be equivalent?
|||I might get this wrong, as naming of assemblies and namespaces is not my strong suit. The type name is the namespace + the name of the public class you are referencing. So your namespace (and asembly) should be named SSISExcelExport, and your class should be named ExcelExport. I believe that it is case sensitive.|||Hmmmm... not sure that this is the problem. I now get the error

"Cannot create a task with the name "SSISExcelExport.ExcelExport, SSISExcelExport.ExcelExport, Version .... Verify that the name is correct."
|||

Something is wrong, because it should only be asking for the type in one part of the name.

Not sure what to tell you. I'd suspect that either the namespace or assembly is not being set properly, or the GAC still has an older version registered.

|||Any other ideas here?

I believe I've uninstalled old versions through the gacutil ... using a batch file...

cd \
cd "Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin"
gacutil -u SSISExcelExport.ExcelExport
gacutil -if "C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\SSISExcelExport.ExcelExport.dll"

and as for my namespace, not sure what to do.
|||

From the error message you mentioned above, it looks like there is still something not right in the namespace declaration.

Your assembly name is the same as your dll name, minus .dll. I'd suggest making sure that the namespace declaration in your component matches your assembly name, just for convenience. Then, when creating the task, it should reference the assembly name ("SSISExcelExport.ExcelExport") and type ("SSISExcelExport.ExcelExport.<name of your public class>").

|||

Take a step back here, tasks do not care what namespace or assembly name you use. There is no reference to them in code, just in a package, or perhaps the designer. So for error #1 to have happened it says that this is an existing package and you have changed the string name of the task since it was built, or there is a mismatch between the cached task information in the designer and what is now installed in the GAC. Start a new package from scratch. It sounds like this is what you may have done in which case why does the designer think a task existing which it can not then create for you? Start by closing all instances of VS. Delete all copies of your task from \Program Files\SQL.. DTS\Tasks\ and also the GAC. Double check they are both clean. Open VS and Reset Toolbox, right click. Your task should now have gone from the toolbox. Make sure it has, if not why not? Close VS. Rebuild your task, add to Tasks folder and GAC, checking it is the same version, from the clean build. Then start again adding your task.

|||haven't forgotten about this... I'm going to be looking at it as soon as time permits. Thanks for the responses...