Error 954: Database has invalid schema - SQL2000

I'm restoring a database on another server, the restore from disk goes
through successfully, until I try to click on tables or views I get the
message below:
Error 954: Database 'dbname' has invalid schema
Thanks in advance for any help.ITDUDE27,
Are you using SharePoint and Small Business Server? If so, here are a
couple of links:
http://blogs.technet.com/edwalt/archive/2006/03/06/421346.aspx
http://msmvps.com/blogs/bradley/archive/2005/09/13/66344.aspx
I do have one weird thought: it sounds as if the file location for the files
in the database does not match the actual file locations of the mdf and/or
ldf. Did you use the MOVE option during the RESTORE in order to position
the files properly?
Other than that, I have no really useful suggestions.
RLF
"ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
news:DB40C301-EF5E-4664-819C-B251D4F8BE24@.microsoft.com...
> I'm restoring a database on another server, the restore from disk goes
> through successfully, until I try to click on tables or views I get the
> message below:
> Error 954: Database 'dbname' has invalid schema
> Thanks in advance for any help.
>|||Thanks Russ.
I'am running SP on SBS 2003. my Live sharepoint site is running fine and I
was able to install SP 2.0 on another server and it came up fine. I trying to
restore a copy of the live db as test and that is what is causing the error.
I had seen the second link you refered too, it was not help full. The point
of this exercise is to restore the sp database using Enterprize manager and
query it and then map it as my SP content database.
I've tried the move command using osql with no success. I think you are
absoluty correct about the Move, I'm just not having any luck, which ever way
I restore the SP db I get the same message.
Thanks in advance for any other feedback.
"Russell Fields" wrote:
> ITDUDE27,
> Are you using SharePoint and Small Business Server? If so, here are a
> couple of links:
> http://blogs.technet.com/edwalt/archive/2006/03/06/421346.aspx
> http://msmvps.com/blogs/bradley/archive/2005/09/13/66344.aspx
> I do have one weird thought: it sounds as if the file location for the files
> in the database does not match the actual file locations of the mdf and/or
> ldf. Did you use the MOVE option during the RESTORE in order to position
> the files properly?
> Other than that, I have no really useful suggestions.
> RLF
> "ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
> news:DB40C301-EF5E-4664-819C-B251D4F8BE24@.microsoft.com...
> > I'm restoring a database on another server, the restore from disk goes
> > through successfully, until I try to click on tables or views I get the
> > message below:
> >
> > Error 954: Database 'dbname' has invalid schema
> >
> > Thanks in advance for any help.
> >
> >
>
>|||Russell,
Can you comfirm the syntax for me.
Current location: N:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\avalanche.bak from other server
New location: N:\Program Files\Microsoft SQL Server\MSSQL\Data
RESTORE DATABASE avalanche_new FROM DISK = 'N:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\avalanche.bak'
WITH
MOVE 'northwind' TO 'N:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\avalanche_new.mdf'
MOVE 'northwind_log' TO 'N:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\avalanche_log.ldf'
Thanks in advance.
"Russell Fields" wrote:
> ITDUDE27,
> Are you using SharePoint and Small Business Server? If so, here are a
> couple of links:
> http://blogs.technet.com/edwalt/archive/2006/03/06/421346.aspx
> http://msmvps.com/blogs/bradley/archive/2005/09/13/66344.aspx
> I do have one weird thought: it sounds as if the file location for the files
> in the database does not match the actual file locations of the mdf and/or
> ldf. Did you use the MOVE option during the RESTORE in order to position
> the files properly?
> Other than that, I have no really useful suggestions.
> RLF
> "ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
> news:DB40C301-EF5E-4664-819C-B251D4F8BE24@.microsoft.com...
> > I'm restoring a database on another server, the restore from disk goes
> > through successfully, until I try to click on tables or views I get the
> > message below:
> >
> > Error 954: Database 'dbname' has invalid schema
> >
> > Thanks in advance for any help.
> >
> >
>
>|||ITDUDE27,
Syntax looks correct, but the code does not match your spec. Compare:
N:\Program Files\Microsoft SQL Server\MSSQL\Data
N:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\avalanche_new.mdf
If N:\ is a network drive that is not a supported configuration for SQL
Server databases. You will need to place the database files on locally
attached storage or on your SAN.
And, of course, I assume that the 'northwind%' logical names are correct.
I also usually specify a couple of things that should not be necessary in my
RESTORE command. Habit, you know, but I include the options:
RECOVERY, REPLACE
FWIW,
RLF
"ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
news:F7C1965F-448C-44F1-8DEF-9860E15E1A86@.microsoft.com...
> Russell,
> Can you comfirm the syntax for me.
> Current location: N:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\avalanche.bak from other server
> New location: N:\Program Files\Microsoft SQL Server\MSSQL\Data
>
> RESTORE DATABASE avalanche_new FROM DISK = 'N:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\avalanche.bak'
> WITH
> MOVE 'northwind' TO 'N:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\avalanche_new.mdf'
> MOVE 'northwind_log' TO 'N:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\avalanche_log.ldf'
> Thanks in advance.
>
> "Russell Fields" wrote:
>> ITDUDE27,
>> Are you using SharePoint and Small Business Server? If so, here are a
>> couple of links:
>> http://blogs.technet.com/edwalt/archive/2006/03/06/421346.aspx
>> http://msmvps.com/blogs/bradley/archive/2005/09/13/66344.aspx
>> I do have one weird thought: it sounds as if the file location for the
>> files
>> in the database does not match the actual file locations of the mdf
>> and/or
>> ldf. Did you use the MOVE option during the RESTORE in order to position
>> the files properly?
>> Other than that, I have no really useful suggestions.
>> RLF
>> "ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
>> news:DB40C301-EF5E-4664-819C-B251D4F8BE24@.microsoft.com...
>> > I'm restoring a database on another server, the restore from disk goes
>> > through successfully, until I try to click on tables or views I get the
>> > message below:
>> >
>> > Error 954: Database 'dbname' has invalid schema
>> >
>> > Thanks in advance for any help.
>> >
>> >
>>

Error 954: Database 'dbname' has invalid schema

I'm restoring a database on another server, the restore from disk goes
through successfully, until I try to click on tables or views I get the
message below:
Error 954: Database 'dbname' has invalid schema
any thoughts?Hi
Can you provide us with more info? What is the version are you using? Do you
try restore from SS2000 to SS2005?
"ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
news:35AE8C40-3659-44DB-BABB-8B65D1223181@.microsoft.com...
> I'm restoring a database on another server, the restore from disk goes
> through successfully, until I try to click on tables or views I get the
> message below:
> Error 954: Database 'dbname' has invalid schema
> any thoughts?|||Thanks for the response uri.
I'm doing the restore on SS2000 to SS2000. I'm trying to test the install of
WSS3.0 on a test environment but the restore is displaying that error.
Thanks in advance.
"Uri Dimant" wrote:
> Hi
> Can you provide us with more info? What is the version are you using? Do you
> try restore from SS2000 to SS2005?
> "ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
> news:35AE8C40-3659-44DB-BABB-8B65D1223181@.microsoft.com...
> >
> > I'm restoring a database on another server, the restore from disk goes
> > through successfully, until I try to click on tables or views I get the
> > message below:
> >
> > Error 954: Database 'dbname' has invalid schema
> >
> > any thoughts?
>
>

Error 5180: Could not open FCB for invalid file id : 120

'"Error 5180: Could not open FCB for invalid file id : 120"

When we attach the mdf and ldf files we get this error, what can we do to restore the database?

SEe this KBA http://support.microsoft.com/default.aspx?scid=kb;en-us;815183 to fix.

Error 5180: Could not open FCB for invalid file id : 120

'"Error 5180: Could not open FCB for invalid file id : 120"

When we attach the mdf and ldf files we get this error, what can we do to restore the database?

SEe this KBA http://support.microsoft.com/default.aspx?scid=kb;en-us;815183 to fix.|||

I de-tached and then attempted reattached a database from my server. I was not able to reattached, so I changed the name of the old database file by adding an X to the end. I then created a new database with the same name as the old one, deleted the new database file, and then renamed the old file by removing the X. Now when I try to open tables or veiws, I get error 5180: Could not open FCB... I followed the link to the suggestion about parallelism, ran the code, and still have the problem. I am running SQL Server 2000, but I don't know about the service packs.

ERROR 28000 Invalid authorization specification

a customer is getting on mS SQL 2000
ERROR ODBC 28000 Invalid authorization specification

I dont understand because all the rigth are OK
ASP NET USER, IISS user and so on !

i am trying to connect the to SQL from ASPX pages (it works for me and a few customers but not that one)

