can't backup - urgent

Hi,
When I do the backup and click on the add button, an error come
out:
Microsoft SQL-DMO (ODBC SQLSTATE: 42000)
Error 0: Cannot load the DLL xpstar.dll , or one of the DLLs it references.
Reason:998 (invalid access to memory location)
Please help. I cannot do the backup now. Thanks.
Allen,
Have you tried running the backup from Query Analyzer instead of Enterprise
Manager, using the BACKUP DATABASE syntax? I don't know what that error
means, but don't let the UI's failure to respond stop you...
""Allen Iverson"" <no_spam@.bk.com> wrote in message
news:eGZiOvbqEHA.2856@.TK2MSFTNGP10.phx.gbl...
> Hi,
> When I do the backup and click on the add button, an error come
> out:
> Microsoft SQL-DMO (ODBC SQLSTATE: 42000)
> Error 0: Cannot load the DLL xpstar.dll , or one of the DLLs it
references.
> Reason:998 (invalid access to memory location)
>
> Please help. I cannot do the backup now. Thanks.
>
|||Hi,
Should be MDAC issue. But as an immediate solution execute the backup
database command from query analyzer for backup.
Backup database <dbname> to disk='c:\backup\dbname.bak' with init,stats=10
After the backup, First update the SQL server by SP3a (latest service pack)
and try backup from Enterprise manager.
If you still have issues try updating latest MDAC
Thanks
Hari
MCDBA
""Allen Iverson"" <no_spam@.bk.com> wrote in message
news:eGZiOvbqEHA.2856@.TK2MSFTNGP10.phx.gbl...
> Hi,
> When I do the backup and click on the add button, an error come
> out:
> Microsoft SQL-DMO (ODBC SQLSTATE: 42000)
> Error 0: Cannot load the DLL xpstar.dll , or one of the DLLs it
> references. Reason:998 (invalid access to memory location)
>
> Please help. I cannot do the backup now. Thanks.
>
|||Hari and Adam,
This SQL server has already been applied SP3a long time ago.
Last week we got no problem to do the daily backup. But it suddenly happened
this morning. Any clue. I will try the query analyzer now. Thanks.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:OfRez2bqEHA.1272@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Should be MDAC issue. But as an immediate solution execute the backup
> database command from query analyzer for backup.
> Backup database <dbname> to disk='c:\backup\dbname.bak' with init,stats=10
> After the backup, First update the SQL server by SP3a (latest service
> pack) and try backup from Enterprise manager.
> If you still have issues try updating latest MDAC
> Thanks
> Hari
> MCDBA
>
>
> ""Allen Iverson"" <no_spam@.bk.com> wrote in message
> news:eGZiOvbqEHA.2856@.TK2MSFTNGP10.phx.gbl...
>
|||> This SQL server has already been applied SP3a long time ago.
So some other program with an improper install program or version DLL checking might mess thing up
for the SQL Server. This is why Hari suggested to *reinstall* sp 3, so it might sort things out for
you.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
""Allen Iverson"" <no_spam@.bk.com> wrote in message news:OhY6AGcqEHA.3592@.TK2MSFTNGP14.phx.gbl...
> Hari and Adam,
> This SQL server has already been applied SP3a long time ago. Last week we got no
> problem to do the daily backup. But it suddenly happened this morning. Any clue. I will try the
> query analyzer now. Thanks.
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:OfRez2bqEHA.1272@.TK2MSFTNGP09.phx.gbl...
>
|||I see. Will this re-apply cause any impact or conflict? Do I need to reboot
the server after? THanks.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OBI6zYdqEHA.3172@.TK2MSFTNGP10.phx.gbl...
> So some other program with an improper install program or version DLL
> checking might mess thing up for the SQL Server. This is why Hari
> suggested to *reinstall* sp 3, so it might sort things out for you.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> ""Allen Iverson"" <no_spam@.bk.com> wrote in message
> news:OhY6AGcqEHA.3592@.TK2MSFTNGP14.phx.gbl...
>

can't backup - urgent

