I have the following error on executing a. asp file which uploads a file
into a 2005 SQL DB.
Take note that the SQL server and IIS resides in the same server.
Mcrosoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find se
rver
'servername' in sysservers. Execute sp_addlinkedserver to add the server to
sysservers.Hi Monica
You can use SQL Profiler to see the statements you are sending to the server
.
If the server has been renamed check out
http://support.microsoft.com/kb/303774.
John
"Monica" wrote:
> I have the following error on executing a. asp file which uploads a file
> into a 2005 SQL DB.
> Take note that the SQL server and IIS resides in the same server.
> --
> Mcrosoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find
server
> 'servername' in sysservers. Execute sp_addlinkedserver to add the server t
o
> sysservers.
> --
>
>|||hi John,
Is this also an issue even if the server was renamed even before I created
the DB? BTW, the Db came from a SQL 2000 version that was working fine, but
had this problem when I restored in the 2005 version.
Thanks,
Monica
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:FEB13C42-80EC-4218-B5F0-E6B2C0E841BD@.microsoft.com...[vbcol=seagreen]
> Hi Monica
> You can use SQL Profiler to see the statements you are sending to the
> server.
> If the server has been renamed check out
> http://support.microsoft.com/kb/303774.
> John
> "Monica" wrote:
>|||Hi Monica
This is a problem with the server and not the database. If you have not
renamed the SQL 2005 Server then you should not have this problem. Checking
@.@.SERVERNAME will show if you have this problem also check out "Hot to:
Rename a Stand-alone Instance of SQL Server 2005" in books online for more
information.
If @.@.SERVERNAME is correct you may have some SQL that is not compatible with
SQL 2005, this can be checked by running SQL Profiler.
John
"Monica" wrote:
> hi John,
> Is this also an issue even if the server was renamed even before I created
> the DB? BTW, the Db came from a SQL 2000 version that was working fine, b
ut
> had this problem when I restored in the 2005 version.
> Thanks,
> Monica
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:FEB13C42-80EC-4218-B5F0-E6B2C0E841BD@.microsoft.com...
>
>|||Hi John,
Now I have this error message,
Microsoft OLE DB Provider for ODBC Drivers error '80040e23'
[Microsoft][ODBC SQL Server Driver][SQL Server]The cursor does n
ot include
the table being modified or the table is not updatable through the cursor.
What does this mean?
Monica
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:3C74BC77-EF9F-4063-A26E-2110688DB2A5@.microsoft.com...[vbcol=seagreen]
> Hi Monica
> This is a problem with the server and not the database. If you have not
> renamed the SQL 2005 Server then you should not have this problem.
> Checking
> @.@.SERVERNAME will show if you have this problem also check out "Hot to:
> Rename a Stand-alone Instance of SQL Server 2005" in books online for more
> information.
> If @.@.SERVERNAME is correct you may have some SQL that is not compatible
> with
> SQL 2005, this can be checked by running SQL Profiler.
> John
>
> "Monica" wrote:
>|||Hi Monica
This sounds a bit like http://support.microsoft.com//kb/290413 although it
will not apply to your version, it could be something to do with how you are
forming your SQL statements, can you pinpoint the statement with SQL profile
r?
John
"Monica" wrote:
> Hi John,
> Now I have this error message,
> Microsoft OLE DB Provider for ODBC Drivers error '80040e23'
> [Microsoft][ODBC SQL Server Driver][SQL Server]The cursor does
not include
> the table being modified or the table is not updatable through the cursor.
> What does this mean?
>
> Monica
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:3C74BC77-EF9F-4063-A26E-2110688DB2A5@.microsoft.com...
>
>
Showing posts with label note. Show all posts
Showing posts with label note. Show all posts
Wednesday, March 21, 2012
error '80004005' on .asp
I have the following error on executing a. asp file which uploads a file
into a 2005 SQL DB.
Take note that the SQL server and IIS resides in the same server.
--
Mcrosoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server
'servername' in sysservers. Execute sp_addlinkedserver to add the server to
sysservers.
--Hi Monica
You can use SQL Profiler to see the statements you are sending to the server.
If the server has been renamed check out
http://support.microsoft.com/kb/303774.
John
"Monica" wrote:
> I have the following error on executing a. asp file which uploads a file
> into a 2005 SQL DB.
> Take note that the SQL server and IIS resides in the same server.
> --
> Mcrosoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server
> 'servername' in sysservers. Execute sp_addlinkedserver to add the server to
> sysservers.
> --
>
>|||hi John,
Is this also an issue even if the server was renamed even before I created
the DB? BTW, the Db came from a SQL 2000 version that was working fine, but
had this problem when I restored in the 2005 version.
Thanks,
Monica
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:FEB13C42-80EC-4218-B5F0-E6B2C0E841BD@.microsoft.com...
> Hi Monica
> You can use SQL Profiler to see the statements you are sending to the
> server.
> If the server has been renamed check out
> http://support.microsoft.com/kb/303774.
> John
> "Monica" wrote:
>> I have the following error on executing a. asp file which uploads a file
>> into a 2005 SQL DB.
>> Take note that the SQL server and IIS resides in the same server.
>> --
>> Mcrosoft OLE DB Provider for ODBC Drivers error '80004005'
>> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server
>> 'servername' in sysservers. Execute sp_addlinkedserver to add the server
>> to
>> sysservers.
>> --
>>|||Hi Monica
This is a problem with the server and not the database. If you have not
renamed the SQL 2005 Server then you should not have this problem. Checking
@.@.SERVERNAME will show if you have this problem also check out "Hot to:
Rename a Stand-alone Instance of SQL Server 2005" in books online for more
information.
If @.@.SERVERNAME is correct you may have some SQL that is not compatible with
SQL 2005, this can be checked by running SQL Profiler.
John
"Monica" wrote:
> hi John,
> Is this also an issue even if the server was renamed even before I created
> the DB? BTW, the Db came from a SQL 2000 version that was working fine, but
> had this problem when I restored in the 2005 version.
> Thanks,
> Monica
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:FEB13C42-80EC-4218-B5F0-E6B2C0E841BD@.microsoft.com...
> > Hi Monica
> >
> > You can use SQL Profiler to see the statements you are sending to the
> > server.
> >
> > If the server has been renamed check out
> > http://support.microsoft.com/kb/303774.
> >
> > John
> >
> > "Monica" wrote:
> >
> >> I have the following error on executing a. asp file which uploads a file
> >> into a 2005 SQL DB.
> >>
> >> Take note that the SQL server and IIS resides in the same server.
> >>
> >> --
> >>
> >> Mcrosoft OLE DB Provider for ODBC Drivers error '80004005'
> >> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server
> >> 'servername' in sysservers. Execute sp_addlinkedserver to add the server
> >> to
> >> sysservers.
> >>
> >> --
> >>
> >>
> >>
>
>|||Hi John,
Now I have this error message,
Microsoft OLE DB Provider for ODBC Drivers error '80040e23'
[Microsoft][ODBC SQL Server Driver][SQL Server]The cursor does not include
the table being modified or the table is not updatable through the cursor.
What does this mean?
Monica
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:3C74BC77-EF9F-4063-A26E-2110688DB2A5@.microsoft.com...
> Hi Monica
> This is a problem with the server and not the database. If you have not
> renamed the SQL 2005 Server then you should not have this problem.
> Checking
> @.@.SERVERNAME will show if you have this problem also check out "Hot to:
> Rename a Stand-alone Instance of SQL Server 2005" in books online for more
> information.
> If @.@.SERVERNAME is correct you may have some SQL that is not compatible
> with
> SQL 2005, this can be checked by running SQL Profiler.
> John
>
> "Monica" wrote:
>> hi John,
>> Is this also an issue even if the server was renamed even before I
>> created
>> the DB? BTW, the Db came from a SQL 2000 version that was working fine,
>> but
>> had this problem when I restored in the 2005 version.
>> Thanks,
>> Monica
>> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
>> news:FEB13C42-80EC-4218-B5F0-E6B2C0E841BD@.microsoft.com...
>> > Hi Monica
>> >
>> > You can use SQL Profiler to see the statements you are sending to the
>> > server.
>> >
>> > If the server has been renamed check out
>> > http://support.microsoft.com/kb/303774.
>> >
>> > John
>> >
>> > "Monica" wrote:
>> >
>> >> I have the following error on executing a. asp file which uploads a
>> >> file
>> >> into a 2005 SQL DB.
>> >>
>> >> Take note that the SQL server and IIS resides in the same server.
>> >>
>> >> --
>> >>
>> >> Mcrosoft OLE DB Provider for ODBC Drivers error '80004005'
>> >> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server
>> >> 'servername' in sysservers. Execute sp_addlinkedserver to add the
>> >> server
>> >> to
>> >> sysservers.
>> >>
>> >> --
>> >>
>> >>
>> >>
>>|||Hi Monica
This sounds a bit like http://support.microsoft.com//kb/290413 although it
will not apply to your version, it could be something to do with how you are
forming your SQL statements, can you pinpoint the statement with SQL profiler?
John
"Monica" wrote:
> Hi John,
> Now I have this error message,
> Microsoft OLE DB Provider for ODBC Drivers error '80040e23'
> [Microsoft][ODBC SQL Server Driver][SQL Server]The cursor does not include
> the table being modified or the table is not updatable through the cursor.
> What does this mean?
>
> Monica
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:3C74BC77-EF9F-4063-A26E-2110688DB2A5@.microsoft.com...
> > Hi Monica
> >
> > This is a problem with the server and not the database. If you have not
> > renamed the SQL 2005 Server then you should not have this problem.
> > Checking
> > @.@.SERVERNAME will show if you have this problem also check out "Hot to:
> > Rename a Stand-alone Instance of SQL Server 2005" in books online for more
> > information.
> >
> > If @.@.SERVERNAME is correct you may have some SQL that is not compatible
> > with
> > SQL 2005, this can be checked by running SQL Profiler.
> >
> > John
> >
> >
> > "Monica" wrote:
> >
> >> hi John,
> >>
> >> Is this also an issue even if the server was renamed even before I
> >> created
> >> the DB? BTW, the Db came from a SQL 2000 version that was working fine,
> >> but
> >> had this problem when I restored in the 2005 version.
> >>
> >> Thanks,
> >> Monica
> >>
> >> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> >> news:FEB13C42-80EC-4218-B5F0-E6B2C0E841BD@.microsoft.com...
> >> > Hi Monica
> >> >
> >> > You can use SQL Profiler to see the statements you are sending to the
> >> > server.
> >> >
> >> > If the server has been renamed check out
> >> > http://support.microsoft.com/kb/303774.
> >> >
> >> > John
> >> >
> >> > "Monica" wrote:
> >> >
> >> >> I have the following error on executing a. asp file which uploads a
> >> >> file
> >> >> into a 2005 SQL DB.
> >> >>
> >> >> Take note that the SQL server and IIS resides in the same server.
> >> >>
> >> >> --
> >> >>
> >> >> Mcrosoft OLE DB Provider for ODBC Drivers error '80004005'
> >> >> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server
> >> >> 'servername' in sysservers. Execute sp_addlinkedserver to add the
> >> >> server
> >> >> to
> >> >> sysservers.
> >> >>
> >> >> --
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
into a 2005 SQL DB.
Take note that the SQL server and IIS resides in the same server.
--
Mcrosoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server
'servername' in sysservers. Execute sp_addlinkedserver to add the server to
sysservers.
--Hi Monica
You can use SQL Profiler to see the statements you are sending to the server.
If the server has been renamed check out
http://support.microsoft.com/kb/303774.
John
"Monica" wrote:
> I have the following error on executing a. asp file which uploads a file
> into a 2005 SQL DB.
> Take note that the SQL server and IIS resides in the same server.
> --
> Mcrosoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server
> 'servername' in sysservers. Execute sp_addlinkedserver to add the server to
> sysservers.
> --
>
>|||hi John,
Is this also an issue even if the server was renamed even before I created
the DB? BTW, the Db came from a SQL 2000 version that was working fine, but
had this problem when I restored in the 2005 version.
Thanks,
Monica
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:FEB13C42-80EC-4218-B5F0-E6B2C0E841BD@.microsoft.com...
> Hi Monica
> You can use SQL Profiler to see the statements you are sending to the
> server.
> If the server has been renamed check out
> http://support.microsoft.com/kb/303774.
> John
> "Monica" wrote:
>> I have the following error on executing a. asp file which uploads a file
>> into a 2005 SQL DB.
>> Take note that the SQL server and IIS resides in the same server.
>> --
>> Mcrosoft OLE DB Provider for ODBC Drivers error '80004005'
>> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server
>> 'servername' in sysservers. Execute sp_addlinkedserver to add the server
>> to
>> sysservers.
>> --
>>|||Hi Monica
This is a problem with the server and not the database. If you have not
renamed the SQL 2005 Server then you should not have this problem. Checking
@.@.SERVERNAME will show if you have this problem also check out "Hot to:
Rename a Stand-alone Instance of SQL Server 2005" in books online for more
information.
If @.@.SERVERNAME is correct you may have some SQL that is not compatible with
SQL 2005, this can be checked by running SQL Profiler.
John
"Monica" wrote:
> hi John,
> Is this also an issue even if the server was renamed even before I created
> the DB? BTW, the Db came from a SQL 2000 version that was working fine, but
> had this problem when I restored in the 2005 version.
> Thanks,
> Monica
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:FEB13C42-80EC-4218-B5F0-E6B2C0E841BD@.microsoft.com...
> > Hi Monica
> >
> > You can use SQL Profiler to see the statements you are sending to the
> > server.
> >
> > If the server has been renamed check out
> > http://support.microsoft.com/kb/303774.
> >
> > John
> >
> > "Monica" wrote:
> >
> >> I have the following error on executing a. asp file which uploads a file
> >> into a 2005 SQL DB.
> >>
> >> Take note that the SQL server and IIS resides in the same server.
> >>
> >> --
> >>
> >> Mcrosoft OLE DB Provider for ODBC Drivers error '80004005'
> >> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server
> >> 'servername' in sysservers. Execute sp_addlinkedserver to add the server
> >> to
> >> sysservers.
> >>
> >> --
> >>
> >>
> >>
>
>|||Hi John,
Now I have this error message,
Microsoft OLE DB Provider for ODBC Drivers error '80040e23'
[Microsoft][ODBC SQL Server Driver][SQL Server]The cursor does not include
the table being modified or the table is not updatable through the cursor.
What does this mean?
Monica
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:3C74BC77-EF9F-4063-A26E-2110688DB2A5@.microsoft.com...
> Hi Monica
> This is a problem with the server and not the database. If you have not
> renamed the SQL 2005 Server then you should not have this problem.
> Checking
> @.@.SERVERNAME will show if you have this problem also check out "Hot to:
> Rename a Stand-alone Instance of SQL Server 2005" in books online for more
> information.
> If @.@.SERVERNAME is correct you may have some SQL that is not compatible
> with
> SQL 2005, this can be checked by running SQL Profiler.
> John
>
> "Monica" wrote:
>> hi John,
>> Is this also an issue even if the server was renamed even before I
>> created
>> the DB? BTW, the Db came from a SQL 2000 version that was working fine,
>> but
>> had this problem when I restored in the 2005 version.
>> Thanks,
>> Monica
>> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
>> news:FEB13C42-80EC-4218-B5F0-E6B2C0E841BD@.microsoft.com...
>> > Hi Monica
>> >
>> > You can use SQL Profiler to see the statements you are sending to the
>> > server.
>> >
>> > If the server has been renamed check out
>> > http://support.microsoft.com/kb/303774.
>> >
>> > John
>> >
>> > "Monica" wrote:
>> >
>> >> I have the following error on executing a. asp file which uploads a
>> >> file
>> >> into a 2005 SQL DB.
>> >>
>> >> Take note that the SQL server and IIS resides in the same server.
>> >>
>> >> --
>> >>
>> >> Mcrosoft OLE DB Provider for ODBC Drivers error '80004005'
>> >> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server
>> >> 'servername' in sysservers. Execute sp_addlinkedserver to add the
>> >> server
>> >> to
>> >> sysservers.
>> >>
>> >> --
>> >>
>> >>
>> >>
>>|||Hi Monica
This sounds a bit like http://support.microsoft.com//kb/290413 although it
will not apply to your version, it could be something to do with how you are
forming your SQL statements, can you pinpoint the statement with SQL profiler?
John
"Monica" wrote:
> Hi John,
> Now I have this error message,
> Microsoft OLE DB Provider for ODBC Drivers error '80040e23'
> [Microsoft][ODBC SQL Server Driver][SQL Server]The cursor does not include
> the table being modified or the table is not updatable through the cursor.
> What does this mean?
>
> Monica
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:3C74BC77-EF9F-4063-A26E-2110688DB2A5@.microsoft.com...
> > Hi Monica
> >
> > This is a problem with the server and not the database. If you have not
> > renamed the SQL 2005 Server then you should not have this problem.
> > Checking
> > @.@.SERVERNAME will show if you have this problem also check out "Hot to:
> > Rename a Stand-alone Instance of SQL Server 2005" in books online for more
> > information.
> >
> > If @.@.SERVERNAME is correct you may have some SQL that is not compatible
> > with
> > SQL 2005, this can be checked by running SQL Profiler.
> >
> > John
> >
> >
> > "Monica" wrote:
> >
> >> hi John,
> >>
> >> Is this also an issue even if the server was renamed even before I
> >> created
> >> the DB? BTW, the Db came from a SQL 2000 version that was working fine,
> >> but
> >> had this problem when I restored in the 2005 version.
> >>
> >> Thanks,
> >> Monica
> >>
> >> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> >> news:FEB13C42-80EC-4218-B5F0-E6B2C0E841BD@.microsoft.com...
> >> > Hi Monica
> >> >
> >> > You can use SQL Profiler to see the statements you are sending to the
> >> > server.
> >> >
> >> > If the server has been renamed check out
> >> > http://support.microsoft.com/kb/303774.
> >> >
> >> > John
> >> >
> >> > "Monica" wrote:
> >> >
> >> >> I have the following error on executing a. asp file which uploads a
> >> >> file
> >> >> into a 2005 SQL DB.
> >> >>
> >> >> Take note that the SQL server and IIS resides in the same server.
> >> >>
> >> >> --
> >> >>
> >> >> Mcrosoft OLE DB Provider for ODBC Drivers error '80004005'
> >> >> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server
> >> >> 'servername' in sysservers. Execute sp_addlinkedserver to add the
> >> >> server
> >> >> to
> >> >> sysservers.
> >> >>
> >> >> --
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
Friday, February 17, 2012
Error -2147217900: failed to create SQL database
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...
>
>
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:
>
>
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:
>
>
Subscribe to:
Posts (Atom)