what can be the problem ?

thank youODBC state 28000 usually means a bad password or login. You can confirm this by running a trace of the login failed event on sql server.|||maybe he has entered a password or login somewhere and even dont remember it !
normally we have asked no login no password and no trusted connection

how do you run a trace on SQL 2000 ?

thanks again for helping|||Run Profiler from the SQL Server programs group.|||i try it ! thank you|||but the trace run and run how long ?
i get no result|||Provoke the error in your application, and you should see something.

Error 25 invalid connection string

here is the string:
Data Source=.\MSSQLSERVER;AttachDbFilename="C:\Program Files\Microsoft
SQL Server\MSSQL.1\MSSQL\Data\AdventureWorks_Data.mdf" ;Integrated
Security=True;Connect Timeout=30;User Instance=True
i am trying to connect visuyal c# express with sql server 2005 develop
edition
Can someone point what is wrong with my connection string
Try adding the "Initial Catalog=AdventureWorks" key-value pair. What's the
exception message?
See Chapter 9.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"pierre" <pf@.arobas.net> wrote in message
news:uEARym9THHA.4928@.TK2MSFTNGP03.phx.gbl...
> here is the string:
> Data Source=.\MSSQLSERVER;AttachDbFilename="C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\AdventureWorks_Data.mdf" ;Integrated
> Security=True;Connect Timeout=30;User Instance=True
> i am trying to connect visuyal c# express with sql server 2005 develop
> edition
> Can someone point what is wrong with my connection string

Error 25 invalid connection string

here is the string:
Data Source=.\MSSQLSERVER;AttachDbFilename="C:\Program Files\Microsoft
SQL Server\MSSQL.1\MSSQL\Data\AdventureWorks_Data.mdf";Integrated
Security=True;Connect Timeout=30;User Instance=True
i am trying to connect visuyal c# express with sql server 2005 develop
edition
Can someone point what is wrong with my connection stringTry adding the "Initial Catalog=AdventureWorks" key-value pair. What's the
exception message?
See Chapter 9.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"pierre" <pf@.arobas.net> wrote in message
news:uEARym9THHA.4928@.TK2MSFTNGP03.phx.gbl...
> here is the string:
> Data Source=.\MSSQLSERVER;AttachDbFilename="C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\AdventureWorks_Data.mdf";Integrated
> Security=True;Connect Timeout=30;User Instance=True
> i am trying to connect visuyal c# express with sql server 2005 develop
> edition
> Can someone point what is wrong with my connection string

Error 208: Invalid object name 'syspublications'

Hi!
Before reinstalling sql server and restoring old system databases I
forgot to delete and replication that was no longer needed. Now,
Expired Subscriptions Clean Up job fails with the following error:
Error 208: Invalid object name 'syspublications'. I don't need this
replication and would like to delete that completed but everytime I
try I get the same error message.
Please advise how can I delete all manually.
Thank you,
T.
Hi
Have you checked out http://tinyurl.com/33ls84
John
"tolcis" wrote:

> Hi!
> Before reinstalling sql server and restoring old system databases I
> forgot to delete and replication that was no longer needed. Now,
> Expired Subscriptions Clean Up job fails with the following error:
> Error 208: Invalid object name 'syspublications'. I don't need this
> replication and would like to delete that completed but everytime I
> try I get the same error message.
> Please advise how can I delete all manually.
> Thank you,
> T.
>

Error 208: Invalid object name 'syspublications'

Hi!
Before reinstalling sql server and restoring old system databases I
forgot to delete and replication that was no longer needed. Now,
Expired Subscriptions Clean Up job fails with the following error:
Error 208: Invalid object name 'syspublications'. I don't need this
replication and would like to delete that completed but everytime I
try I get the same error message.
Please advise how can I delete all manually.
Thank you,
T.Hi
Have you checked out http://tinyurl.com/33ls84
John
"tolcis" wrote:
> Hi!
> Before reinstalling sql server and restoring old system databases I
> forgot to delete and replication that was no longer needed. Now,
> Expired Subscriptions Clean Up job fails with the following error:
> Error 208: Invalid object name 'syspublications'. I don't need this
> replication and would like to delete that completed but everytime I
> try I get the same error message.
> Please advise how can I delete all manually.
> Thank you,
> T.
>

Error 208: Invalid object name 'sysextendedarticlesview'

hi,
for maintainance tasks (converting database from SQL_Latin to Latin_General)
we scripted a working merge replication and removed it with Enterprise
Manager (3 servers, 1 database, SQL 2000 SP3 on all 3 Servers).
Now, when trying to reinstall the replication (via script or EM), the
publication seems to be installed ok, snapshot passed without error. But the
setup of a new subscription fails with the following error message (raw
translation from german message):
Error 208: Invalid object name 'sysextendedarticlesview'.
(Original Errormessage: Server: Nachr.-Nr. 208, Schweregrad 16, Status 1,
Prozedur sp_addmergesubscription, Zeile 325
Ungltiger Objektname 'sysextendedarticlesview'.)
This view indeed cannot be found on one of the participating servers, but on
a different set of servers, where the same kind of replication is still
running, this view can't be found either.
Any help / suggestions would we appreciated.
TIA
Frank Linde
find a server/database that has this view on. In EM, right click on the view
and select copy. Then connect to the database you are having this problem
using EM. select tools, Query Analyzer and then hit ctrl v.
Then run this script. You may encounter more missing object problems but
they can be solved in the same way.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"A.Hoff" <z100@.gmx.org> wrote in message
news:cbk6a5$j6m$01$1@.news.t-online.com...
> hi,
> for maintainance tasks (converting database from SQL_Latin to
Latin_General)
> we scripted a working merge replication and removed it with Enterprise
> Manager (3 servers, 1 database, SQL 2000 SP3 on all 3 Servers).
> Now, when trying to reinstall the replication (via script or EM), the
> publication seems to be installed ok, snapshot passed without error. But
the
> setup of a new subscription fails with the following error message (raw
> translation from german message):
> Error 208: Invalid object name 'sysextendedarticlesview'.
> (Original Errormessage: Server: Nachr.-Nr. 208, Schweregrad 16, Status 1,
> Prozedur sp_addmergesubscription, Zeile 325
> Ungltiger Objektname 'sysextendedarticlesview'.)
> This view indeed cannot be found on one of the participating servers, but
on
> a different set of servers, where the same kind of replication is still
> running, this view can't be found either.
> Any help / suggestions would we appreciated.
> TIA
> Frank Linde
>

Error 208, Missing Stats

Hi chaps

Just been having my head messed with...

I was running a trace capturing all errors and SQL. Had a bucket of
error 208's (invalid object name). Found the SQL that caused it - an
SP.

Ran the sp by hand, no messages come up - error 208 logged in the
trace.

Couldn't work it out. Then noticed stats missing on one column.
Created the stats manually - and suddenly the 208 error stops. Wtf?
Is this predicted/expected behaviour? Just me being a noob?

Thought I'd just share that. ta ;)
SQL2k, sp3a, w2k server.WangKhar (Wangkhar@.yahoo.com) writes:
> I was running a trace capturing all errors and SQL. Had a bucket of
> error 208's (invalid object name). Found the SQL that caused it - an
> SP.

Yes, this to be expected. This is because of deferred name resolution.
If the procedure creates temp tables, you'll get a lot of 208s. It could
be missing stastistics too. These are just signaled internally and inter-
cepted by some other module.

They are possibly of interest if they are causing recompiles for missing
tables, but then you should look for SP:Recompile instead.

And, true, missing statistics is another thing you could find. Then
again, with auto-statistics on, the statistics should come by time anyway.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog <sommar@.algonet.se> wrote in message
> Yes, this to be expected. This is because of deferred name resolution.

Ta.

Error 208 when updating any Stored Procedure