Hi,
When I do the backup and click on the add button, an error come
out:
Microsoft SQL-DMO (ODBC SQLSTATE: 42000)
Error 0: Cannot load the DLL xpstar.dll , or one of the DLLs it references.
Reason:998 (invalid access to memory location)
Please help. I cannot do the backup now. Thanks.Allen,
Have you tried running the backup from Query Analyzer instead of Enterprise
Manager, using the BACKUP DATABASE syntax? I don't know what that error
means, but don't let the UI's failure to respond stop you...
""Allen Iverson"" <no_spam@.bk.com> wrote in message
news:eGZiOvbqEHA.2856@.TK2MSFTNGP10.phx.gbl...
> Hi,
> When I do the backup and click on the add button, an error come
> out:
> Microsoft SQL-DMO (ODBC SQLSTATE: 42000)
> Error 0: Cannot load the DLL xpstar.dll , or one of the DLLs it
references.
> Reason:998 (invalid access to memory location)
>
> Please help. I cannot do the backup now. Thanks.
>|||Hi,
Should be MDAC issue. But as an immediate solution execute the backup
database command from query analyzer for backup.
Backup database <dbname> to disk='c:\backup\dbname.bak' with init,stats=10
After the backup, First update the SQL server by SP3a (latest service pack)
and try backup from Enterprise manager.
If you still have issues try updating latest MDAC
Thanks
Hari
MCDBA
""Allen Iverson"" <no_spam@.bk.com> wrote in message
news:eGZiOvbqEHA.2856@.TK2MSFTNGP10.phx.gbl...
> Hi,
> When I do the backup and click on the add button, an error come
> out:
> Microsoft SQL-DMO (ODBC SQLSTATE: 42000)
> Error 0: Cannot load the DLL xpstar.dll , or one of the DLLs it
> references. Reason:998 (invalid access to memory location)
>
> Please help. I cannot do the backup now. Thanks.
>|||Hari and Adam,
This SQL server has already been applied SP3a long time ago.
Last week we got no problem to do the daily backup. But it suddenly happened
this morning. Any clue. I will try the query analyzer now. Thanks.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:OfRez2bqEHA.1272@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Should be MDAC issue. But as an immediate solution execute the backup
> database command from query analyzer for backup.
> Backup database <dbname> to disk='c:\backup\dbname.bak' with init,stats=10
> After the backup, First update the SQL server by SP3a (latest service
> pack) and try backup from Enterprise manager.
> If you still have issues try updating latest MDAC
> Thanks
> Hari
> MCDBA
>
>
> ""Allen Iverson"" <no_spam@.bk.com> wrote in message
> news:eGZiOvbqEHA.2856@.TK2MSFTNGP10.phx.gbl...
>> Hi,
>> When I do the backup and click on the add button, an error come
>> out:
>> Microsoft SQL-DMO (ODBC SQLSTATE: 42000)
>> Error 0: Cannot load the DLL xpstar.dll , or one of the DLLs it
>> references. Reason:998 (invalid access to memory location)
>>
>> Please help. I cannot do the backup now. Thanks.
>|||> This SQL server has already been applied SP3a long time ago.
So some other program with an improper install program or version DLL checking might mess thing up
for the SQL Server. This is why Hari suggested to *reinstall* sp 3, so it might sort things out for
you.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
""Allen Iverson"" <no_spam@.bk.com> wrote in message news:OhY6AGcqEHA.3592@.TK2MSFTNGP14.phx.gbl...
> Hari and Adam,
> This SQL server has already been applied SP3a long time ago. Last week we got no
> problem to do the daily backup. But it suddenly happened this morning. Any clue. I will try the
> query analyzer now. Thanks.
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:OfRez2bqEHA.1272@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> Should be MDAC issue. But as an immediate solution execute the backup database command from
>> query analyzer for backup.
>> Backup database <dbname> to disk='c:\backup\dbname.bak' with init,stats=10
>> After the backup, First update the SQL server by SP3a (latest service pack) and try backup from
>> Enterprise manager.
>> If you still have issues try updating latest MDAC
>> Thanks
>> Hari
>> MCDBA
>>
>>
>> ""Allen Iverson"" <no_spam@.bk.com> wrote in message news:eGZiOvbqEHA.2856@.TK2MSFTNGP10.phx.gbl...
>> Hi,
>> When I do the backup and click on the add button, an error come out:
>> Microsoft SQL-DMO (ODBC SQLSTATE: 42000)
>> Error 0: Cannot load the DLL xpstar.dll , or one of the DLLs it references. Reason:998 (invalid
>> access to memory location)
>>
>> Please help. I cannot do the backup now. Thanks.
>>
>|||I see. Will this re-apply cause any impact or conflict? Do I need to reboot
the server after? THanks.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OBI6zYdqEHA.3172@.TK2MSFTNGP10.phx.gbl...
>> This SQL server has already been applied SP3a long time ago.
> So some other program with an improper install program or version DLL
> checking might mess thing up for the SQL Server. This is why Hari
> suggested to *reinstall* sp 3, so it might sort things out for you.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> ""Allen Iverson"" <no_spam@.bk.com> wrote in message
> news:OhY6AGcqEHA.3592@.TK2MSFTNGP14.phx.gbl...
>> Hari and Adam,
>> This SQL server has already been applied SP3a long time ago.
>> Last week we got no problem to do the daily backup. But it suddenly
>> happened this morning. Any clue. I will try the query analyzer now.
>> Thanks.
>>
>> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
>> news:OfRez2bqEHA.1272@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> Should be MDAC issue. But as an immediate solution execute the backup
>> database command from query analyzer for backup.
>> Backup database <dbname> to disk='c:\backup\dbname.bak' with
>> init,stats=10
>> After the backup, First update the SQL server by SP3a (latest service
>> pack) and try backup from Enterprise manager.
>> If you still have issues try updating latest MDAC
>> Thanks
>> Hari
>> MCDBA
>>
>>
>> ""Allen Iverson"" <no_spam@.bk.com> wrote in message
>> news:eGZiOvbqEHA.2856@.TK2MSFTNGP10.phx.gbl...
>> Hi,
>> When I do the backup and click on the add button, an error
>> come out:
>> Microsoft SQL-DMO (ODBC SQLSTATE: 42000)
>> Error 0: Cannot load the DLL xpstar.dll , or one of the DLLs it
>> references. Reason:998 (invalid access to memory location)
>>
>> Please help. I cannot do the backup now. Thanks.
>>
>>
>sql

