MSDE and Access 2000

Hi everyone,

In using the SQL Server Database Wizard in Access 2000 to create a new
access project, I get two consecutive error messages and then the wizard
shuts down. The first, which apprears immediately after starting the wizard
is a message box stating something like "the property value is too large".
After clicking through and filling out the values in the connection and
database dialog, I get a second dialog box with the message "Overflow" and
the wizard terminates.

My operating system is Windows 2000 Professional with Access 2000 and MSDE
2000.

Does anyone have any thoughts about what might be causing these errors?

Thanks in advance.Hi Stephen

Have a look at Microsoft Knowledge Base Article Q272384
http://support.microsoft.com/defaul...kb;EN-US;272384

It describes the overflow error when creating a MS Access project on MSDE
2000.
Apparently, installing MS Office Service Pack 3 should fix the problem.

Hope this helps!

Martin

"Stephen Bishop" <sbishop33@.comcast.net> wrote in message
news:5KednfNSnerNM-vdRVn-tw@.comcast.com...
> Hi everyone,
> In using the SQL Server Database Wizard in Access 2000 to create a new
> access project, I get two consecutive error messages and then the wizard
> shuts down. The first, which apprears immediately after starting the
wizard
> is a message box stating something like "the property value is too large".
> After clicking through and filling out the values in the connection and
> database dialog, I get a second dialog box with the message "Overflow" and
> the wizard terminates.
> My operating system is Windows 2000 Professional with Access 2000 and MSDE
> 2000.
> Does anyone have any thoughts about what might be causing these errors?
> Thanks in advance.|||Thanks, Martin. I'll take a look at the article and see if it helps. As
far as the office version, I'm using Access 2000 (9.0.2720) and Office
2000, but I don't know the service pack status.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!|||Open Access -> Help -> About Microsoft Access

At the end of first line it should say e.g. SP-1, SP-2 etc depending
on what service pack is installed.

Stephen Bishop <sbishop33@.comcast.net> wrote in message news:<40784f48$0$206$75868355@.news.frii.net>...
> Thanks, Martin. I'll take a look at the article and see if it helps. As
> far as the office version, I'm using Access 2000 (9.0.2720) and Office
> 2000, but I don't know the service pack status.

MSDE 2000a Deployment Issues

I need to deploy MSDE 2000a with a custom app built in VB6. I found the
setup package to add MSDE 1.0 through the Package & Deployment Wizard, but
the link I found for MSDE 2000 goes to the same article as 1.0. I've also
seen a lot of info on using merge modules to deploy MSDE 2000, but I'm
clueless about them. What is the best (and hopefully easiest) way to deploy
MSDE 2000 with a custom app built with VB6 using the Package & Deployment
Wizard? Any help would be greatly appreciated.
My advice is don't.
Package the setup program from MS, configure the setup.ini file the way you
want it and get the user to run it. Every other option seems to end up in
pain at present. Much better story coming for SQL Express.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"pbb" <pbb@.discussions.microsoft.com> wrote in message
news:DDFFD02B-301D-4273-B32B-D6CCFAB50A76@.microsoft.com...
>I need to deploy MSDE 2000a with a custom app built in VB6. I found the
> setup package to add MSDE 1.0 through the Package & Deployment Wizard, but
> the link I found for MSDE 2000 goes to the same article as 1.0. I've also
> seen a lot of info on using merge modules to deploy MSDE 2000, but I'm
> clueless about them. What is the best (and hopefully easiest) way to
> deploy
> MSDE 2000 with a custom app built with VB6 using the Package & Deployment
> Wizard? Any help would be greatly appreciated.
|||Okay, so it sounds like what you're saying is that it's best to include 2
setup programs? First have the user run the setup.exe that comes with MSDE
(with the customized ini file), and then have them run the setup package for
the custom app?
"Greg Low [MVP]" wrote:

> My advice is don't.
> Package the setup program from MS, configure the setup.ini file the way you
> want it and get the user to run it. Every other option seems to end up in
> pain at present. Much better story coming for SQL Express.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "pbb" <pbb@.discussions.microsoft.com> wrote in message
> news:DDFFD02B-301D-4273-B32B-D6CCFAB50A76@.microsoft.com...
>
>
|||Yep
"pbb" <pbb@.discussions.microsoft.com> wrote in message
news:4203C438-9A56-48F0-B36D-22793F26F4AD@.microsoft.com...[vbcol=seagreen]
> Okay, so it sounds like what you're saying is that it's best to include 2
> setup programs? First have the user run the setup.exe that comes with
> MSDE
> (with the customized ini file), and then have them run the setup package
> for
> the custom app?
> "Greg Low [MVP]" wrote:

msdb refuses to back up w/ plan

All,
I've created (and re-created) a Mx plan for the system databases.
Part of it is a complete backup. All the default options in the
wizard were chosen, including the option to verify.
Master and Model back up fine. MSDB, however, fails. According to
the Mx Plan log, the backup completes successfully, but the verify
fails as follows:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup
device 'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042207.BAK'. Device
error or device off-line. See the SQL Server error log for more
details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
terminating abnormally.
1- It doesn't appear that the backup actually succeeded, as there is
no msdb_db_200407042207.bak file in the directory.
2- There is no additional information in the SQL Server error log
3- I can successfully back up msdb -manually- without a hiccup.
I've tried:
1- Recreating a new Mx Plan from scratch (no effect)
2- Can full index/optimizations on msdb (no errors found)
3- Tried shrinking the database (it's 215MBish) to make it faster
4- Tried a full backup/restore of msdb in case it had any mystery
corruption (no effect)
Oh yes, SQL Server standard 2000 sp3 on W2.3K standard. NTFS
partition. SQL Agent using a domain account, SQL Server running under
the same account.
Can anyone shed light on this? I can come up with no reason why the
Mx plan would fail for just this one database, when I can back it up
just fine manually.
GeofHere's some more info:
I did find some additional information in the app event log, giving the specific T-SQL that was failing:
BACKUP DATABASE [msdb] TO DISK = N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
After some pondering and re-reading my own post, I went ahead and logged into the server interactively using SQL Server's account. I attempted to execute the above SQL and lo and behond, it failed (General Network Error). When executed under my normal UserID, it executed fine.
Trial and error then produced the rather odd discovery that the problem part of the statement is the seemingly innocuous "STATS=10" command. If the same statement is run under the SQL Server account EXCEPT for removing the stats=10 command, it works fine.
While I've gotten more information on exactly what is causing the problem, I:
1- Have no idea why the problem is occurring, and
2- Don't know a way around it (other than backup w/o using a Mx Plan)
My nearest stab would be that this particular T-SQL (and STATS option in particular) is causing some sort of collision between SQL Server and SQL Server Agent since they would both be running under the same account. (But surely I'm not the only one in the history of SQL Server to have created a sysdb mx plan w/ both SQL and SQL Agent running under an identical domain account, huh')
Ideas'|||Go the Maintenance Plan and right click and view maintenance history out
there ...Thats where most of the reasoning is for the failure..
"Geof" <Geof@.discussions.microsoft.com> wrote in message
news:C6436F94-BF81-41FD-9869-5595F7FBA6B4@.microsoft.com...
> Here's some more info:
> I did find some additional information in the app event log, giving the
specific T-SQL that was failing:
> BACKUP DATABASE [msdb] TO DISK =N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BAK' WITH INIT , NOUNLOAD
, NOSKIP , STATS = 10, NOFORMAT
> After some pondering and re-reading my own post, I went ahead and logged
into the server interactively using SQL Server's account. I attempted to
execute the above SQL and lo and behond, it failed (General Network Error).
When executed under my normal UserID, it executed fine.
> Trial and error then produced the rather odd discovery that the problem
part of the statement is the seemingly innocuous "STATS=10" command. If the
same statement is run under the SQL Server account EXCEPT for removing the
stats=10 command, it works fine.
> While I've gotten more information on exactly what is causing the problem,
I:
> 1- Have no idea why the problem is occurring, and
> 2- Don't know a way around it (other than backup w/o using a Mx Plan)
> My nearest stab would be that this particular T-SQL (and STATS option in
particular) is causing some sort of collision between SQL Server and SQL
Server Agent since they would both be running under the same account. (But
surely I'm not the only one in the history of SQL Server to have created a
sysdb mx plan w/ both SQL and SQL Agent running under an identical domain
account, huh')
> Ideas'|||In my first post I listed what was in the Mx Plan History. Does
anyone have any other ideas?
Geof
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:<#GDGyveYEHA.996@.TK2MSFTNGP12.phx.gbl>...
> Go the Maintenance Plan and right click and view maintenance history out
> there ...Thats where most of the reasoning is for the failure..

MSDb and Master maintenance

Using the Database Maintenenace Plan Wizard I set up
maintenance plans for each of the databases on my MS SQL
Server. This is working fine except for the "msdb"
and "master" databases. For these I get the following
errors. What am I doing wrong?
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
(trusted)
Starting maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 8:00:01 AM
[1] Database msdb: Check Data and Index Linkage...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Backup can not be performed on database 'msdb'. This sub
task is ignored.
End of maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 8:00:02 AM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
(trusted)
Starting maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 4:00:01 AM
[1] Database msdb: Check Data and Index Linkage...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Backup can not be performed on database 'msdb'. This sub
task is ignored.
End of maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 4:00:02 AM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
You probably try to do log backups. You can't do log backup on master. You can on model, but that is
overkill and would require setting it to full recovery mode. I suggest you create two plans, One in
which you do log backup, another in which you don't.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John Schuster" <schuster@.llnl.gov> wrote in message news:4aa201c49f30$4fc629d0$a601280a@.phx.gbl...
> Using the Database Maintenenace Plan Wizard I set up
> maintenance plans for each of the databases on my MS SQL
> Server. This is working fine except for the "msdb"
> and "master" databases. For these I get the following
> errors. What am I doing wrong?
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged
> on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
> (trusted)
> Starting maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 8:00:01 AM
> [1] Database msdb: Check Data and Index Linkage...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Backup can not be performed on database 'msdb'. This sub
> task is ignored.
> End of maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 8:00:02 AM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
> ----
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged
> on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
> (trusted)
> Starting maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 4:00:01 AM
> [1] Database msdb: Check Data and Index Linkage...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Backup can not be performed on database 'msdb'. This sub
> task is ignored.
> End of maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 4:00:02 AM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>

MSDb and Master maintenance

Using the Database Maintenenace Plan Wizard I set up
maintenance plans for each of the databases on my MS SQL
Server. This is working fine except for the "msdb"
and "master" databases. For these I get the following
errors. What am I doing wrong?
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
(trusted)
Starting maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 8:00:01 AM
[1] Database msdb: Check Data and Index Linkage...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Backup can not be performed on database 'msdb'. This sub
task is ignored.
End of maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 8:00:02 AM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
----
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
(trusted)
Starting maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 4:00:01 AM
[1] Database msdb: Check Data and Index Linkage...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Backup can not be performed on database 'msdb'. This sub
task is ignored.
End of maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 4:00:02 AM
SQLMAINT.EXE Process Exit Code: 1 (Failed)You probably try to do log backups. You can't do log backup on master. You can on model, but that is
overkill and would require setting it to full recovery mode. I suggest you create two plans, One in
which you do log backup, another in which you don't.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John Schuster" <schuster@.llnl.gov> wrote in message news:4aa201c49f30$4fc629d0$a601280a@.phx.gbl...
> Using the Database Maintenenace Plan Wizard I set up
> maintenance plans for each of the databases on my MS SQL
> Server. This is working fine except for the "msdb"
> and "master" databases. For these I get the following
> errors. What am I doing wrong?
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged
> on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
> (trusted)
> Starting maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 8:00:01 AM
> [1] Database msdb: Check Data and Index Linkage...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Backup can not be performed on database 'msdb'. This sub
> task is ignored.
> End of maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 8:00:02 AM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
> ----
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged
> on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
> (trusted)
> Starting maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 4:00:01 AM
> [1] Database msdb: Check Data and Index Linkage...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Backup can not be performed on database 'msdb'. This sub
> task is ignored.
> End of maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 4:00:02 AM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>