Hey all,
I can't update any stored procedure in my database, even as an
admin. I get:
Error 208: Invalid object name 'storedprocedurename'
Any suggestions? I've done a search on the MS knowledgebase and
google but no luck. The user can't do it and myself as an admin can't
either.
The workaround right now is to drop the proc and re-create it with the
changes.who is the owner of the sp?
"Dave" <shoad316@.hotmail.com> wrote in message
news:78cf0572.0401131336.5d46a539@.posting.google.com...
> Hey all,
> I can't update any stored procedure in my database, even as an
> admin. I get:
> Error 208: Invalid object name 'storedprocedurename'
> Any suggestions? I've done a search on the MS knowledgebase and
> google but no luck. The user can't do it and myself as an admin can't
> either.
> The workaround right now is to drop the proc and re-create it with the
> changes.|||A user is the db_owner and its the same account trying to do the update.
Thanks
--
--
david.best@.sympatico.ca
"Thanks to the remote control I have the attention span of a gerbil!"
"There are 10 types of people in the world. Those who understand binary,
and those who don't."
"NEW NAME, OLD GUY" <PLEASE!> wrote in message
news:OJF58Ui2DHA.2208@.TK2MSFTNGP12.phx.gbl...
> who is the owner of the sp?
> "Dave" <shoad316@.hotmail.com> wrote in message
> news:78cf0572.0401131336.5d46a539@.posting.google.com...
> > Hey all,
> >
> > I can't update any stored procedure in my database, even as an
> > admin. I get:
> >
> > Error 208: Invalid object name 'storedprocedurename'
> >
> > Any suggestions? I've done a search on the MS knowledgebase and
> > google but no luck. The user can't do it and myself as an admin can't
> > either.
> >
> > The workaround right now is to drop the proc and re-create it with the
> > changes.
>|||probably this should help
ALTER PROC owner_name.PROC_NAME
................
replace owner_name with the correct owner name.
"Dave Best" <david.bestNOSPAM@.sympatico.ca> wrote in message
news:RT0Nb.10886$881.1646973@.news20.bellglobal.com...
> A user is the db_owner and its the same account trying to do the update.
> Thanks
> --
> --
> david.best@.sympatico.ca
> "Thanks to the remote control I have the attention span of a gerbil!"
> "There are 10 types of people in the world. Those who understand binary,
> and those who don't."
> "NEW NAME, OLD GUY" <PLEASE!> wrote in message
> news:OJF58Ui2DHA.2208@.TK2MSFTNGP12.phx.gbl...
> > who is the owner of the sp?
> >
> > "Dave" <shoad316@.hotmail.com> wrote in message
> > news:78cf0572.0401131336.5d46a539@.posting.google.com...
> > > Hey all,
> > >
> > > I can't update any stored procedure in my database, even as an
> > > admin. I get:
> > >
> > > Error 208: Invalid object name 'storedprocedurename'
> > >
> > > Any suggestions? I've done a search on the MS knowledgebase and
> > > google but no luck. The user can't do it and myself as an admin can't
> > > either.
> > >
> > > The workaround right now is to drop the proc and re-create it with the
> > > changes.
> >
> >
>

Error 208 when updating any Stored Procedure

Hey all,
I can't update any stored procedure in my database, even as an
admin. I get:
Error 208: Invalid object name 'storedprocedurename'
Any suggestions? I've done a search on the MS knowledgebase and
google but no luck. The user can't do it and myself as an admin can't
either.
The workaround right now is to drop the proc and re-create it with the
changes.who is the owner of the sp?
"Dave" <shoad316@.hotmail.com> wrote in message
news:78cf0572.0401131336.5d46a539@.posting.google.com...

quote:

---

> Hey all,
> I can't update any stored procedure in my database, even as an
> admin. I get:
> Error 208: Invalid object name 'storedprocedurename'
> Any suggestions? I've done a search on the MS knowledgebase and
> google but no luck. The user can't do it and myself as an admin can't
> either.
> The workaround right now is to drop the proc and re-create it with the
> changes.

---

|||A user is the db_owner and its the same account trying to do the update.
Thanks
--
david.best@.sympatico.ca
"Thanks to the remote control I have the attention span of a gerbil!"
"There are 10 types of people in the world. Those who understand binary,
and those who don't."
"NEW NAME, OLD GUY" <PLEASE!> wrote in message
news:OJF58Ui2DHA.2208@.TK2MSFTNGP12.phx.gbl...

quote:

---

> who is the owner of the sp?
> "Dave" <shoad316@.hotmail.com> wrote in message
> news:78cf0572.0401131336.5d46a539@.posting.google.com...
>

---

|||probably this should help
ALTER PROC owner_name.PROC_NAME
................
replace owner_name with the correct owner name.
"Dave Best" <david.bestNOSPAM@.sympatico.ca> wrote in message
news:RT0Nb.10886$881.1646973@.news20.bellglobal.com...

quote:

---

> A user is the db_owner and its the same account trying to do the update.
> Thanks
> --
> --
> david.best@.sympatico.ca
> "Thanks to the remote control I have the attention span of a gerbil!"
> "There are 10 types of people in the world. Those who understand binary,
> and those who don't."
> "NEW NAME, OLD GUY" <PLEASE!> wrote in message
> news:OJF58Ui2DHA.2208@.TK2MSFTNGP12.phx.gbl...
>

---

Error 208 Failed to open new connection