Cannot view log for SQL Agent job (SQL2005)

Hi,
I've set up jobs and output files in SQL2005. When the job is completed, I
would like to check the output file by clicking VIEW button. However, the
button is grey-out.
The owner of the job is sa. What is other permission I missed ?
Thanks.
Hi Johnny
"Johnny" wrote:

> Hi,
> I've set up jobs and output files in SQL2005. When the job is completed, I
> would like to check the output file by clicking VIEW button. However, the
> button is grey-out.
> The owner of the job is sa. What is other permission I missed ?
> Thanks.
According to Books Online it is not available in SQL 2005
From Books Online:
View
In Microsoft SQL Server 2005, this button is disabled for viewing output
files. Instead, use Notepad to view job step output files. In Microsoft SQL
Server 2000, this launches Notepad to view the output file.
John
|||Hi John,
Thank you. Why leave the button there ?
Regards,
Johnny
"John Bell" wrote:

> Hi Johnny
> "Johnny" wrote:
> According to Books Online it is not available in SQL 2005
> From Books Online:
> View
> In Microsoft SQL Server 2005, this button is disabled for viewing output
> files. Instead, use Notepad to view job step output files. In Microsoft SQL
> Server 2000, this launches Notepad to view the output file.
>
> John
>
|||Hi Johnny
"Johnny" wrote:
[vbcol=seagreen]
> Hi John,
> Thank you. Why leave the button there ?
> Regards,
> Johnny
> "John Bell" wrote:
I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
will bring up the log file in Notepad!!!!
John
|||Yes, I always check the output file for any jobs in SQL2000 Agent job.
"John Bell" wrote:

> Hi Johnny
> "Johnny" wrote:
>
> I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
> will bring up the log file in Notepad!!!!
> John
|||"John Bell" wrote:
> I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
> will bring up the log file in Notepad!!!!
> John
And it does!!
John

Cannot view log for SQL Agent job (SQL2005)

Hi,
I've set up jobs and output files in SQL2005. When the job is completed, I
would like to check the output file by clicking VIEW button. However, the
button is grey-out.
The owner of the job is sa. What is other permission I missed ?
Thanks.Hi Johnny
"Johnny" wrote:

> Hi,
> I've set up jobs and output files in SQL2005. When the job is completed,
I
> would like to check the output file by clicking VIEW button. However, the
> button is grey-out.
> The owner of the job is sa. What is other permission I missed ?
> Thanks.
According to Books Online it is not available in SQL 2005
From Books Online:
View
In Microsoft SQL Server 2005, this button is disabled for viewing output
files. Instead, use Notepad to view job step output files. In Microsoft SQL
Server 2000, this launches Notepad to view the output file.
John|||Hi John,
Thank you. Why leave the button there ?
Regards,
Johnny
"John Bell" wrote:

> Hi Johnny
> "Johnny" wrote:
>
> According to Books Online it is not available in SQL 2005
> From Books Online:
> View
> In Microsoft SQL Server 2005, this button is disabled for viewing output
> files. Instead, use Notepad to view job step output files. In Microsoft SQ
L
> Server 2000, this launches Notepad to view the output file.
>
> John
>|||Hi Johnny
"Johnny" wrote:
[vbcol=seagreen]
> Hi John,
> Thank you. Why leave the button there ?
> Regards,
> Johnny
> "John Bell" wrote:
>
I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
will bring up the log file in Notepad!!!!
John|||Yes, I always check the output file for any jobs in SQL2000 Agent job.
"John Bell" wrote:

> Hi Johnny
> "Johnny" wrote:
>
> I guess that if you are looking at a SQL 2000 instance of SQL Agent then i
t
> will bring up the log file in Notepad!!!!
> John|||"John Bell" wrote:
> I guess that if you are looking at a SQL 2000 instance of SQL Agent then i
t
> will bring up the log file in Notepad!!!!
> John
And it does!!
John

Cannot view log for SQL Agent job (SQL2005)

Hi,
I've set up jobs and output files in SQL2005. When the job is completed, I
would like to check the output file by clicking VIEW button. However, the
button is grey-out.
The owner of the job is sa. What is other permission I missed ?
Thanks.Hi Johnny
"Johnny" wrote:
> Hi,
> I've set up jobs and output files in SQL2005. When the job is completed, I
> would like to check the output file by clicking VIEW button. However, the
> button is grey-out.
> The owner of the job is sa. What is other permission I missed ?
> Thanks.
According to Books Online it is not available in SQL 2005
From Books Online:
View
In Microsoft SQL Server 2005, this button is disabled for viewing output
files. Instead, use Notepad to view job step output files. In Microsoft SQL
Server 2000, this launches Notepad to view the output file.
John|||Hi John,
Thank you. Why leave the button there ?
Regards,
Johnny
"John Bell" wrote:
> Hi Johnny
> "Johnny" wrote:
> > Hi,
> >
> > I've set up jobs and output files in SQL2005. When the job is completed, I
> > would like to check the output file by clicking VIEW button. However, the
> > button is grey-out.
> >
> > The owner of the job is sa. What is other permission I missed ?
> >
> > Thanks.
> According to Books Online it is not available in SQL 2005
> From Books Online:
> View
> In Microsoft SQL Server 2005, this button is disabled for viewing output
> files. Instead, use Notepad to view job step output files. In Microsoft SQL
> Server 2000, this launches Notepad to view the output file.
>
> John
>|||Hi Johnny
"Johnny" wrote:
> Hi John,
> Thank you. Why leave the button there ?
> Regards,
> Johnny
> "John Bell" wrote:
> > According to Books Online it is not available in SQL 2005
> >
> > From Books Online:
> >
> > View
> > In Microsoft SQL Server 2005, this button is disabled for viewing output
> > files. Instead, use Notepad to view job step output files. In Microsoft SQL
> > Server 2000, this launches Notepad to view the output file.
> >
> >
> > John
> >
I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
will bring up the log file in Notepad!!!!
John|||Yes, I always check the output file for any jobs in SQL2000 Agent job.
"John Bell" wrote:
> Hi Johnny
> "Johnny" wrote:
> > Hi John,
> >
> > Thank you. Why leave the button there ?
> >
> > Regards,
> > Johnny
> >
> > "John Bell" wrote:
> >
> > > According to Books Online it is not available in SQL 2005
> > >
> > > From Books Online:
> > >
> > > View
> > > In Microsoft SQL Server 2005, this button is disabled for viewing output
> > > files. Instead, use Notepad to view job step output files. In Microsoft SQL
> > > Server 2000, this launches Notepad to view the output file.
> > >
> > >
> > > John
> > >
> I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
> will bring up the log file in Notepad!!!!
> John|||"John Bell" wrote:
> I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
> will bring up the log file in Notepad!!!!
> John
And it does!!
John

Cannot Update Records that contain NULL Values!

Hi,

I am trying to use a formView with an update button to update individual records in an sql database. (when i click update it doesnt perform the update and just refreshes the page. ) One of the fields in my records is a NULL - this is also one of the fields that i need to update. When i manually go into the database and enter some data, and then go back to my form, it updates fine, but as soon as i delete the data from the field, it returns to NULL and im back to square one.

Any Ideas on how to get around this problem?

THanks

Then what's wrong? Since you delete the data from the field, it should be set to NULL. What do you expect to get after deleting the data? And what's meaing of "im back to square one"|||Fix your update statement. If you've used the wizard with "Check Original Values", then you are correct, it fails with nulls. You have to manually modify the update to handle nulls.|||

yep.. i got it now... i had to change "compare all values" to "overwrite changes". That makes sense. you cant compare null values to each other.

Thanks