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:
>
>