Not sure what this means. Not much to google on it.
TITLE: Database Engine Tuning Advisor
--
Failed to open a new connection.
Invalid object name 'msdb.dbo.DTA_input'.
Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
--
Regards,
JamieHi Jamie
I believe when you first run DTA it creates a whole bunch of tables etc in
the dbo schema in MSDB. If you checked yours I expect they do not exist and
you don't have permissions to create them.
John
"thejamie" wrote:
> Not sure what this means. Not much to google on it.
> TITLE: Database Engine Tuning Advisor
> --
> Failed to open a new connection.
> Invalid object name 'msdb.dbo.DTA_input'.
> Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
>
> --
> Regards,
> Jamie|||If the sa logs in and the service user is an administrator on the machine,
these should be created, or at least I thought so. Conditions change during
an upgrade from Server advanced 2000 to an enterprise 2003 R2 64 bit server.
I expect it may have something to do with it. How can I enable the DTA to
work with the SA account? Or do I need to login as the admin to run tuning?
--
Regards,
Jamie
"John Bell" wrote:
> Hi Jamie
> I believe when you first run DTA it creates a whole bunch of tables etc in
> the dbo schema in MSDB. If you checked yours I expect they do not exist and
> you don't have permissions to create them.
> John
> "thejamie" wrote:
> > Not sure what this means. Not much to google on it.
> >
> > TITLE: Database Engine Tuning Advisor
> > --
> > Failed to open a new connection.
> >
> > Invalid object name 'msdb.dbo.DTA_input'.
> > Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> >
> > For help, click:
> > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
> >
> >
> > --
> > Regards,
> > Jamie|||The error on the server level is "DTS Design Error" "Provider not
initialized."
ErrorSource Microsoft JET Database Engine. Package was created in Windows
2000 with a reference to a Windows 97 Excel sheet. Error description The
provider is not recognizing the files on the drive.
--
Regards,
Jamie
"John Bell" wrote:
> Hi Jamie
> I believe when you first run DTA it creates a whole bunch of tables etc in
> the dbo schema in MSDB. If you checked yours I expect they do not exist and
> you don't have permissions to create them.
> John
> "thejamie" wrote:
> > Not sure what this means. Not much to google on it.
> >
> > TITLE: Database Engine Tuning Advisor
> > --
> > Failed to open a new connection.
> >
> > Invalid object name 'msdb.dbo.DTA_input'.
> > Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> >
> > For help, click:
> > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
> >
> >
> > --
> > Regards,
> > Jamie|||Hi
It could be that your 32 bit drivers have not been installed correctly, in
which case you would have other issues with 32 bit application.
It may be worthwhile running the DTA clean up script
http://support.microsoft.com/kb/899634/
John
"thejamie" wrote:
> The error on the server level is "DTS Design Error" "Provider not
> initialized."
> ErrorSource Microsoft JET Database Engine. Package was created in Windows
> 2000 with a reference to a Windows 97 Excel sheet. Error description The
> provider is not recognizing the files on the drive.
> --
> Regards,
> Jamie
>
> "John Bell" wrote:
> > Hi Jamie
> >
> > I believe when you first run DTA it creates a whole bunch of tables etc in
> > the dbo schema in MSDB. If you checked yours I expect they do not exist and
> > you don't have permissions to create them.
> >
> > John
> >
> > "thejamie" wrote:
> >
> > > Not sure what this means. Not much to google on it.
> > >
> > > TITLE: Database Engine Tuning Advisor
> > > --
> > > Failed to open a new connection.
> > >
> > > Invalid object name 'msdb.dbo.DTA_input'.
> > > Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> > >
> > > For help, click:
> > > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
> > >
> > >
> > > --
> > > Regards,
> > > Jamie|||THis script is for 2005 SQL Server. If I am running 2000, is this a good idea?
--
Regards,
Jamie
"John Bell" wrote:
> Hi
> It could be that your 32 bit drivers have not been installed correctly, in
> which case you would have other issues with 32 bit application.
> It may be worthwhile running the DTA clean up script
> http://support.microsoft.com/kb/899634/
> John
> "thejamie" wrote:
> > The error on the server level is "DTS Design Error" "Provider not
> > initialized."
> >
> > ErrorSource Microsoft JET Database Engine. Package was created in Windows
> > 2000 with a reference to a Windows 97 Excel sheet. Error description The
> > provider is not recognizing the files on the drive.
> > --
> > Regards,
> > Jamie
> >
> >
> > "John Bell" wrote:
> >
> > > Hi Jamie
> > >
> > > I believe when you first run DTA it creates a whole bunch of tables etc in
> > > the dbo schema in MSDB. If you checked yours I expect they do not exist and
> > > you don't have permissions to create them.
> > >
> > > John
> > >
> > > "thejamie" wrote:
> > >
> > > > Not sure what this means. Not much to google on it.
> > > >
> > > > TITLE: Database Engine Tuning Advisor
> > > > --
> > > > Failed to open a new connection.
> > > >
> > > > Invalid object name 'msdb.dbo.DTA_input'.
> > > > Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> > > >
> > > > For help, click:
> > > > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
> > > >
> > > >
> > > > --
> > > > Regards,
> > > > Jamie|||Hi
DTA is only on SQL 2005 ITW was on SQL 2000!
John
"thejamie" wrote:
> THis script is for 2005 SQL Server. If I am running 2000, is this a good idea?
> --
> Regards,
> Jamie
>
> "John Bell" wrote:
> > Hi
> >
> > It could be that your 32 bit drivers have not been installed correctly, in
> > which case you would have other issues with 32 bit application.
> >
> > It may be worthwhile running the DTA clean up script
> > http://support.microsoft.com/kb/899634/
> >
> > John
> >
> > "thejamie" wrote:
> >
> > > The error on the server level is "DTS Design Error" "Provider not
> > > initialized."
> > >
> > > ErrorSource Microsoft JET Database Engine. Package was created in Windows
> > > 2000 with a reference to a Windows 97 Excel sheet. Error description The
> > > provider is not recognizing the files on the drive.
> > > --
> > > Regards,
> > > Jamie
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi Jamie
> > > >
> > > > I believe when you first run DTA it creates a whole bunch of tables etc in
> > > > the dbo schema in MSDB. If you checked yours I expect they do not exist and
> > > > you don't have permissions to create them.
> > > >
> > > > John
> > > >
> > > > "thejamie" wrote:
> > > >
> > > > > Not sure what this means. Not much to google on it.
> > > > >
> > > > > TITLE: Database Engine Tuning Advisor
> > > > > --
> > > > > Failed to open a new connection.
> > > > >
> > > > > Invalid object name 'msdb.dbo.DTA_input'.
> > > > > Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> > > > >
> > > > > For help, click:
> > > > > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
> > > > >
> > > > >
> > > > > --
> > > > > Regards,
> > > > > Jamie|||Maybe this is why the error is confusing me. If there is no DTA on 2000, I
wonder why it would ask for it. Is the office installation required for the
MAPI client? The network administrator had to install an office client for
the MAPI. Would the version of JET be affected?
--
Regards,
Jamie
"John Bell" wrote:
> Hi
> DTA is only on SQL 2005 ITW was on SQL 2000!
> John
> "thejamie" wrote:
> > THis script is for 2005 SQL Server. If I am running 2000, is this a good idea?
> > --
> > Regards,
> > Jamie
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > It could be that your 32 bit drivers have not been installed correctly, in
> > > which case you would have other issues with 32 bit application.
> > >
> > > It may be worthwhile running the DTA clean up script
> > > http://support.microsoft.com/kb/899634/
> > >
> > > John
> > >
> > > "thejamie" wrote:
> > >
> > > > The error on the server level is "DTS Design Error" "Provider not
> > > > initialized."
> > > >
> > > > ErrorSource Microsoft JET Database Engine. Package was created in Windows
> > > > 2000 with a reference to a Windows 97 Excel sheet. Error description The
> > > > provider is not recognizing the files on the drive.
> > > > --
> > > > Regards,
> > > > Jamie
> > > >
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi Jamie
> > > > >
> > > > > I believe when you first run DTA it creates a whole bunch of tables etc in
> > > > > the dbo schema in MSDB. If you checked yours I expect they do not exist and
> > > > > you don't have permissions to create them.
> > > > >
> > > > > John
> > > > >
> > > > > "thejamie" wrote:
> > > > >
> > > > > > Not sure what this means. Not much to google on it.
> > > > > >
> > > > > > TITLE: Database Engine Tuning Advisor
> > > > > > --
> > > > > > Failed to open a new connection.
> > > > > >
> > > > > > Invalid object name 'msdb.dbo.DTA_input'.
> > > > > > Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> > > > > >
> > > > > > For help, click:
> > > > > > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Regards,
> > > > > > Jamie|||Hi
I am not longer clear what you are trying to do when you get this error!
SQLMail for SQL 2000 required the MAPI DLLs which you can only legitimately
install with a version of outlook. There are 3rd party XPs that use SMTP the
most common being http://www.sqldev.net/xp/xpsmtp.htm, but you would have to
use the XPs rather than the SQLMail procs.
John
"thejamie" wrote:
> Maybe this is why the error is confusing me. If there is no DTA on 2000, I
> wonder why it would ask for it. Is the office installation required for the
> MAPI client? The network administrator had to install an office client for
> the MAPI. Would the version of JET be affected?
> --
> Regards,
> Jamie
>
> "John Bell" wrote:
> > Hi
> >
> > DTA is only on SQL 2005 ITW was on SQL 2000!
> >
> > John
> >
> > "thejamie" wrote:
> >
> > > THis script is for 2005 SQL Server. If I am running 2000, is this a good idea?
> > > --
> > > Regards,
> > > Jamie
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > It could be that your 32 bit drivers have not been installed correctly, in
> > > > which case you would have other issues with 32 bit application.
> > > >
> > > > It may be worthwhile running the DTA clean up script
> > > > http://support.microsoft.com/kb/899634/
> > > >
> > > > John
> > > >
> > > > "thejamie" wrote:
> > > >
> > > > > The error on the server level is "DTS Design Error" "Provider not
> > > > > initialized."
> > > > >
> > > > > ErrorSource Microsoft JET Database Engine. Package was created in Windows
> > > > > 2000 with a reference to a Windows 97 Excel sheet. Error description The
> > > > > provider is not recognizing the files on the drive.
> > > > > --
> > > > > Regards,
> > > > > Jamie
> > > > >
> > > > >
> > > > > "John Bell" wrote:
> > > > >
> > > > > > Hi Jamie
> > > > > >
> > > > > > I believe when you first run DTA it creates a whole bunch of tables etc in
> > > > > > the dbo schema in MSDB. If you checked yours I expect they do not exist and
> > > > > > you don't have permissions to create them.
> > > > > >
> > > > > > John
> > > > > >
> > > > > > "thejamie" wrote:
> > > > > >
> > > > > > > Not sure what this means. Not much to google on it.
> > > > > > >
> > > > > > > TITLE: Database Engine Tuning Advisor
> > > > > > > --
> > > > > > > Failed to open a new connection.
> > > > > > >
> > > > > > > Invalid object name 'msdb.dbo.DTA_input'.
> > > > > > > Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> > > > > > >
> > > > > > > For help, click:
> > > > > > > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Regards,
> > > > > > > Jamie|||Clarity is where I am lacking as well. These errors occur when I open the
DTS design package and attempt to look at the jobs (SQL Server 2000). I
could not find information on the error. You have referred me to a DTA fix,
but as I understand it, on SQL 2000 I am running ITW. I am still not sure
what the 208 error is. Since the fix for DTA is SQL 2005, I am hesitant to
run it. In our last meeting for IT, we discussed whether to downgrade the
Enterprise 64 bit server to 32 bit and rebuild the SQL Server again, or
whether to move to a 64 bit SQL 2005 server.
Is there a strong possibility that these issues will not stop and that there
is no resolution going forward with SQL 2000 on 64 bit? We know it is not
recommended.
But if I can solve the DTA issue temporarily, how would I approach the DTA
issue?
--
Regards,
Jamie
"John Bell" wrote:
> Hi
> I am not longer clear what you are trying to do when you get this error!
> SQLMail for SQL 2000 required the MAPI DLLs which you can only legitimately
> install with a version of outlook. There are 3rd party XPs that use SMTP the
> most common being http://www.sqldev.net/xp/xpsmtp.htm, but you would have to
> use the XPs rather than the SQLMail procs.
> John
> "thejamie" wrote:
> > Maybe this is why the error is confusing me. If there is no DTA on 2000, I
> > wonder why it would ask for it. Is the office installation required for the
> > MAPI client? The network administrator had to install an office client for
> > the MAPI. Would the version of JET be affected?
> > --
> > Regards,
> > Jamie
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > DTA is only on SQL 2005 ITW was on SQL 2000!
> > >
> > > John
> > >
> > > "thejamie" wrote:
> > >
> > > > THis script is for 2005 SQL Server. If I am running 2000, is this a good idea?
> > > > --
> > > > Regards,
> > > > Jamie
> > > >
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > It could be that your 32 bit drivers have not been installed correctly, in
> > > > > which case you would have other issues with 32 bit application.
> > > > >
> > > > > It may be worthwhile running the DTA clean up script
> > > > > http://support.microsoft.com/kb/899634/
> > > > >
> > > > > John
> > > > >
> > > > > "thejamie" wrote:
> > > > >
> > > > > > The error on the server level is "DTS Design Error" "Provider not
> > > > > > initialized."
> > > > > >
> > > > > > ErrorSource Microsoft JET Database Engine. Package was created in Windows
> > > > > > 2000 with a reference to a Windows 97 Excel sheet. Error description The
> > > > > > provider is not recognizing the files on the drive.
> > > > > > --
> > > > > > Regards,
> > > > > > Jamie
> > > > > >
> > > > > >
> > > > > > "John Bell" wrote:
> > > > > >
> > > > > > > Hi Jamie
> > > > > > >
> > > > > > > I believe when you first run DTA it creates a whole bunch of tables etc in
> > > > > > > the dbo schema in MSDB. If you checked yours I expect they do not exist and
> > > > > > > you don't have permissions to create them.
> > > > > > >
> > > > > > > John
> > > > > > >
> > > > > > > "thejamie" wrote:
> > > > > > >
> > > > > > > > Not sure what this means. Not much to google on it.
> > > > > > > >
> > > > > > > > TITLE: Database Engine Tuning Advisor
> > > > > > > > --
> > > > > > > > Failed to open a new connection.
> > > > > > > >
> > > > > > > > Invalid object name 'msdb.dbo.DTA_input'.
> > > > > > > > Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> > > > > > > >
> > > > > > > > For help, click:
> > > > > > > > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Regards,
> > > > > > > > Jamie|||Hi
I think the DTA thing is a red herring, you posted something from the
newsgroup that was having a error 208. This error is generic "Invalid object
name '%.*ls'"
You would need to know what object it is trying to access. Have you checked
the SQL Server Log or Windows Event Log? If nothing is in there use SQL
Profile and monitor the events Exceptions and also Execution Warnings (from
Errors and Warnings) with DatabaseId, ObjectId and EventSubClass
John
"thejamie" wrote:
> Clarity is where I am lacking as well. These errors occur when I open the
> DTS design package and attempt to look at the jobs (SQL Server 2000). I
> could not find information on the error. You have referred me to a DTA fix,
> but as I understand it, on SQL 2000 I am running ITW. I am still not sure
> what the 208 error is. Since the fix for DTA is SQL 2005, I am hesitant to
> run it. In our last meeting for IT, we discussed whether to downgrade the
> Enterprise 64 bit server to 32 bit and rebuild the SQL Server again, or
> whether to move to a 64 bit SQL 2005 server.
> Is there a strong possibility that these issues will not stop and that there
> is no resolution going forward with SQL 2000 on 64 bit? We know it is not
> recommended.
> But if I can solve the DTA issue temporarily, how would I approach the DTA
> issue?
> --
> Regards,
> Jamie
>
> "John Bell" wrote:
> > Hi
> >
> > I am not longer clear what you are trying to do when you get this error!
> >
> > SQLMail for SQL 2000 required the MAPI DLLs which you can only legitimately
> > install with a version of outlook. There are 3rd party XPs that use SMTP the
> > most common being http://www.sqldev.net/xp/xpsmtp.htm, but you would have to
> > use the XPs rather than the SQLMail procs.
> >
> > John
> >
> > "thejamie" wrote:
> >
> > > Maybe this is why the error is confusing me. If there is no DTA on 2000, I
> > > wonder why it would ask for it. Is the office installation required for the
> > > MAPI client? The network administrator had to install an office client for
> > > the MAPI. Would the version of JET be affected?
> > > --
> > > Regards,
> > > Jamie
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > DTA is only on SQL 2005 ITW was on SQL 2000!
> > > >
> > > > John
> > > >
> > > > "thejamie" wrote:
> > > >
> > > > > THis script is for 2005 SQL Server. If I am running 2000, is this a good idea?
> > > > > --
> > > > > Regards,
> > > > > Jamie
> > > > >
> > > > >
> > > > > "John Bell" wrote:
> > > > >
> > > > > > Hi
> > > > > >
> > > > > > It could be that your 32 bit drivers have not been installed correctly, in
> > > > > > which case you would have other issues with 32 bit application.
> > > > > >
> > > > > > It may be worthwhile running the DTA clean up script
> > > > > > http://support.microsoft.com/kb/899634/
> > > > > >
> > > > > > John
> > > > > >
> > > > > > "thejamie" wrote:
> > > > > >
> > > > > > > The error on the server level is "DTS Design Error" "Provider not
> > > > > > > initialized."
> > > > > > >
> > > > > > > ErrorSource Microsoft JET Database Engine. Package was created in Windows
> > > > > > > 2000 with a reference to a Windows 97 Excel sheet. Error description The
> > > > > > > provider is not recognizing the files on the drive.
> > > > > > > --
> > > > > > > Regards,
> > > > > > > Jamie
> > > > > > >
> > > > > > >
> > > > > > > "John Bell" wrote:
> > > > > > >
> > > > > > > > Hi Jamie
> > > > > > > >
> > > > > > > > I believe when you first run DTA it creates a whole bunch of tables etc in
> > > > > > > > the dbo schema in MSDB. If you checked yours I expect they do not exist and
> > > > > > > > you don't have permissions to create them.
> > > > > > > >
> > > > > > > > John
> > > > > > > >
> > > > > > > > "thejamie" wrote:
> > > > > > > >
> > > > > > > > > Not sure what this means. Not much to google on it.
> > > > > > > > >
> > > > > > > > > TITLE: Database Engine Tuning Advisor
> > > > > > > > > --
> > > > > > > > > Failed to open a new connection.
> > > > > > > > >
> > > > > > > > > Invalid object name 'msdb.dbo.DTA_input'.
> > > > > > > > > Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> > > > > > > > >
> > > > > > > > > For help, click:
> > > > > > > > > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Regards,
> > > > > > > > > Jamie|||Your help and a reboot put us back in business. Thanks.
--
Regards,
Jamie
"John Bell" wrote:
> Hi
> It could be that your 32 bit drivers have not been installed correctly, in
> which case you would have other issues with 32 bit application.
> It may be worthwhile running the DTA clean up script
> http://support.microsoft.com/kb/899634/
> John
> "thejamie" wrote:
> > The error on the server level is "DTS Design Error" "Provider not
> > initialized."
> >
> > ErrorSource Microsoft JET Database Engine. Package was created in Windows
> > 2000 with a reference to a Windows 97 Excel sheet. Error description The
> > provider is not recognizing the files on the drive.
> > --
> > Regards,
> > Jamie
> >
> >
> > "John Bell" wrote:
> >
> > > Hi Jamie
> > >
> > > I believe when you first run DTA it creates a whole bunch of tables etc in
> > > the dbo schema in MSDB. If you checked yours I expect they do not exist and
> > > you don't have permissions to create them.
> > >
> > > John
> > >
> > > "thejamie" wrote:
> > >
> > > > Not sure what this means. Not much to google on it.
> > > >
> > > > TITLE: Database Engine Tuning Advisor
> > > > --
> > > > Failed to open a new connection.
> > > >
> > > > Invalid object name 'msdb.dbo.DTA_input'.
> > > > Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> > > >
> > > > For help, click:
> > > > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
> > > >
> > > >
> > > > --
> > > > Regards,
> > > > Jamie|||Not sure what I contributed! Did you find out what was missing?
John
"thejamie" wrote:
> Your help and a reboot put us back in business. Thanks.
> --
> Regards,
> Jamie
>
> "John Bell" wrote:
> > Hi
> >
> > It could be that your 32 bit drivers have not been installed correctly, in
> > which case you would have other issues with 32 bit application.
> >
> > It may be worthwhile running the DTA clean up script
> > http://support.microsoft.com/kb/899634/
> >
> > John
> >
> > "thejamie" wrote:
> >
> > > The error on the server level is "DTS Design Error" "Provider not
> > > initialized."
> > >
> > > ErrorSource Microsoft JET Database Engine. Package was created in Windows
> > > 2000 with a reference to a Windows 97 Excel sheet. Error description The
> > > provider is not recognizing the files on the drive.
> > > --
> > > Regards,
> > > Jamie
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi Jamie
> > > >
> > > > I believe when you first run DTA it creates a whole bunch of tables etc in
> > > > the dbo schema in MSDB. If you checked yours I expect they do not exist and
> > > > you don't have permissions to create them.
> > > >
> > > > John
> > > >
> > > > "thejamie" wrote:
> > > >
> > > > > Not sure what this means. Not much to google on it.
> > > > >
> > > > > TITLE: Database Engine Tuning Advisor
> > > > > --
> > > > > Failed to open a new connection.
> > > > >
> > > > > Invalid object name 'msdb.dbo.DTA_input'.
> > > > > Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> > > > >
> > > > > For help, click:
> > > > > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
> > > > >
> > > > >
> > > > > --
> > > > > Regards,
> > > > > Jamie|||I think you are right about the red herring. There is definitely an issue
here due to the 64 bit Enterprise server running SQL 2000 Std... we can't get
DTS to run the older OLE Excel when it is used in a package. I suspect but
did not isolate the cause but suspect the security is tighter on the 64 bit
servers. The 64 bit server has other surprises - if you set up a new one the
64 bit servers that are already in the network quarantine it until after they
are rebooted. The 64 bit machine requires that security be altered on the
temp directory profile of the service account if you want the SQLAgent to
kick off email for anyone except the admin accounts (this includes sa).
All this - running a Std 2000 SQL package. We must upgrade to SQL 2005 64
bit. As far as the DTS is concerned, I don't think there is a fix.
--
Regards,
Jamie
"John Bell" wrote:
> Not sure what I contributed! Did you find out what was missing?
> John
> "thejamie" wrote:
> > Your help and a reboot put us back in business. Thanks.
> > --
> > Regards,
> > Jamie
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > It could be that your 32 bit drivers have not been installed correctly, in
> > > which case you would have other issues with 32 bit application.
> > >
> > > It may be worthwhile running the DTA clean up script
> > > http://support.microsoft.com/kb/899634/
> > >
> > > John
> > >
> > > "thejamie" wrote:
> > >
> > > > The error on the server level is "DTS Design Error" "Provider not
> > > > initialized."
> > > >
> > > > ErrorSource Microsoft JET Database Engine. Package was created in Windows
> > > > 2000 with a reference to a Windows 97 Excel sheet. Error description The
> > > > provider is not recognizing the files on the drive.
> > > > --
> > > > Regards,
> > > > Jamie
> > > >
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi Jamie
> > > > >
> > > > > I believe when you first run DTA it creates a whole bunch of tables etc in
> > > > > the dbo schema in MSDB. If you checked yours I expect they do not exist and
> > > > > you don't have permissions to create them.
> > > > >
> > > > > John
> > > > >
> > > > > "thejamie" wrote:
> > > > >
> > > > > > Not sure what this means. Not much to google on it.
> > > > > >
> > > > > > TITLE: Database Engine Tuning Advisor
> > > > > > --
> > > > > > Failed to open a new connection.
> > > > > >
> > > > > > Invalid object name 'msdb.dbo.DTA_input'.
> > > > > > Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> > > > > >
> > > > > > For help, click:
> > > > > > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Regards,
> > > > > > Jamie|||Hi
Have you tried creating a new package with an excel data source?
Moving to SQL 2005 you should be using the benefits of SSIS.
John
"thejamie" wrote:
> I think you are right about the red herring. There is definitely an issue
> here due to the 64 bit Enterprise server running SQL 2000 Std... we can't get
> DTS to run the older OLE Excel when it is used in a package. I suspect but
> did not isolate the cause but suspect the security is tighter on the 64 bit
> servers. The 64 bit server has other surprises - if you set up a new one the
> 64 bit servers that are already in the network quarantine it until after they
> are rebooted. The 64 bit machine requires that security be altered on the
> temp directory profile of the service account if you want the SQLAgent to
> kick off email for anyone except the admin accounts (this includes sa).
> All this - running a Std 2000 SQL package. We must upgrade to SQL 2005 64
> bit. As far as the DTS is concerned, I don't think there is a fix.
> --
> Regards,
> Jamie
>
> "John Bell" wrote:
> > Not sure what I contributed! Did you find out what was missing?
> >
> > John
> >
> > "thejamie" wrote:
> >
> > > Your help and a reboot put us back in business. Thanks.
> > > --
> > > Regards,
> > > Jamie
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > It could be that your 32 bit drivers have not been installed correctly, in
> > > > which case you would have other issues with 32 bit application.
> > > >
> > > > It may be worthwhile running the DTA clean up script
> > > > http://support.microsoft.com/kb/899634/
> > > >
> > > > John
> > > >
> > > > "thejamie" wrote:
> > > >
> > > > > The error on the server level is "DTS Design Error" "Provider not
> > > > > initialized."
> > > > >
> > > > > ErrorSource Microsoft JET Database Engine. Package was created in Windows
> > > > > 2000 with a reference to a Windows 97 Excel sheet. Error description The
> > > > > provider is not recognizing the files on the drive.
> > > > > --
> > > > > Regards,
> > > > > Jamie
> > > > >
> > > > >
> > > > > "John Bell" wrote:
> > > > >
> > > > > > Hi Jamie
> > > > > >
> > > > > > I believe when you first run DTA it creates a whole bunch of tables etc in
> > > > > > the dbo schema in MSDB. If you checked yours I expect they do not exist and
> > > > > > you don't have permissions to create them.
> > > > > >
> > > > > > John
> > > > > >
> > > > > > "thejamie" wrote:
> > > > > >
> > > > > > > Not sure what this means. Not much to google on it.
> > > > > > >
> > > > > > > TITLE: Database Engine Tuning Advisor
> > > > > > > --
> > > > > > > Failed to open a new connection.
> > > > > > >
> > > > > > > Invalid object name 'msdb.dbo.DTA_input'.
> > > > > > > Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> > > > > > >
> > > > > > > For help, click:
> > > > > > > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Regards,
> > > > > > > Jamie|||The 208 message is a red-herring. That was as good an answer as I might
expect. As far as running a 32 bit SQL 2000 Std version on a 64 bit
Enterprise 2003 R2, the jury is still out but we have stablized and the
system appears solid. I hate to say it for sure because that'll jinx it.
Around here it is sometimes hard to distinguish what is a programming error
on our part versus what is bad data causing failures internally. It is
extremely difficult to predict what surprises will come through on our EDI
system. Other than the Excel blip - which might be something as simple as
group policy, the system in general, including linked servers, MCI
connections, routers, nic cards, jobs, dts packages, logins, moving
databases, tcp/ip aliasing... this part has been relatively smooth. There
were some rough spots that were only resolved by server reboots. As my
supervisor stated returning from the warehouse "No bullet holes... that's a
good thing."
I've yet to try to put together an Excel package with SSIS.
Regards,
Jamie
"John Bell" wrote:
> Not sure what I contributed! Did you find out what was missing?
> John
> "thejamie" wrote:
> > Your help and a reboot put us back in business. Thanks.
> > --
> > Regards,
> > Jamie
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > It could be that your 32 bit drivers have not been installed correctly, in
> > > which case you would have other issues with 32 bit application.
> > >
> > > It may be worthwhile running the DTA clean up script
> > > http://support.microsoft.com/kb/899634/
> > >
> > > John
> > >
> > > "thejamie" wrote:
> > >
> > > > The error on the server level is "DTS Design Error" "Provider not
> > > > initialized."
> > > >
> > > > ErrorSource Microsoft JET Database Engine. Package was created in Windows
> > > > 2000 with a reference to a Windows 97 Excel sheet. Error description The
> > > > provider is not recognizing the files on the drive.
> > > > --
> > > > Regards,
> > > > Jamie
> > > >
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi Jamie
> > > > >
> > > > > I believe when you first run DTA it creates a whole bunch of tables etc in
> > > > > the dbo schema in MSDB. If you checked yours I expect they do not exist and
> > > > > you don't have permissions to create them.
> > > > >
> > > > > John
> > > > >
> > > > > "thejamie" wrote:
> > > > >
> > > > > > Not sure what this means. Not much to google on it.
> > > > > >
> > > > > > TITLE: Database Engine Tuning Advisor
> > > > > > --
> > > > > > Failed to open a new connection.
> > > > > >
> > > > > > Invalid object name 'msdb.dbo.DTA_input'.
> > > > > > Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> > > > > >
> > > > > > For help, click:
> > > > > > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Regards,
> > > > > > Jamie|||I'm actually still stumbling with one of the issues.
Example:
A query that uses an absolute reference to a server over a linked server...
Select * from servera.database1.dbo.table where mycolumn='xyz'
will pretty much give instant results whereas
Declare @.var varchar(25)
set @.var='xyz'
select * from servera.database1.dbo.table where mycolumn=@.var
takes forever and ever and there is no error message - just a huge delay for
the data to relay. I tried creating a role with permission to
(select,update,delete,insert,execute,references) all tables, all views, all
procs and all functions and adding the domain users to the role. This does
not work to make the query any faster.
The example above takes about 8 minutes to process with the variable less
than one second to process.
What is the difference?
--
Regards,
Jamie
"John Bell" wrote:
> Not sure what I contributed! Did you find out what was missing?
> John
> "thejamie" wrote:
> > Your help and a reboot put us back in business. Thanks.
> > --
> > Regards,
> > Jamie
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > It could be that your 32 bit drivers have not been installed correctly, in
> > > which case you would have other issues with 32 bit application.
> > >
> > > It may be worthwhile running the DTA clean up script
> > > http://support.microsoft.com/kb/899634/
> > >
> > > John
> > >
> > > "thejamie" wrote:
> > >
> > > > The error on the server level is "DTS Design Error" "Provider not
> > > > initialized."
> > > >
> > > > ErrorSource Microsoft JET Database Engine. Package was created in Windows
> > > > 2000 with a reference to a Windows 97 Excel sheet. Error description The
> > > > provider is not recognizing the files on the drive.
> > > > --
> > > > Regards,
> > > > Jamie
> > > >
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi Jamie
> > > > >
> > > > > I believe when you first run DTA it creates a whole bunch of tables etc in
> > > > > the dbo schema in MSDB. If you checked yours I expect they do not exist and
> > > > > you don't have permissions to create them.
> > > > >
> > > > > John
> > > > >
> > > > > "thejamie" wrote:
> > > > >
> > > > > > Not sure what this means. Not much to google on it.
> > > > > >
> > > > > > TITLE: Database Engine Tuning Advisor
> > > > > > --
> > > > > > Failed to open a new connection.
> > > > > >
> > > > > > Invalid object name 'msdb.dbo.DTA_input'.
> > > > > > Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> > > > > >
> > > > > > For help, click:
> > > > > > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Regards,
> > > > > > Jamie|||Here is the answer to the Error 208 failed to open connection
A DTS package can be saved on the 64-bit server, and a DTS package can be
run against a SQL Server 2000 (64-bit) dataset, but the package must run from
a 32-bit machine that is set up with SQL Server 2000 tools.
http://www.sqlservercentral.com/articles/Miscellaneous/overviewof64bitsql/1166/
--
Regards,
Jamie
"John Bell" wrote:
> Hi
> Have you tried creating a new package with an excel data source?
> Moving to SQL 2005 you should be using the benefits of SSIS.
> John
> "thejamie" wrote:
> > I think you are right about the red herring. There is definitely an issue
> > here due to the 64 bit Enterprise server running SQL 2000 Std... we can't get
> > DTS to run the older OLE Excel when it is used in a package. I suspect but
> > did not isolate the cause but suspect the security is tighter on the 64 bit
> > servers. The 64 bit server has other surprises - if you set up a new one the
> > 64 bit servers that are already in the network quarantine it until after they
> > are rebooted. The 64 bit machine requires that security be altered on the
> > temp directory profile of the service account if you want the SQLAgent to
> > kick off email for anyone except the admin accounts (this includes sa).
> >
> > All this - running a Std 2000 SQL package. We must upgrade to SQL 2005 64
> > bit. As far as the DTS is concerned, I don't think there is a fix.
> > --
> > Regards,
> > Jamie
> >
> >
> > "John Bell" wrote:
> >
> > > Not sure what I contributed! Did you find out what was missing?
> > >
> > > John
> > >
> > > "thejamie" wrote:
> > >
> > > > Your help and a reboot put us back in business. Thanks.
> > > > --
> > > > Regards,
> > > > Jamie
> > > >
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > It could be that your 32 bit drivers have not been installed correctly, in
> > > > > which case you would have other issues with 32 bit application.
> > > > >
> > > > > It may be worthwhile running the DTA clean up script
> > > > > http://support.microsoft.com/kb/899634/
> > > > >
> > > > > John
> > > > >
> > > > > "thejamie" wrote:
> > > > >
> > > > > > The error on the server level is "DTS Design Error" "Provider not
> > > > > > initialized."
> > > > > >
> > > > > > ErrorSource Microsoft JET Database Engine. Package was created in Windows
> > > > > > 2000 with a reference to a Windows 97 Excel sheet. Error description The
> > > > > > provider is not recognizing the files on the drive.
> > > > > > --
> > > > > > Regards,
> > > > > > Jamie
> > > > > >
> > > > > >
> > > > > > "John Bell" wrote:
> > > > > >
> > > > > > > Hi Jamie
> > > > > > >
> > > > > > > I believe when you first run DTA it creates a whole bunch of tables etc in
> > > > > > > the dbo schema in MSDB. If you checked yours I expect they do not exist and
> > > > > > > you don't have permissions to create them.
> > > > > > >
> > > > > > > John
> > > > > > >
> > > > > > > "thejamie" wrote:
> > > > > > >
> > > > > > > > Not sure what this means. Not much to google on it.
> > > > > > > >
> > > > > > > > TITLE: Database Engine Tuning Advisor
> > > > > > > > --
> > > > > > > > Failed to open a new connection.
> > > > > > > >
> > > > > > > > Invalid object name 'msdb.dbo.DTA_input'.
> > > > > > > > Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> > > > > > > >
> > > > > > > > For help, click:
> > > > > > > > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Regards,
> > > > > > > > Jamie|||Hi
This may be something to do with where the filter is applied, check out the
query plans to see the difference. To get around this you could use EXEC or
OPENQUERY and concatenate the value
John
"thejamie" wrote:
> I'm actually still stumbling with one of the issues.
> Example:
> A query that uses an absolute reference to a server over a linked server...
> Select * from servera.database1.dbo.table where mycolumn='xyz'
> will pretty much give instant results whereas
> Declare @.var varchar(25)
> set @.var='xyz'
> select * from servera.database1.dbo.table where mycolumn=@.var
> takes forever and ever and there is no error message - just a huge delay for
> the data to relay. I tried creating a role with permission to
> (select,update,delete,insert,execute,references) all tables, all views, all
> procs and all functions and adding the domain users to the role. This does
> not work to make the query any faster.
> The example above takes about 8 minutes to process with the variable less
> than one second to process.
> What is the difference?
> --
> Regards,
> Jamie
>
> "John Bell" wrote:
> > Not sure what I contributed! Did you find out what was missing?
> >
> > John
> >
> > "thejamie" wrote:
> >
> > > Your help and a reboot put us back in business. Thanks.
> > > --
> > > Regards,
> > > Jamie
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > It could be that your 32 bit drivers have not been installed correctly, in
> > > > which case you would have other issues with 32 bit application.
> > > >
> > > > It may be worthwhile running the DTA clean up script
> > > > http://support.microsoft.com/kb/899634/
> > > >
> > > > John
> > > >
> > > > "thejamie" wrote:
> > > >
> > > > > The error on the server level is "DTS Design Error" "Provider not
> > > > > initialized."
> > > > >
> > > > > ErrorSource Microsoft JET Database Engine. Package was created in Windows
> > > > > 2000 with a reference to a Windows 97 Excel sheet. Error description The
> > > > > provider is not recognizing the files on the drive.
> > > > > --
> > > > > Regards,
> > > > > Jamie
> > > > >
> > > > >
> > > > > "John Bell" wrote:
> > > > >
> > > > > > Hi Jamie
> > > > > >
> > > > > > I believe when you first run DTA it creates a whole bunch of tables etc in
> > > > > > the dbo schema in MSDB. If you checked yours I expect they do not exist and
> > > > > > you don't have permissions to create them.
> > > > > >
> > > > > > John
> > > > > >
> > > > > > "thejamie" wrote:
> > > > > >
> > > > > > > Not sure what this means. Not much to google on it.
> > > > > > >
> > > > > > > TITLE: Database Engine Tuning Advisor
> > > > > > > --
> > > > > > > Failed to open a new connection.
> > > > > > >
> > > > > > > Invalid object name 'msdb.dbo.DTA_input'.
> > > > > > > Invalid object name 'msdb.dbo.DTA_output'. (Microsoft SQL Server, Error: 208)
> > > > > > >
> > > > > > > For help, click:
> > > > > > > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=208&LinkId=20476
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Regards,
> > > > > > > Jamie

