DB2OLEDB Failed to install on SQL Server 2005 Developer Edition

I have SQL Server 2005 Developer Edition installed on XP Pro sp2 and have not been able to get OLE DB Provider for DB2 Version 1.0 with Service Pack 1 to install. After getting a notice that the install has failed, I get these log files:

=== Logging started at: 2:12:35 PM Monday, August 20, 2007 Build: 7.0.3038.0 Calling process: H:\SQL2005\DB2OLEDB7\Setup.exe === The current user is NORTHGRUM\dinsest. Computer name: DICA2ESITE13005 OS Version: 5.1 Build: 2600 Service Pack: 2.0 Suite: 256 Product Type: 1
[2:12:35 PM Info] Command Line: H:\SQL2005\DB2OLEDB7\Setup.exe
[2:12:35 PM Info] Language: 1033
[2:12:59 PM Info] Raw module path: H:\SQL2005\DB2OLEDB7\Setup.exe
[2:12:59 PM Info] Universal module path: H:\SQL2005\DB2OLEDB7\Setup.exe
[2:12:59 PM Info] Current version of msi.dll is: 3.1 build: 4000 platform: 2
[2:12:59 PM Info] Raw module path: H:\SQL2005\DB2OLEDB7\Setup.exe
[2:12:59 PM Info] Universal module path: H:\SQL2005\DB2OLEDB7\Setup.exe === Logging stopped: 2:12:59 PM Monday, August 20, 2007 === === Logging started at: 2:13:00 PM Monday, August 20, 2007 Build: 7.0.3038.0 Calling process: C:\DOCUME~1\dinsest\LOCALS~1\Temp\EBZ34671.tmp\Setup.exe === The current user is NORTHGRUM\dinsest. Computer name: DICA2ESITE13005 OS Version: 5.1 Build: 2600 Service Pack: 2.0 Suite: 256 Product Type: 1
[2:13:00 PM Info] Command Line: H:\SQL2005\DB2OLEDB7\Setup.exe /Relaunch /RunningFromTemp /SetupXML C:\DOCUME~1\dinsest\LOCALS~1\Temp\EBZ34671.tmp\HISDB2_x86.xml
[2:13:00 PM Info] Language: 1033
[2:13:00 PM Info]

