Showing posts with label dll. Show all posts
Showing posts with label dll. Show all posts

Tuesday, March 27, 2012

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

Thursday, March 22, 2012

Can't add ReportViewer to VS toolbox.

I went through all the steps described in sample project but I don't
see ReportViewer in the Toolbox after linking the .dll reference in
Customize Toolbox. What am I missing?Hi Alex,
You should select "Add Remove Items..." on the context menu when you right
click over the Toolbox screen. And then you can point to reportviewer.dll by
browsing it
"Alex Mirzayanov" wrote:
> I went through all the steps described in sample project but I don't
> see ReportViewer in the Toolbox after linking the .dll reference in
> Customize Toolbox. What am I missing?
>sql

Can't Add Reference to Microsoft.SQLServer.RMO.dll

Hi All,
I'm trying to add a reference to this DLL in Visual Studio 2003 so I
can programmatically trigger replication. When I try and add the
reference I get the following exception:
"A reference to 'C:\Program Files\Microsoft SQL Server\90\SDK
\Assemblies\Microsoft.SqlServer.Rmo.dll' could not be added. This is
not a valid assembly or COM component. Only assemblies with extension
'dll' and COM components can be referenced. Please make sure that the
file is accessible, and that it is a valid assembly or COM component."
As you can see it does have a .dll extension.
The file I try to reference indicates it was created on 14 October
2005, 03:43:34 and is version 9.0.1399.0
C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies
\Microsoft.SqlServer.Rmo.dll
Can I doenload another version of the DLL from somewhere?
Any help appreciated!
Thanks
Rajl
On 13 Jul, 13:16, rajpate...@.hotmail.com wrote:
> Hi All,
> I'm trying to add a reference to this DLL in Visual Studio 2003 so I
> can programmatically trigger replication. When I try and add the
> reference I get the following exception:
> "A reference to 'C:\Program Files\Microsoft SQL Server\90\SDK
> \Assemblies\Microsoft.SqlServer.Rmo.dll' could not be added. This is
> not a valid assembly or COM component. Only assemblies with extension
> 'dll' and COM components can be referenced. Please make sure that the
> file is accessible, and that it is a valid assembly or COM component."
> As you can see it does have a .dll extension.
> The file I try to reference indicates it was created on 14 October
> 2005, 03:43:34 and is version 9.0.1399.0
> C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies
> \Microsoft.SqlServer.Rmo.dll
> Can I doenload another version of the DLL from somewhere?
> Any help appreciated!
> Thanks
> Rajl
Also got a newer version of the file version 9.0.242.0, created 10th
Feb 2007 but that has the same problem
|||On 13 Jul, 16:22, rajpate...@.hotmail.com wrote:
> On 13 Jul, 13:16, rajpate...@.hotmail.com wrote:
>
>
>
>
>
>
>
> Also got a newer version of the file version 9.0.242.0, created 10th
> Feb 2007 but that has the same problem- Hide quoted text -
> - Show quoted text -
OK, this is resolved now. I think the issue is to do with the fact I'm
using VS2003. I tried adding the reference to a VS2005 project and
that works fine. I'm guessing that the dll is a .NET 2.0 dll and so
not compatible against VS2003?
|||If you want to programmatically start replication, you probably will also
need to add a reference to the "Replication Agent Library" assembly.
For more information, see
http://msdn2.microsoft.com/de-de/library/ms146869.aspx.
Cheers!
Glenn Gailey
SQL Server User Education
This posting is provided "AS IS" with no warranties, and confers no rights.
"rajpatel50@.hotmail.com" wrote:

> On 13 Jul, 16:22, rajpate...@.hotmail.com wrote:
> OK, this is resolved now. I think the issue is to do with the fact I'm
> using VS2003. I tried adding the reference to a VS2005 project and
> that works fine. I'm guessing that the dll is a .NET 2.0 dll and so
> not compatible against VS2003?
>