error 207 when trying to add a new job

when trying to add a new job via sql agent server, receiving a message:
"error sqlstate: 42s33"
error 207: invalid column name 'category_id'
invalid column name 'netsend_address'
invalid column name 'last_netsend_date'
invalid column name 'last_netsend_time.
Hi,
Did you upgraded your SQL server from older version. If yes then the MSDB
upgrade was not done fully. See the below old post for the step by step
solution.
http://groups.google.com/groups?hl=e...lm=0TDE0%23ZdB
HA.187%40cppssbbsa01.microsoft.com
Thanks
Hari
MCDBA
"ed" <ed@.discussions.microsoft.com> wrote in message
news:99EECA57-E7CC-4F36-A248-F97616029E50@.microsoft.com...
> when trying to add a new job via sql agent server, receiving a message:
> "error sqlstate: 42s33"
> error 207: invalid column name 'category_id'
> invalid column name 'netsend_address'
> invalid column name 'last_netsend_date'
> invalid column name 'last_netsend_time.
|||Hi
-As per SQL Server Books Online "This error (error 207) occurs when a column
referenced in a Transact-SQL statement was not found in any table specified
in
the FROM clause of the query.
-Table msdb..sysoperators didn't have the following columns 'category_id', '
netsend_address',' last_netsend_date',' last_netsend_time'
Looks like some problem with MSDB, try and rebuild as suggested in previous
post.
HTH
Regards
Sadeesh
This posting is provided AS IS with no warranties, and confers no rights.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:OBuR4L6cEHA.3512@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Did you upgraded your SQL server from older version. If yes then the MSDB
> upgrade was not done fully. See the below old post for the step by step
> solution.
>
> http://groups.google.com/groups?hl=e...lm=0TDE0%23ZdB
> HA.187%40cppssbbsa01.microsoft.com
> Thanks
> Hari
> MCDBA
> "ed" <ed@.discussions.microsoft.com> wrote in message
> news:99EECA57-E7CC-4F36-A248-F97616029E50@.microsoft.com...
>