[2:13:00 PM Info] Running prehook init function
[2:13:00 PM Info] Entering PreInitHook
[2:13:00 PM Info] Detecting Sql Server 2005 (32bit)
[2:13:00 PM Info] Enumerating Sql Server 2005 instances from Software\Microsoft\Microsoft SQL Server\Instance Names\SQL
[2:13:00 PM Info] Checking SQL version and edition for: Software\Microsoft\Microsoft SQL Server\MSSQL.1\Setup
[2:13:00 PM Info] Got Version 9.2.3042.00
[2:13:00 PM Info] Got edition Developer Edition
[2:13:00 PM Info] Done enumerating Sql Server 2005 instances, original hr = 00000000
[2:13:00 PM Info] Done enumerating Sql Server 2005 instances, hr = 00000000
[2:13:00 PM Info] Done detecting Sql Server 2005, hr = 00000000
[2:13:00 PM Info] Detecting existing integration server installations
[2:13:00 PM Info] Integration server is not installed
[2:13:00 PM Info] Done detecting existing integration server installations, hr = 00000000
[2:13:00 PM Info] Leaving PreInitHook (hr = 00000000)
[2:13:00 PM Info] Prehook Init function returned: 0.
[2:13:00 PM Info] Prehook Init function returned the following mode: 0
[2:13:01 PM Info] Product code: {722CAF00-DE6E-4438-82DE-E664B8B6222B}
[2:13:01 PM Info] Product name: Microsoft OLE DB Provider for DB2
[2:13:01 PM Info] Product PIDSKU: BI6-00082
[2:13:01 PM Info] Product Code (MPC): 91197
[2:13:01 PM Info] OEMID:
[2:13:01 PM Info] Product is not already installed.
[2:13:01 PM Info] Successfully opened Msi package: H:\SQL2005\DB2OLEDB7\Msi\x86\HISDB2.msi
[2:13:01 PM Info] Raw module path: C:\DOCUME~1\dinsest\LOCALS~1\Temp\EBZ34671.tmp\Setup.exe
[2:13:01 PM Info] Universal module path: C:\DOCUME~1\dinsest\LOCALS~1\Temp\EBZ34671.tmp\Setup.exe
[2:13:10 PM Info] Initializing Component Updater ...
[2:13:10 PM Info] Initialized Component Updater
[2:13:10 PM Info] No updates were found on the SUS server to download.
[2:13:14 PM Info] Required platform components:
[2:13:20 PM Info] Initializing Component Updater ...
[2:13:20 PM Info] Initialized Component Updater
[2:13:20 PM Info] No updates were found on the SUS server to download.
[2:13:20 PM Info] Required platform components: (none)
[2:13:20 PM Info] MSI command line: ADDLOCAL=REQUIRED_FEATURE,OLE_DB_PROVIDER_FOR_DB2 INSTALLDIR="C:\Program Files\Microsoft OLE DB Provider for DB2\" PIDKEY="R2D433DHG9DQ79WW3DXQ929DY" USERNAME="Northrop Grumman Corporation" COMPANYNAME="NGGN" FILESINUSEERROR=""
[2:13:20 PM Info] MSI command line is ADDLOCAL=REQUIRED_FEATURE,OLE_DB_PROVIDER_FOR_DB2 INSTALLDIR="C:\Program Files\Microsoft OLE DB Provider for DB2\" PIDKEY="R2D433DHG9DQ79WW3DXQ929DY" USERNAME="Northrop Grumman Corporation" COMPANYNAME="NGGN" FILESINUSEERROR=""
[2:13:20 PM Info] Detailed Log information for product H:\SQL2005\DB2OLEDB7\Msi\x86\HISDB2.msi is available at DetailedLog
[2:13:20 PM Info] MSI installation returned 2 - The system cannot find the file specified.
[2:13:20 PM Error] Error 0 occurred during MSI installation.
[2:13:20 PM Error]
[2:13:20 PM Error] === Logging stopped: 2:13:25 PM Monday, August 20, 2007 ===

Detailed Log

=== Verbose logging started: 8/20/200714:13:20Build type: SHIP UNICODE 3.01.4000.2435Calling process: C:\DOCUME~1\dinsest\LOCALS~1\Temp\EBZ34671.tmp\Setup.exe ===

MSI (c) (E4C) [14:13:20:343]: Resetting cached policy values

MSI (c) (E4C) [14:13:20:343]: Machine policy value 'Debug' is 0

MSI (c) (E4C) [14:13:20:343]: ******* RunEngine:

******* Product: H:\SQL2005\DB2OLEDB7\Msi\x86\HISDB2.msi

******* Action:

******* CommandLine: **********

MSI (c) (E4C) [14:13:20:343]: Client-side and UI is none or basic: Running entire install on the server.

MSI (c) (E4C) [14:13:20:343]: Grabbed execution mutex.

MSI (c) (E4C) [14:13:20:359]: Cloaking enabled.

MSI (c) (E4C) [14:13:20:359]: Attempting to enable all disabled priveleges before calling Install on Server

MSI (c) (E4C) [14:13:20:359]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI (s) (B88) [14:13:20:374]: Grabbed execution mutex.

MSI (s) (B8:90) [14:13:20:374]: Resetting cached policy values

MSI (s) (B8:90) [14:13:20:374]: Machine policy value 'Debug' is 0

MSI (s) (B8:90) [14:13:20:374]: ******* RunEngine:

******* Product: H:\SQL2005\DB2OLEDB7\Msi\x86\HISDB2.msi

******* Action:

******* CommandLine: **********

MSI (s) (B8:90) [14:13:20:374]: Machine policy value 'DisableUserInstalls' is 0

MSI (s) (B8:90) [14:13:20:406]: MainEngineThread is returning 2

MSI (c) (E4C) [14:13:20:421]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.Counter after decrement: -1

MSI (c) (E4C) [14:13:20:421]: MainEngineThread is returning 2

