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