error 207 when trying to add a new job

when trying to add a new job via sql agent server, receiving a message:
"error sqlstate: 42s33"
error 207: invalid column name 'category_id'
invalid column name 'netsend_address'
invalid column name 'last_netsend_date'
invalid column name 'last_netsend_time.Hi,
Did you upgraded your SQL server from older version. If yes then the MSDB
upgrade was not done fully. See the below old post for the step by step
solution.
http://groups.google.com/groups?hl=...elm=0TDE0%23ZdB
HA.187%40cppssbbsa01.microsoft.com
Thanks
Hari
MCDBA
"ed" <ed@.discussions.microsoft.com> wrote in message
news:99EECA57-E7CC-4F36-A248-F97616029E50@.microsoft.com...
> when trying to add a new job via sql agent server, receiving a message:
> "error sqlstate: 42s33"
> error 207: invalid column name 'category_id'
> invalid column name 'netsend_address'
> invalid column name 'last_netsend_date'
> invalid column name 'last_netsend_time.|||Hi
-As per SQL Server Books Online "This error (error 207) occurs when a column
referenced in a Transact-SQL statement was not found in any table specified
in
the FROM clause of the query.
-Table msdb..sysoperators didn't have the following columns 'category_id', '
netsend_address',' last_netsend_date',' last_netsend_time'
Looks like some problem with MSDB, try and rebuild as suggested in previous
post.
HTH
Regards
Sadeesh
--
This posting is provided AS IS with no warranties, and confers no rights.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:OBuR4L6cEHA.3512@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Did you upgraded your SQL server from older version. If yes then the MSDB
> upgrade was not done fully. See the below old post for the step by step
> solution.
>
> [url]http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=0TDE0%23ZdB[/ur
l]
> HA.187%40cppssbbsa01.microsoft.com
> Thanks
> Hari
> MCDBA
> "ed" <ed@.discussions.microsoft.com> wrote in message
> news:99EECA57-E7CC-4F36-A248-F97616029E50@.microsoft.com...
>|||hi,
i didn't upgrage but i restored msdb from backup and it was ok.
thanks.
"Hari Prasad" wrote:

