Problems when performing RESTORE DATABASE on Windows XP Mediacenter with Intel Core Duo

Hi!
We have an application, which as a database server uses
MS SQL Server 2000 Desktop Engine (MSDE; SP3a version). One
of the application users reported that after he switched
computers (installed our application with MSDE on a new
computer with parameters mentioned in the message subject),
the application began to have problems with backup functionality.
The backup functionality of the application does only one
thing: it uses SQL-DMO interface to execute this TransactSQL:
"RESTORE DATABASE ...". The effect of that is one of two:
either the database is apparently restored, but the control
does not return to the application (so the application hangs),
or the database remains in "restoring" state (and the control
does not return to the application too) and is useless to
the user.
The question is: Do you know any possible causes and / or
solutions to this problems? I'd be grateful for any information.
The user did not send me the server log files yet. As soon
as I get them, I'll try to post anything interesting that
I find in them.
HilarionHi
Can you run the command from osql on this machine?
John
"Hilarion" wrote:
> Hi!
> We have an application, which as a database server uses
> MS SQL Server 2000 Desktop Engine (MSDE; SP3a version). One
> of the application users reported that after he switched
> computers (installed our application with MSDE on a new
> computer with parameters mentioned in the message subject),
> the application began to have problems with backup functionality.
> The backup functionality of the application does only one
> thing: it uses SQL-DMO interface to execute this TransactSQL:
> "RESTORE DATABASE ...". The effect of that is one of two:
> either the database is apparently restored, but the control
> does not return to the application (so the application hangs),
> or the database remains in "restoring" state (and the control
> does not return to the application too) and is useless to
> the user.
> The question is: Do you know any possible causes and / or
> solutions to this problems? I'd be grateful for any information.
> The user did not send me the server log files yet. As soon
> as I get them, I'll try to post anything interesting that
> I find in them.
> Hilarion
>|||Hilarion wrote:
> > We have an application, which as a database server uses
> > MS SQL Server 2000 Desktop Engine (MSDE; SP3a version). One
> > of the application users reported that after he switched
> > computers (installed our application with MSDE on a new
> > computer with parameters mentioned in the message subject),
> > the application began to have problems with backup functionality.
> > The backup functionality of the application does only one
> > thing: it uses SQL-DMO interface to execute this TransactSQL:
> > "RESTORE DATABASE ...". The effect of that is one of two:
> > either the database is apparently restored, but the control
> > does not return to the application (so the application hangs),
> > or the database remains in "restoring" state (and the control
> > does not return to the application too) and is useless to
> > the user.
> > The question is: Do you know any possible causes and / or
> > solutions to this problems? I'd be grateful for any information.
> > The user did not send me the server log files yet. As soon
> > as I get them, I'll try to post anything interesting that
> > I find in them.
John Bell wrote:
> Can you run the command from osql on this machine?
I have no direct access to the machine and not a very good contact
to the user, but I'll try to ask that user to try osql to perform
the restore operation. I'll post the results as soon as I get them.
Thank you for your suggestion. If you have any other ideas, then
please post them (do not wait for my reply on the "osql" use -
- it may take much time). Thank you in advance for any future
suggestions and any other help.
Hilarion|||Hi
Maybe it would be possible to use remote desktop or some other alternative
to get this tested? If you have an alternative backup file you could try then
it may be worth trying.
John
"Hilarion" wrote:
> Hilarion wrote:
> > > We have an application, which as a database server uses
> > > MS SQL Server 2000 Desktop Engine (MSDE; SP3a version). One
> > > of the application users reported that after he switched
> > > computers (installed our application with MSDE on a new
> > > computer with parameters mentioned in the message subject),
> > > the application began to have problems with backup functionality.
> > > The backup functionality of the application does only one
> > > thing: it uses SQL-DMO interface to execute this TransactSQL:
> > > "RESTORE DATABASE ...". The effect of that is one of two:
> > > either the database is apparently restored, but the control
> > > does not return to the application (so the application hangs),
> > > or the database remains in "restoring" state (and the control
> > > does not return to the application too) and is useless to
> > > the user.
> > > The question is: Do you know any possible causes and / or
> > > solutions to this problems? I'd be grateful for any information.
> > > The user did not send me the server log files yet. As soon
> > > as I get them, I'll try to post anything interesting that
> > > I find in them.
>
> John Bell wrote:
> > Can you run the command from osql on this machine?
> I have no direct access to the machine and not a very good contact
> to the user, but I'll try to ask that user to try osql to perform
> the restore operation. I'll post the results as soon as I get them.
> Thank you for your suggestion. If you have any other ideas, then
> please post them (do not wait for my reply on the "osql" use -
> - it may take much time). Thank you in advance for any future
> suggestions and any other help.
> Hilarion
>