=== Verbose logging stopped: 8/20/200714:13:20 ===

Does anyone have an idea as to why the installation is failing?

TIA,

Steve

P.S. Those aren't really smileys, they're actually semicolon Ds but I can't seem to get rid of the cartoon translation, even after checking the "This post contains a code sample" checkbox.

Trial and error has provided my answer to this problem. It seems that not all executables will perform as expected when run from a USB attached drive. Copying them to the C: drive and then executing them was the only way this worked.

Hope this will help someone else. I didn't know this would be a problem.

Steve

sql

db_owner role

I am getting this error message when disabling a job. The user is not a SA.

TITLE: Microsoft.SqlServer.Smo

Alter failed for Job 'XYZ'.

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

EXECUTE permission denied on object 'sp_help_operator', database 'msdb', owner 'dbo'. (Microsoft SQL Server, Error: 229)

The user can diasble the job if i give db_owner permission on msdb.

Is there a way i can do this without making the user db_owner?

Thanks for any help

There is no specific db_role for job administation, but you can create one. Grant the appropiate permission to the role that you need and assign the user to that role. You sure can also only grant the specific user the rights for that, but the next time you want another user to do the job you will have to repeat your work for that.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks.

Could you describe the "Grant the appropriate permission to the role that you need" in as little more detail as to what has to be done?

Thanks for the help

|||

I don′t know the complete list of permissions you will need for your work to be done, so you would have to go the iterative way to get your work done, here are the steps to complete:

-Create a db Role in the Database msdb (as you want to administer the alerts and things related to the SQL Agent)
-Assign users to this role that should do the administrative work.
-Assign the appropiate permissions to that db role (where the users are currently in) Put in the execute right for that procedure you get an error for.

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de

DB_E_ERRORSOCCURRED

inline void Field20::PutValue ( const _variant_t & pvar )

{

HRESULT _hr = put_Value(pvar); > where pVar is datetime value

if (FAILED(_hr)) _com_issue_errorex(_hr, this, __uuidof(this));

}

The put_Value() method returns "DB_E_ERRORSOCCURRED" and the error description which i'm getting is "Multiple-step operation generated errors. Check each status value"

Can anyone please help me out of this.

Note: The above piece of code is working fine in SQL server 2000 but after migrating to SQL server 2005, i am getting this error.

http://www.support.microsoft.com/kb/223180

http://search.microsoft.com/results.aspx?mkt=en-US&setlang=en-US&q=DB_E_ERRORSOCCURRED

|||

I am also facing a similar problem

Any ideas, code working fine in sql 2000 is not working in sql 2005?

What could be the probable reasons?

|||

Hi,

The DB_E_ERRORSOCCURRED (with the Multistep operation failed...) is quite a generic message and may be raised in multiple locations in the Provider code.

My suggestion is to attack the problem from 2 sides:

(a) Capture a SQL Server 2005 Profiler trace, see if any errors would be indicated or anything alarming would show when attempting to set the Value property

(b) On the client, capture a BID trace to attempt to narrow the op which is returning the error. Detailed instructions can be found in the following article:

Data Access Tracing in SQL Server 2005 http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/data_access_tracing.asp

Since SQL Native Client OLEDB provider contains more detailed BID tracing points, good idea is to use SQLNCLI as your Provider.

Based on the findings from these two, you should be able to determine what is wrong with the field's Value you are trying to set. Most likely you are running into a compatibility requirement for SQL 2005 or a case of a more strict requirement being enforced. If you don't manage to narrow the issue down, please provide a script for the underlying table/field creation + a simplified C/C++ repro code.

HTH,

Jivko Dobrev - MSFT

--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Just to follow up on Jivko's points.

SQL 2005 is much stricter than SQL 2000 when evaluating incoming data at the lowest level (the TDS layer). We do this to ensure 100% data purity when data is inserted into the database. So one thing I would do is examine very closely the value of the incoming variant value that is failing, it is most likely an invalid datetime value like Feb 30th for example. Running a sql profiler trace that includes all errors should turn up some errors like:

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter X: The supplied value is not a valid instance of data type Y. Check the source data for invalid values. An example of an invalid value is data of numeric type with scale greater than precision.