> Hi,
> Did you upgraded your SQL server from older version. If yes then the MSDB
> upgrade was not done fully. See the below old post for the step by step
> solution.
>
> [url]http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=0TDE0%23ZdB[/ur
l]
> HA.187%40cppssbbsa01.microsoft.com
> Thanks
> Hari
> MCDBA
> "ed" <ed@.discussions.microsoft.com> wrote in message
> news:99EECA57-E7CC-4F36-A248-F97616029E50@.microsoft.com...
>
>|||yep some of the columns were missing from the system tables in msdb? resto
red msdb from an old backup.
thanks for your help.
"Sadeesh[MSFT]" wrote:

> Hi
> -As per SQL Server Books Online "This error (error 207) occurs when a colu
mn
> referenced in a Transact-SQL statement was not found in any table specifie
d
> in
> the FROM clause of the query.
> -Table msdb..sysoperators didn't have the following columns 'category_id',
'
> netsend_address',' last_netsend_date',' last_netsend_time'
> Looks like some problem with MSDB, try and rebuild as suggested in previou
s
> post.
> HTH
> Regards
> Sadeesh
> --
> This posting is provided AS IS with no warranties, and confers no rights.
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:OBuR4L6cEHA.3512@.TK2MSFTNGP12.phx.gbl...
>
>

