By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,313 Members | 1,145 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,313 IT Pros & Developers. It's quick & easy.

Unable to create a step in a SQLServer Job

P: n/a
I am running SQLServer 2000 SP3 with MDAC 2.8.

On instances created via MSDE, I am unable to create the first step in
a job. Instances created with SQLServer 2000, this problem does not
occur.

The message I am receiving on the instances created with MSDE, the
message I get immediately upon pressing the Add button to define a step
is "Error 170: Line 1: Incorrect syntax near '\'"

Any help would would be greatly appreciated.

Wardell Castles

Jul 23 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
wardellcastles (wa************@hotmail.com) writes:
I am running SQLServer 2000 SP3 with MDAC 2.8.

On instances created via MSDE, I am unable to create the first step in
a job. Instances created with SQLServer 2000, this problem does not
occur.

The message I am receiving on the instances created with MSDE, the
message I get immediately upon pressing the Add button to define a step
is "Error 170: Line 1: Incorrect syntax near '\'"


You do not tell how you create this step, but the \ delimiter only
appears with named instances, so presumably it is a server specificaion
that fails. In order to adress put SERVER\INSTANCE with in brackets,
for instance [SERVER\INSTANCE].
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
Jul 23 '05 #2

P: n/a
Erland,

I get the error the moment I press the "New" button on the Steps tab of
the Job Properties dialog within SQL Enterprise Manager.

It does not seem to matter if it's a named instance or the default
instance. The only thing that seems to matter is if the instance
(named or not) is created via the setup.exe of MSDE or through SQL
Server. Again, it fails with this error consistently with instances
created via MSDE but not with instances created with SQL Server.

Thanks,
Wardell Castles

Jul 23 '05 #3

P: n/a
Hi

Other than the DTS designer not being supplied with MSDE then I am not sure
what other things will stop you designing DTS packages on a MSDE database.
You could write the packages on one of the versions that ships DTS Designer
and then tranfer them to the target system get around any problems.

http://www.sqldts.com/default.aspx?204

John

"wardellcastles" <wa************@hotmail.com> wrote in message
news:11*********************@l41g2000cwc.googlegro ups.com...
Erland,

I get the error the moment I press the "New" button on the Steps tab of
the Job Properties dialog within SQL Enterprise Manager.

It does not seem to matter if it's a named instance or the default
instance. The only thing that seems to matter is if the instance
(named or not) is created via the setup.exe of MSDE or through SQL
Server. Again, it fails with this error consistently with instances
created via MSDE but not with instances created with SQL Server.

Thanks,
Wardell Castles

Jul 23 '05 #4

P: n/a
wardellcastles (wa************@hotmail.com) writes:
I get the error the moment I press the "New" button on the Steps tab of
the Job Properties dialog within SQL Enterprise Manager.

It does not seem to matter if it's a named instance or the default
instance. The only thing that seems to matter is if the instance
(named or not) is created via the setup.exe of MSDE or through SQL
Server. Again, it fails with this error consistently with instances
created via MSDE but not with instances created with SQL Server.


I used Profiler to trace what was being sent from SQL Server to see
if I could find something that would give a clue, but I was out of luck.
Still you could try this, and see if any backslashes turns up.

However, if you were able to solve the technical problem, there is a legal
problem that remains: your license does not permit you to use SQL Enterprise
Manager to administer MSDE. It does not matter that you have paid for
your Enterprise Edition or whatever you have, EM is not for MSDE. All you
can use with MSDE is OSQL (and any third-party tool you can find).

At least this is the information that I have. You may want to contact
your local Microsoft representative to have it confirmed. (And if they
say I am wrong, you trust you MS rep, not me.)

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
Jul 23 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.