DB Suspect error

hi,
my db went into suspect,,got the following error messages from log files..can anyone help me to sort out the problem
1) FCB::Open failed: Could not open device e:\disbursement\disbdata\ICICI_Disb_log.ldf for virtual device number (VDN) 2.
2) udopen: Operating system error 32(The process cannot access the file because it is being used by another process.) during the creation/opening of physical device e:\disbursement\disbdata\ICICI_Disb_log.ldf.
thanks
sanjayNeed some more information regarding the version of SQL
Server that you are running on your server.
This posting is provided "AS IS" with no warranties, and
confers no rights.
http://www.microsoft.com/info/cpyright.htm
>--Original Message--
>hi,
> my db went into suspect,,got the following error
messages from log files..can anyone help me to sort out
the problem
>1) FCB::Open failed: Could not open device
e:\disbursement\disbdata\ICICI_Disb_log.ldf for virtual
device number (VDN) 2.
>2) udopen: Operating system error 32(The process cannot
access the file because it is being used by another
process.) during the creation/opening of physical device
e:\disbursement\disbdata\ICICI_Disb_log.ldf.
>thanks
>sanjay
>.
>|||Seems like some other program is using one of your database files, resulting in SQL Server not being
able to open the file. Could be an anti-virus software, for instance.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"samkau" <anonymous@.discussions.microsoft.com> wrote in message
news:F09AA7EC-7161-412A-AE29-83635DCC9753@.microsoft.com...
> hi,
> my db went into suspect,,got the following error messages from log files..can anyone help me to
sort out the problem
> 1) FCB::Open failed: Could not open device e:\disbursement\disbdata\ICICI_Disb_log.ldf for virtual
device number (VDN) 2.
> 2) udopen: Operating system error 32(The process cannot access the file because it is being used
by another process.) during the creation/opening of physical device
e:\disbursement\disbdata\ICICI_Disb_log.ldf.
> thanks
> sanjay|||its sqlserver 2000,
wot can be the reasons of db going suspect.|||One such reason is another piece of software opening the file so that SQL Server then cannot open
the file for exclusive use. This is more likely to happen if you have autoclose for the database.
Other obvious reasons are hardware problems.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"sanjay" <anonymous@.discussions.microsoft.com> wrote in message
news:72A8470C-34EB-4BD6-88F0-26A67C13146E@.microsoft.com...
> its sqlserver 2000,
> wot can be the reasons of db going suspect.

DB Optimization Failed

Error 21268: [SQL-DMO]Row or column specified is outside the range of the
specified query result set.
This is the error I am getting while running optimization on a database, it
is a mid size database about 30gb having lots of documnets, text datatas
Any quick help is highly appreciated.
Regards...Piku.And in another OPTIMAZION Job getting this Msg, similar lype of database as
mentioned above :
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options have
incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
I don't know why the error Msg says : DBCC failed actually it is an
Optimization Job which failing. I also tried by dropping and recreating the
same.
"Piku" wrote:
> Error 21268: [SQL-DMO]Row or column specified is outside the range of the
> specified query result set.
> This is the error I am getting while running optimization on a database, it
> is a mid size database about 30gb having lots of documnets, text datatas
> Any quick help is highly appreciated.
> Regards...Piku.

DB Optimization Failed

Error 21268: [SQL-DMO]Row or column specified is outside the range of th
e
specified query result set.
This is the error I am getting while running optimization on a database, it
is a mid size database about 30gb having lots of documnets, text datatas
Any quick help is highly appreciated.
Regards...Piku.And in another OPTIMAZION Job getting this Msg, similar lype of database as
mentioned above :
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]&#
91;ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options
have
incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
I don't know why the error Msg says : DBCC failed actually it is an
Optimization Job which failing. I also tried by dropping and recreating the
same.
"Piku" wrote:

> Error 21268: [SQL-DMO]Row or column specified is outside the range of
the
> specified query result set.
> This is the error I am getting while running optimization on a database, i
t
> is a mid size database about 30gb having lots of documnets, text datatas
> Any quick help is highly appreciated.
> Regards...Piku.

