Friday, March 9, 2012
Error 5041. MODIFY FILE failed. File '%.*ls' does not exist.
10% and I get the message:
Microsoft SQL-MDO (ODBC SQL-STATE 42000)
Error 5041. MODIFY FILE failed. File '%.*ls' does not
exist.
All I know is that this system error message is of
severity 16.
DO you have any ideas?
See my other reply. Please don't re-post...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Kostas Kourtides" <KostasKourtides@.yahoo.com> wrote in message
news:275101c45d0a$f7b4bd90$3501280a@.phx.gbl...
> I am trying to set the file growth of a database file to
> 10% and I get the message:
> Microsoft SQL-MDO (ODBC SQL-STATE 42000)
> Error 5041. MODIFY FILE failed. File '%.*ls' does not
> exist.
> All I know is that this system error message is of
> severity 16.
> DO you have any ideas?
Error 5041. MODIFY FILE failed. File '%.*ls' does not exist.
10% and I get the message:
Microsoft SQL-MDO (ODBC SQL-STATE 42000)
Error 5041. MODIFY FILE failed. File '%.*ls' does not
exist.
All I know is that this system error message is of
severity 16.
DO you have any ideas?See my other reply. Please don't re-post...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Kostas Kourtides" <KostasKourtides@.yahoo.com> wrote in message
news:275101c45d0a$f7b4bd90$3501280a@.phx.gbl...
> I am trying to set the file growth of a database file to
> 10% and I get the message:
> Microsoft SQL-MDO (ODBC SQL-STATE 42000)
> Error 5041. MODIFY FILE failed. File '%.*ls' does not
> exist.
> All I know is that this system error message is of
> severity 16.
> DO you have any ideas?
Error 5041. MODIFY FILE failed. File '%.*ls' does not exist.
10% and I get the message:
Microsoft SQL-MDO (ODBC SQL-STATE 42000)
Error 5041. MODIFY FILE failed. File '%.*ls' does not
exist.
All I know is that this system error message is of
severity 16.
DO you have any ideas?See my other reply. Please don't re-post...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Kostas Kourtides" <KostasKourtides@.yahoo.com> wrote in message
news:275101c45d0a$f7b4bd90$3501280a@.phx.gbl...
> I am trying to set the file growth of a database file to
> 10% and I get the message:
> Microsoft SQL-MDO (ODBC SQL-STATE 42000)
> Error 5041. MODIFY FILE failed. File '%.*ls' does not
> exist.
> All I know is that this system error message is of
> severity 16.
> DO you have any ideas?
Wednesday, March 7, 2012
error 3926 , server failed to resume transaction
In a high load asp.net environment, I am getting an error.
The transation active in this session has been committed or aborted by another session.
Here is the code , I am getting error.
1object returnObject =null;2 SqlTransaction sqlTrans =null;3try4 {5//Getting new SqlConnection6 comm.Connection = GetConnection();7//Opening connection8 OpenConn(comm.Connection);9//beginning transaction10 sqlTrans = comm.Connection.BeginTransaction( IsolationLevel.ReadCommitted );11//setting transaction to SqlCommand object12 comm.Transaction = sqlTrans;13//executing operation14 returnObject = comm.ExecuteScalar();15//trying to commit.16 sqlTrans.Commit();171819 }20catch (SqlException sex)21 {22if (sqlTrans !=null)23 {24 sqlTrans.Rollback();25 }26 }27finally28 {29 comm.Connection.Close();30 } Could you please explain , am I doing smthg wrong ?Check out this link: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2041937&SiteID=17
Good luck.
|||Hi CS4Ever ,
Thanks for the reply, but as far as I understood , Thona just submitted the situation , not a solution and the 3rd reply belongs to me :)
What could I possibly do ? Submit a bug to Microsoft ?
Thanks in advance.
|||Still no answers ?
Sunday, February 26, 2012
Error 3013
Executed as user: HACIEXXWVNDA\MH-GAGI-WEB01$. Operation on device '\\.\Tape0' exceeded retry count. [SQLSTATE 42000] (Error 3230) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
Does anyone know why this happened? Any help is appreciated.
Thanks
Hi ..
I'm getting the same error; please anyone can help in the matter ASAP.
Thanks and regards.
|||I'd check out the hardware, but in the mean time why don't you back up to a file instead of to tape, then backup the files to tape. It's a safer way to back up, and you're not relying on that particular tape drive to be available when you need to restore, should that need arise.
Error 3013
Executed as user: HACIEXXWVNDA\MH-GAGI-WEB01$. Operation on device '\\.\Tape0' exceeded retry count. [SQLSTATE 42000] (Error 3230) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
Does anyone know why this happened? Any help is appreciated.
Thanks
Hi ..
I'm getting the same error; please anyone can help in the matter ASAP.
Thanks and regards.
|||I'd check out the hardware, but in the mean time why don't you back up to a file instead of to tape, then backup the files to tape. It's a safer way to back up, and you're not relying on that particular tape drive to be available when you need to restore, should that need arise.
Friday, February 24, 2012
Error 29506. SQL Server Setup failed to modify security permissions
MSI (s) (D8!A0) [21:07:09:062]: Product: Microsoft SQL Server 2005 -- Error 29506. SQL Server Setup failed to modify security permissions on file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ for user Administrator. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.
Tried running install with a domain account and local account with same results.
Based on the error message, I checked permission on the drive and still received the same error.
Followed resolution based on KB 916766, this did not resolve the error.
Only possible resolution I found was to disable UAP, reboot and retry the install. This will be done as a last resort, but any other suggestion will be appreciated.
Many Thanks
http://support.microsoft.com/kb/916766
This was the solution. Pays to read the resolution carefully
Went through ALL the files and finally found the ones without proper permissions
|||Check whether the account(admin ID) u r using to install SP2 has sysadmin privilege in SQL
Error 29506. SQL Server Setup failed to modify security permissions
MSI (s) (D8!A0) [21:07:09:062]: Product: Microsoft SQL Server 2005 -- Error 29506. SQL Server Setup failed to modify security permissions on file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ for user Administrator. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.
Tried running install with a domain account and local account with same results.
Based on the error message, I checked permission on the drive and still received the same error.
Followed resolution based on KB 916766, this did not resolve the error.
Only possible resolution I found was to disable UAP, reboot and retry the install. This will be done as a last resort, but any other suggestion will be appreciated.
Many Thanks
http://support.microsoft.com/kb/916766
This was the solution. Pays to read the resolution carefully
Went through ALL the files and finally found the ones without proper permissions
|||Check whether the account(admin ID) u r using to install SP2 has sysadmin privilege in SQL
Sunday, February 19, 2012
Error 22029
The job failed. The Job was invoked by Schedule 9 (Schedule 1). The last step to run was step 1 (Step 1).
Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
This problem i found in Maintenance Plan & error log file:
Maintenance Plan:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 927: [Microsoft][ODBC SQL Server Driver][SQL Server]Database 'restore_test' cannot be opened. It is in the middle of a restore.
[Microsoft][ODBC SQL Server Driver][SQL
Error Log file:
BACKUP failed to complete the command BACKUP DATABASE [restore_test] TO DISK = N'E:\SQL_Backups\restore_test\restore_test_db_2006 04160200.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
Please help me in find out the solutionverify if the "NT AUTHORITY\SYSTEM" has access to the database and proper rights assigned.|||[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 927: [Microsoft][ODBC SQL Server Driver][SQL Server]Database 'restore_test' cannot be opened. It is in the middle of a restore.
[Microsoft][ODBC SQL Server Driver][SQL
Ummm ... what is the status of the database 'restore_test'?
Loading perhaps? Or suspect?|||Ummm ... what is the status of the database 'restore_test'?
Loading perhaps? Or suspect?
Yes its keep loading|||Yes 'restore_test' database is loading, please provide me help on this.
Regards,
Sumit|||If it is still loading after this much time has past, you might have a corrupt database or bad storage media.
Stop the backup. Stop the restore.
You might try RESTORE VERIFYONLY on the backup file to see if that completes.
If it does complete, it will let you know whether or not the backup file you are using for your restore is viable.
If it does not complete, then that would lead you to your storage device and it's connections to your database server.|||hi tomh,
Thanks for your suggestions, it really works.
Regards,
Sumit|||Hi,
The Problem is solved, Thanks for your valuable time.
Regards,
Sumit
Friday, February 17, 2012
Error -2147217900: failed to create SQL database
On a different note, we rebuilt the SQL cluster network today. However when
I run the MSI, I am seeing the below given error this time:
Event Type:Error
Event Source:MsiInstaller
Event Category:None
Event ID:10005
Date:10/16/2006
Time:4:06:34 PM
User:myDomain\SQLServerAccount
Computer:SQLServer
Description:
Product: Database -- Error 26201. Error -2147217900: failed to create SQL
database: ApplicationDb, error detail: CREATE DATABASE failed. Some file
names listed could not be created. Check previous errors..
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Any thoughts on what this error is, and what could be causing this?
--Mehul
"Geoff N. Hiten" wrote:
> Use the cluster.exe command-line utility to stop and restart instances from
> within a script.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Mehul" <Mehul@.discussions.microsoft.com> wrote in message
> news:39DD3469-5CEE-49DC-9755-681B5701D0EF@.microsoft.com...
>
>
When you rebuilt the cluster, did you add disk resources as dependencies for
SQL Server? If not, then SOL Server cannot see the disks.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"Mehul" <Mehul@.discussions.microsoft.com> wrote in message
news:CCA03ACA-2B83-488C-B479-11406C9E2D1C@.microsoft.com...
Geoff,
On a different note, we rebuilt the SQL cluster network today. However when
I run the MSI, I am seeing the below given error this time:
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 10/16/2006
Time: 4:06:34 PM
User: myDomain\SQLServerAccount
Computer: SQLServer
Description:
Product: Database -- Error 26201. Error -2147217900: failed to create SQL
database: ApplicationDb, error detail: CREATE DATABASE failed. Some file
names listed could not be created. Check previous errors..
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Any thoughts on what this error is, and what could be causing this?
--Mehul
"Geoff N. Hiten" wrote:
> Use the cluster.exe command-line utility to stop and restart instances
> from
> within a script.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Mehul" <Mehul@.discussions.microsoft.com> wrote in message
> news:39DD3469-5CEE-49DC-9755-681B5701D0EF@.microsoft.com...
>
>
|||Try creating the databases maually so you get the SQL error message, not the
installer error message. That should tell you exactly why it failed.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:u4pJE2X8GHA.4708@.TK2MSFTNGP05.phx.gbl...
> When you rebuilt the cluster, did you add disk resources as dependencies
> for
> SQL Server? If not, then SOL Server cannot see the disks.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> .
> "Mehul" <Mehul@.discussions.microsoft.com> wrote in message
> news:CCA03ACA-2B83-488C-B479-11406C9E2D1C@.microsoft.com...
> Geoff,
> On a different note, we rebuilt the SQL cluster network today. However
> when
> I run the MSI, I am seeing the below given error this time:
> Event Type: Error
> Event Source: MsiInstaller
> Event Category: None
> Event ID: 10005
> Date: 10/16/2006
> Time: 4:06:34 PM
> User: myDomain\SQLServerAccount
> Computer: SQLServer
> Description:
> Product: Database -- Error 26201. Error -2147217900: failed to create SQL
> database: ApplicationDb, error detail: CREATE DATABASE failed. Some file
> names listed could not be created. Check previous errors..
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Any thoughts on what this error is, and what could be causing this?
> --Mehul
> "Geoff N. Hiten" wrote:
>
|||You are right on. This is exactly the cause for the below given error log.
We ran profiler to see what commands is the MSI passing to create the DB.
Then we manually tried to run that command in Query analyzer, that throwed
reference to the disk dependency.
Thanks Tom/Geoff for your quick response.
--Mehul
"Tom Moreau" wrote:
> When you rebuilt the cluster, did you add disk resources as dependencies for
> SQL Server? If not, then SOL Server cannot see the disks.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Mehul" <Mehul@.discussions.microsoft.com> wrote in message
> news:CCA03ACA-2B83-488C-B479-11406C9E2D1C@.microsoft.com...
> Geoff,
> On a different note, we rebuilt the SQL cluster network today. However when
> I run the MSI, I am seeing the below given error this time:
> Event Type: Error
> Event Source: MsiInstaller
> Event Category: None
> Event ID: 10005
> Date: 10/16/2006
> Time: 4:06:34 PM
> User: myDomain\SQLServerAccount
> Computer: SQLServer
> Description:
> Product: Database -- Error 26201. Error -2147217900: failed to create SQL
> database: ApplicationDb, error detail: CREATE DATABASE failed. Some file
> names listed could not be created. Check previous errors..
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Any thoughts on what this error is, and what could be causing this?
> --Mehul
> "Geoff N. Hiten" wrote:
>
>
Wednesday, February 15, 2012
Error 208 Failed to open new connection
Regards,
Jamie
"John Bell" wrote:
[vbcol=seagreen]
> 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:
Not sure what I contributed! Did you find out what was missing?
John
"thejamie" wrote:
[vbcol=seagreen]
> Your help and a reboot put us back in business. Thanks.
> --
> Regards,
> Jamie
>
> "John Bell" 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:
[vbcol=seagreen]
> Not sure what I contributed! Did you find out what was missing?
> John
> "thejamie" 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:
[vbcol=seagreen]
> 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:
|||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:
[vbcol=seagreen]
> Not sure what I contributed! Did you find out what was missing?
> 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:
[vbcol=seagreen]
> Not sure what I contributed! Did you find out what was missing?
> John
> "thejamie" wrote:
|||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:
[vbcol=seagreen]
> 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:
|||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:
[vbcol=seagreen]
> 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:
Error 208 Failed to open new connection
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