Error 207

Hi everyone,
I am trying to create a Transactional Pull Subscription=20
but I get an error 207 : Invalid column=20
name "enabled_for_syncmgr"
Invalid columnname "alt_snapshot_folder"
Invalid columnname "dts_package_name".
Both The Publication and Subscriber databases are SQL=20
Server 7 backups restored on a SQL Server 2000 Server. The=20
Publication worked with no problem on the SQL Server 7=20
server environment.
Does anybody have any idea.
Best regards=20
Jakob Br=F8ckner
If possible please also post an answer directly to my=20
email address.
I think your best idea is to recreate the publication - SQL 2000 is sending
some new parameters that were not around in SQL 7
"Jakob Brckner" <jb@.visual.as> wrote in message
news:052301c47fb7$05f48470$7d02280a@.phx.gbl...
Hi everyone,
I am trying to create a Transactional Pull Subscription
but I get an error 207 : Invalid column
name "enabled_for_syncmgr"
Invalid columnname "alt_snapshot_folder"
Invalid columnname "dts_package_name".
Both The Publication and Subscriber databases are SQL
Server 7 backups restored on a SQL Server 2000 Server. The
Publication worked with no problem on the SQL Server 7
server environment.
Does anybody have any idea.
Best regards
Jakob Brckner
If possible please also post an answer directly to my
email address.
|||I have already recreated the publication with same error.
/Jakob Br=F8ckner
>--Original Message--
>I think your best idea is to recreate the publication -=20
SQL 2000 is sending
>some new parameters that were not around in SQL 7
>"Jakob Br=F8ckner" <jb@.visual.as> wrote in message
>news:052301c47fb7$05f48470$7d02280a@.phx.gbl...
>Hi everyone,
>I am trying to create a Transactional Pull Subscription
>but I get an error 207 : Invalid column
>name "enabled_for_syncmgr"
>Invalid columnname "alt_snapshot_folder"
>Invalid columnname "dts_package_name".
>Both The Publication and Subscriber databases are SQL
>Server 7 backups restored on a SQL Server 2000 Server. The
>Publication worked with no problem on the SQL Server 7
>server environment.
>Does anybody have any idea.
>Best regards
>Jakob Br=F8ckner
>If possible please also post an answer directly to my
>email address.
>
>.
>
|||It seems I have solved the problem. The problem was that the tables :
MSsubscription_properties
MSreplication_subscriptions
Have a different design in SQL Server 2K than in SQL Server 7. And these
tables was also restored. And the sp_addpullsubscription_agent tries to
insert into these tables and some fields are missing or have different names.
But the sp_addpullsubscription_agent does not drop and recreate the table
for obvious reasons. But I dropped them through Query Analyser since you are
not allowed to drop System tables through Enterprise manager. But usiing :
DROP TABLE MSsubscription_properties
DROP TABLE MSreplication_subscriptions
and then trying to pull the subscription solved the problem.
/Jakob
"Jakob Br?ckner" wrote:

> I have already recreated the publication with same error.
> /Jakob Br?ckner
> SQL 2000 is sending
>