DB Maintenance Plan - integrity check

Hi:
After I selected "Attemp to repair any minor problems",
my integrity check failed. - "Repair statement not
processed. Database needs to be in single user mode" for
Master and msdb.
How do I change to single user mode from within
Maintenance Plan?
Thanks in advance.You don't - just deselect the option to repair. It's
probably better to just monitor the DBCC statements and if
there are errors, intervene yourself, track down the issues,
make sure there aren't any hardware problems, etc.
-Sue
On Mon, 22 Sep 2003 11:03:43 -0700, "Dave K."
<uk@.hotmail.com> wrote:
>Hi:
>After I selected "Attemp to repair any minor problems",
>my integrity check failed. - "Repair statement not
>processed. Database needs to be in single user mode" for
>Master and msdb.
>How do I change to single user mode from within
>Maintenance Plan?
>Thanks in advance.

db maintenance job filed to delete old backup files

Hi,
I am working on sql server 2000.
It happened few times to me now, one of my database
maintenance backup job failed to delete the old backup
file. And it always happend to the same database. I set
the job to delete any backup file that is older than 1
day. Any thought on this?
Thanks.
JJCheck out below great troubleshooting suggestions from Bill H at MS:
-- Log files don't delete --
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"JJ Wang" <jwang@.leapwireless.com> wrote in message news:051b01c36ac3$e8a1a320$a301280a@.phx.gbl...
> Hi,
> I am working on sql server 2000.
> It happened few times to me now, one of my database
> maintenance backup job failed to delete the old backup
> file. And it always happend to the same database. I set
> the job to delete any backup file that is older than 1
> day. Any thought on this?
> Thanks.
> JJ
>|||>--Original Message--
>Check out below great troubleshooting suggestions from
Bill H at MS:
>
>-- Log files don't delete --
>This is likely to be either a permissions problem or a
sharing violation
>problem. The maintenance plan is run as a job, and jobs
are run by the
>SQLServerAgent service.
>Permissions:
>1. Determine the startup account for the SQLServerAgent
service
>(Start|Programs|Administrative
tools|Services|SQLServerAgent|Startup). This
>account is the security context for jobs, and thus the
maintenance plan.
>2. If SQLServerAgent is started using LocalSystem (as
opposed to a domain
>account) then skip step 3.
>3. On that box, log onto NT as that account. Using
Explorer, attempt to
>delete an expired backup. If that succeeds then go to
Sharing Violation
>section.
>4. Log onto NT with an account that is an administrator
and use Explorer to
>look at the Properties|Security of the folder (where the
backups reside)
>and ensure the SQLServerAgent startup account has Full
Control. If the
>SQLServerAgent startup account is LocalSystem, then the
account to consider
>is SYSTEM.
>5. In NT, if an account is a member of an NT group, and
if that group has
>Access is Denied, then that account will have Access is
Denied, even if
>that account is also a member of the Administrators
group. Thus you may
>need to check group permissions (if the Startup Account
is a member of a
>group).
>6. Keep in mind that permissions (by default) are
inherited from a parent
>folder. Thus, if the backups are stored in C:\bak, and if
someone had
>denied permission to the SQLServerAgent startup account
for C:\, then
>C:\bak will inherit access is denied.
>Sharing violation:
>This is likely to be rooted in a timing issue, with the
most likely cause
>being another scheduled process (such as NT Backup or
Anti-Virus software)
>having the backup file open at the time when the
SQLServerAgent (i.e., the
>maintenance plan job) tried to delete it.
>1. Download filemon and handle from www.sysinternals.com.
>2. I am not sure whether filemon can be scheduled, or you
might be able to
>use NT scheduling services to start filemon just before
the maintenance
>plan job is started, but the filemon log can become very
large, so it would
>be best to start it some short time before the
maintenance plan starts.
>3. Inspect the filemon log for another process that has
that backup file
>open (if your lucky enough to have started filemon before
this other
>process grabs the backup folder), and inspect the log for
the results when
>the SQLServerAgent agent attempts to open that same file.
>4. Schedule the job or that other process to do their
work at different
>times.
>5. You can use the handle utility if you are around at
the time when the
>job is scheduled to run.
>If the backup files are going to a \\share or a mapped
drive (as opposed to
>local drive), then you will need to modify the above
(with respect to where
>the tests and utilities are run).
>Finally, inspection of the maintenance plan's history
report might be
>useful.
>Thanks,
>Bill Hollinshead
>Microsoft, SQL Server
>
>
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
>"JJ Wang" <jwang@.leapwireless.com> wrote in message
news:051b01c36ac3$e8a1a320$a301280a@.phx.gbl...
>> Hi,
>> I am working on sql server 2000.
>> It happened few times to me now, one of my database
>> maintenance backup job failed to delete the old backup
>> file. And it always happend to the same database. I
set
>> the job to delete any backup file that is older than 1
>> day. Any thought on this?
>> Thanks.
>> JJ
>
>.
>

DB in Loading State

There was a restore script executed against a test
database that failed and left the database in loading
state. I fixed the restore script and executed it again.
I need confirmation if this is alright. I noticed the
MDF and LDF files date changed to the current date.
This looks ok as now restore works. Whenever the restore operation fails the
database is shown in loading state.
"J Lee" wrote:

> There was a restore script executed against a test
> database that failed and left the database in loading
> state. I fixed the restore script and executed it again.
> I need confirmation if this is alright. I noticed the
> MDF and LDF files date changed to the current date.
>

DB in Loading State

There was a restore script executed against a test
database that failed and left the database in loading
state. I fixed the restore script and executed it again.
I need confirmation if this is alright. I noticed the
MDF and LDF files date changed to the current date.This looks ok as now restore works. Whenever the restore operation fails the
database is shown in loading state.
"J Lee" wrote:

> There was a restore script executed against a test
> database that failed and left the database in loading
> state. I fixed the restore script and executed it again.
> I need confirmation if this is alright. I noticed the
> MDF and LDF files date changed to the current date.
>

DB in Loading State

There was a restore script executed against a test
database that failed and left the database in loading
state. I fixed the restore script and executed it again.
I need confirmation if this is alright. I noticed the
MDF and LDF files date changed to the current date.This looks ok as now restore works. Whenever the restore operation fails the
database is shown in loading state.
"J Lee" wrote:
> There was a restore script executed against a test
> database that failed and left the database in loading
> state. I fixed the restore script and executed it again.
> I need confirmation if this is alright. I noticed the
> MDF and LDF files date changed to the current date.
>

DB help needed

hi everyone..
i am seeing this error when connecting to the DB.

Login failed for user 'dbo'. Reason: Not associated with a trusted SQL Server connection.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Login failed for user 'dbo'. Reason: Not associated with a trusted SQL Server connection.

can anyone tell me wat is the problem?
thanks for any help..experiencing another error..
can anyone help?
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'h'

thanks|||This means you are referring to a non-existent column named h.

Please provide your code so we can help you to isolate the problem.

Terri|||thanks very much terri.
i have solved the problem..|||encountered this error while doin binding to datagrid
can anyone help me? thanks very much

* Error while binding data
General network error. Check your network documentation.
.Net SqlClient Data Provider

DB error...please help!

Hi
I have a DB running in SQLServer 2000 that has worked fine for ages.
However, a recent data load failed. We check the DB using 'dbcc checkdb'
and it reported errors. We fixed the DB using 'dbcc checkdb
(REPAIR_ALLOW_DATA_LOSS )' and this appeared to fix the problem. However,
the DB has since corrupted twice more within a week. CheckDB run on the
master DB shows no problems.
Error messages:
These have been fairly varied. The error we recieve when doing an update
is:
--
Error -2147467259 - I/O error (bad page ID) detected during read at offset
0x0000001f220000 in file 'd:\mssql\data\[myDBName].mdf'
(This is followed by a whole series of connection failure errors for each
connection attempted during the data upload.)
--
Other error messages include:
--
Server: Msg 3624, Level 20, State 1, Line 1
Location: S:\sql\ntdbms\storeng\drs\include\record.inl:1447
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 75
Process ID: 824
Connection Broken
--
When we correct the errors using CheckDB, we get the following example
messages (should you wish to read):
Table error: Object ID -1291825152, index ID 12336, page ID (1:74256). The
PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 33792, page ID (1:74258). The PageId in
the page header = (0:0).
The error has been repaired.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object
ID -1291825152)' (object ID -1291825152).
CHECKDB fixed 0 allocation errors and 1 consistency errors in table '(Object
ID -1291825152)' (object ID -1291825152).
DBCC results for '[myDataBaseName]'.
The error has been repaired.
CHECKDB found 0 allocation errors and 1 consistency errors not associated
with any single object.
CHECKDB fixed 0 allocation errors and 1 consistency errors not associated
with any single object.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 606625204, index ID 0: Page (1:74256) could not be processed. See
other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 606625204, index ID 0: Page (1:74257) could not be processed. See
other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 606625204, index ID 0: Page (1:74258) could not be processed. See
other errors for details.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 606625204, index ID 1. Page (1:74256) was not seen in
the scan although its parent (1:74322) and previous (1:74271) refer to it.
Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 606625204, index ID 1. Index node page (1:74322),
slot 32 refers to child page (1:74257) and previous child (1:74256), but
they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 606625204, index ID 1. Index node page (1:74322)
DBCC results for 'accountProducts'.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 606625204, index ID 1. Page (1:74259) is missing a
reference from previous page (1:74258). Possible chain linkage problem.
The error has been repaired.
The error has been repaired.
Repair: Page (1:74256) has been deallocated from object ID 606625204, index
ID 0.
Repair: Page (1:74257) has been deallocated from object ID 606625204, index
ID 0.
Repair: Page (1:74258) has been deallocated from object ID 606625204, index
ID 0.
There are 3930517 rows in 64635 pages for object 'accountProducts'.
CHECKDB found 0 allocation errors and 7 consistency errors in table
'accountProducts' (object ID 606625204).
CHECKDB fixed 0 allocation errors and 7 consistency errors in table
'accountProducts' (object ID 606625204).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1312043077, index ID 12341, page ID (1:74257). The
PageId in the page header = (0:1205993552).
There are 7602 rows in 54 pages for object 'crossSellingProducts'.
The error has been repaired.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object
ID 1312043077)' (object ID 1312043077).
CHECKDB fixed 0 allocation errors and 1 consistency errors in table '(Object
ID 1312043077)' (object ID 1312043077).
CHECKDB found 0 allocation errors and 10 consistency errors in database
'[myDBName]'.
CHECKDB fixed 0 allocation errors and 10 consistency errors in database
'[myDBName]'.
--
Any ideas what may be the problem? More importantly, what to do about it?
Many thanks in advance!
GriffHello,
After looking at your problem I think its somehow one or
more of your updates is currupting one of your clusters,
in turn its effecting your pages.
Personally I would examine the data closely and try the
50/50 approach, i.e. load in 50% of the data see if there
is an error of not 50% of the remaining data and so on.
I wish I could give you some more help, but please feel
free to email me on (in reverse order)
ku.oc.elcannip@.nalon.retep.
Peter
>--Original Message--
>Hi
>I have a DB running in SQLServer 2000 that has worked
fine for ages.
>However, a recent data load failed. We check the DB
using 'dbcc checkdb'
>and it reported errors. We fixed the DB using 'dbcc
checkdb
>(REPAIR_ALLOW_DATA_LOSS )' and this appeared to fix the
problem. However,
>the DB has since corrupted twice more within a week.
CheckDB run on the
>master DB shows no problems.
>Error messages:
>These have been fairly varied. The error we recieve when
doing an update
>is:
>--
>Error -2147467259 - I/O error (bad page ID) detected
during read at offset
>0x0000001f220000 in file 'd:\mssql\data\[myDBName].mdf'
>(This is followed by a whole series of connection failure
errors for each
>connection attempted during the data upload.)
>--
>Other error messages include:
>--
>Server: Msg 3624, Level 20, State 1, Line 1
>Location:
S:\sql\ntdbms\storeng\drs\include\record.inl:1447
>Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
>SPID: 75
>Process ID: 824
>Connection Broken
>--
>When we correct the errors using CheckDB, we get the
following example
>messages (should you wish to read):
>Table error: Object ID -1291825152, index ID 12336, page
ID (1:74256). The
>PageId in the page header = (0:0).
>Server: Msg 8909, Level 16, State 1, Line 1
>Table error: Object ID 0, index ID 33792, page ID
(1:74258). The PageId in
>the page header = (0:0).
> The error has been repaired.
>CHECKDB found 0 allocation errors and 1 consistency
errors in table '(Object
>ID -1291825152)' (object ID -1291825152).
>CHECKDB fixed 0 allocation errors and 1 consistency
errors in table '(Object
>ID -1291825152)' (object ID -1291825152).
>DBCC results for '[myDataBaseName]'.
> The error has been repaired.
>CHECKDB found 0 allocation errors and 1 consistency
errors not associated
>with any single object.
>CHECKDB fixed 0 allocation errors and 1 consistency
errors not associated
>with any single object.
>Server: Msg 8928, Level 16, State 1, Line 1
>Object ID 606625204, index ID 0: Page (1:74256) could not
be processed. See
>other errors for details.
>Server: Msg 8928, Level 16, State 1, Line 1
>Object ID 606625204, index ID 0: Page (1:74257) could not
be processed. See
>other errors for details.
>Server: Msg 8928, Level 16, State 1, Line 1
>Object ID 606625204, index ID 0: Page (1:74258) could not
be processed. See
>other errors for details.
>Server: Msg 8976, Level 16, State 1, Line 1
>Table error: Object ID 606625204, index ID 1. Page
(1:74256) was not seen in
>the scan although its parent (1:74322) and previous
(1:74271) refer to it.
>Check any previous errors.
>Server: Msg 8980, Level 16, State 1, Line 1
>Table error: Object ID 606625204, index ID 1. Index node
page (1:74322),
>slot 32 refers to child page (1:74257) and previous child
(1:74256), but
>they were not encountered.
>Server: Msg 8980, Level 16, State 1, Line 1
>Table error: Object ID 606625204, index ID 1. Index node
page (1:74322)
>
>DBCC results for 'accountProducts'.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
>Server: Msg 8978, Level 16, State 1, Line 1
>Table error: Object ID 606625204, index ID 1. Page
(1:74259) is missing a
>reference from previous page (1:74258). Possible chain
linkage problem.
> The error has been repaired.
> The error has been repaired.
>Repair: Page (1:74256) has been deallocated from object
ID 606625204, index
>ID 0.
>Repair: Page (1:74257) has been deallocated from object
ID 606625204, index
>ID 0.
>Repair: Page (1:74258) has been deallocated from object
ID 606625204, index
>ID 0.
>
>There are 3930517 rows in 64635 pages for
object 'accountProducts'.
>CHECKDB found 0 allocation errors and 7 consistency
errors in table
>'accountProducts' (object ID 606625204).
>CHECKDB fixed 0 allocation errors and 7 consistency
errors in table
>'accountProducts' (object ID 606625204).
>Server: Msg 8909, Level 16, State 1, Line 1
>Table error: Object ID 1312043077, index ID 12341, page
ID (1:74257). The
>PageId in the page header = (0:1205993552).
>There are 7602 rows in 54 pages for
object 'crossSellingProducts'.
> The error has been repaired.
>CHECKDB found 0 allocation errors and 1 consistency
errors in table '(Object
>ID 1312043077)' (object ID 1312043077).
>CHECKDB fixed 0 allocation errors and 1 consistency
errors in table '(Object
>ID 1312043077)' (object ID 1312043077).
>CHECKDB found 0 allocation errors and 10 consistency
errors in database
>'[myDBName]'.
>CHECKDB fixed 0 allocation errors and 10 consistency
errors in database
>'[myDBName]'.
>--
>Any ideas what may be the problem? More importantly,
what to do about it?
>Many thanks in advance!
>Griff
>
>.
>