problems with SQLDMO.dll

i have a vb.net application that uses SQL-DMO. the development machine is
WinXP
when i build a setup for my application and then install this on a clean
WinXP test machine it all runs fine
but when i install it on a Win2000 test machine i get the following error -
the sqldmo.dll registers successfully - but just gives this error message.
[SQL-DMO]Invalid Paramter Type; must be string or ordinal......
i have followed all the instructions thru here:-
http://support.microsoft.com/default.aspx?scid=kb;en-us;248241
but still cannot get it to run. any ideas as to what may be causing this? is
there different versions of sqldmo.dll that i need to run for win2k?
Cheers,
Craighi Craig,
"Craig G" <craig.gamble@.yarrasoftware.com> ha scritto nel messaggio
news:%23lsbQskmEHA.3340@.TK2MSFTNGP14.phx.gbl...
> i have a vb.net application that uses SQL-DMO. the development machine is
> WinXP
> when i build a setup for my application and then install this on a clean
> WinXP test machine it all runs fine
> but when i install it on a Win2000 test machine i get the following
error -
> the sqldmo.dll registers successfully - but just gives this error message.
> [SQL-DMO]Invalid Paramter Type; must be string or ordinal......
> i have followed all the instructions thru here:-
> http://support.microsoft.com/default.aspx?scid=kb;en-us;248241
> but still cannot get it to run. any ideas as to what may be causing this?
is
> there different versions of sqldmo.dll that i need to run for win2k?
actually not that I'm aware of...
personally I've built my (InnoSetup) SQL-DMO install package on a WinXP sp1
box, and deployed with success on Win98, Win2k, XP and Win2003..
the list of files I ditribute is like following:
; not licensed by redist.txt but available after installation of MDAC2.6
..\WINDOWS\SYSTEM\odbcbcp.dll; DestDir: WinSys ; sharedfile
; not licensed by redist.txt but available after installation of MDAC2.6
..\WINDOWS\SYSTEM\sqlwoa.dll ; DestDir: WinSys
; not licensed by redist.txt but available after installation of MDAC2.6
..\WINDOWS\SYSTEM\sqlwid.dll ; DestDir: WinSys
..\Programmi\Microsoft SQL Server\80\Tools\Binn\w95scm.dll; DestDir:
DestinationFolder\Binn
..\WINDOWS\SYSTEM\sqlunirl.dll ; DestDir: WinSys
..\Programmi\Microsoft SQL Server\80\Tools\Binn\sqlresld.dll; DestDir:
DestinationFolder\Binn
..\Programmi\Microsoft SQL Server\80\Tools\Binn\sqlsvc.dll; DestDir:
DestinationFolder\Binn
; not licensed by redist.txt but available after installation of MDAC2.6
..\Programmi\Microsoft SQL Server\80\Tools\Binn\Resources\1033\sqlsvc.RLL;
DestDir: DestinationFolder\Binn\Resources\1033
; not licensed by redist.txt but available after installation of MDAC2.6
..\Programmi\Microsoft SQL Server\80\Tools\Binn\Resources\1033\Sqldmo.rll;
DestDir: DestinationFolder\Binn\Resources\1033
..\Programmi\Microsoft SQL Server\80\Tools\Binn\sqldmo.dll; DestDir:
DestinationFolder\Binn ; file to be registered via regserver
DestinationFolder can either be the installation directory of one instance
of Microsoft SqlServer 2000, like ..\Program Files\Microsoft SQL
Server\80\Tools, even if no istance of SQL Server has been installed, or the
installation directory of your application, but the first is preferred.
Please do respect the hierarchy \Binn\Resources\1033 (where 1033 specifies
the language), where needed, in order to grant correct functionality of
Ole-Automation objects.
In order to install SQL-DMO components for MSDE 2000, Microsoft Internet
Explorer 5.5 or higher is required.
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

problems with SQLDMO.dll

i have a vb.net application that uses SQL-DMO. the development machine is
WinXP
when i build a setup for my application and then install this on a clean
WinXP test machine it all runs fine
but when i install it on a Win2000 test machine i get the following error -
the sqldmo.dll registers successfully - but just gives this error message.
[SQL-DMO]Invalid Paramter Type; must be string or ordinal......
i have followed all the instructions thru here:-
http://support.microsoft.com/default...b;en-us;248241
but still cannot get it to run. any ideas as to what may be causing this? is
there different versions of sqldmo.dll that i need to run for win2k?
Cheers,
Craig
Craig,
You may to make sure the your Windows 2000 machine is on the same version of
..NET as was your XP machine.
Regards,
Cory
"Craig G" wrote:

> i have a vb.net application that uses SQL-DMO. the development machine is
> WinXP
> when i build a setup for my application and then install this on a clean
> WinXP test machine it all runs fine
> but when i install it on a Win2000 test machine i get the following error -
> the sqldmo.dll registers successfully - but just gives this error message.
> [SQL-DMO]Invalid Paramter Type; must be string or ordinal......
> i have followed all the instructions thru here:-
> http://support.microsoft.com/default...b;en-us;248241
> but still cannot get it to run. any ideas as to what may be causing this? is
> there different versions of sqldmo.dll that i need to run for win2k?
> Cheers,
> Craig
>
>

problems with merge rep after upgrading from sql server 2000 sp3a to sql server 2005 build 2153

Hi,

We just upgraded 2 sql servers from sql server 2000 sp3a to sql server 2005 build 2153, and merge rep exists between these 2 servers.

However, after sql server upgrade, we had to reinitialize merge replication and now the merge agent is reporting 2 errors

1)

Error messages:

The Merge Agent failed to upgrade triggers, metadata and stored procedures on the Subscriber to versions compatible with SQL Server 2005. Restart synchronization, and if this failure continues to occur reinitialize the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199403)
Get help: http://help/MSSQL_REPL-2147199403

Invalid column name 'metadata_select_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207

Invalid column name 'delete_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207

2)

Command attempted:

{call sp_MSensure_single_instance (N'Merge Agent Name', 4)}

Error messages:

The merge process could not connect to the Publisher 'Server:database'. Check to ensure that the server is running. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199368)
Get help: http://help/MSSQL_REPL-2147199368

Another merge agent for the subscription(s) is running or the server is working on a previous request by the same agent. (Source: MSSQLServer, Error number: 21036)
Get help: http://help/21036

looking inside the sp_MSensure_single_instance stored procedure, it's trying to obtain an exclusive lock on resource 'Merge Agent Name' but fails and returns -1

this is the stored procedure executed by sp_MSensure_single_instance and @.retcode = -1 and thus cannot obtain exclusive lock on resource

EXEC @.retcode = sys.sp_getapplock @.Resource = 'Merge Agent Name',

@.LockMode = 'Exclusive',

@.LockOwner = 'Session',

@.LockTimeout = 0,

@.DbPrincipal = 'MSmerge_PAL_role'

so i think it's failing because for some reason MSmerge_PAL_role database role does not have enough rights to obtain exclusive lock on necessary resources

i've tried many things to fix this, including scripting out and dropping all merge rep, turning off replication db option and reapplying replication create scripts on the server, and even manually deleting the MSmerge_PAL_role database role but still doesn't work

can anyone help?

Thanks

anyone?|||

Looks to me like the upgrade did not happen correctly on the subscriber machine.

Can you check the upgrade log for any failures?

Also would dropping the subscriber db and recreating the subscription help?

If you create a new database and subscriber, do you still see the same error?

|||

Thanks for the reply

however the error with the database role occured at the publisher/distributor and not the subscriber

have went back to check the installation logs for both the publisher/distributor and the subscriber and didn't find any errors

also, both instances did not report any errors during upgrade

any other ideas why this might happen?

thanks

|||

We have the same error under similar circumstances. We upgraded a data from an SQL Server 2000 SP4 machine to a new machine of the same name running SQL Server 2005 (9.0.1399). Prior to the upgrade I dropped all subscriptions for this database from the publisher (SQL Server 2005 9.0.) and then copied the MDF and LDF files to the new server and attached them.

Snapshot and Transactional replication run fine, but Merge replication does not run at all. As per the original messenger I have tried to initialize the subscriptions, delete the subscriptions and re-create them, and nothing is working.

Any ideas would be gratefully received.

|||Sorry. The publisher is version 9..3054.|||Im having this problem as well, anybody mange to solve it?

problems with merge rep after upgrading from sql server 2000 sp3a to sql server 2005 build 2153

Hi,

We just upgraded 2 sql servers from sql server 2000 sp3a to sql server 2005 build 2153, and merge rep exists between these 2 servers.

However, after sql server upgrade, we had to reinitialize merge replication and now the merge agent is reporting 2 errors

1)

Error messages:

The Merge Agent failed to upgrade triggers, metadata and stored procedures on the Subscriber to versions compatible with SQL Server 2005. Restart synchronization, and if this failure continues to occur reinitialize the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199403)
Get help: http://help/MSSQL_REPL-2147199403

Invalid column name 'metadata_select_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207

Invalid column name 'delete_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207

2)

Command attempted:

{call sp_MSensure_single_instance (N'Merge Agent Name', 4)}

Error messages:

The merge process could not connect to the Publisher 'Server:database'. Check to ensure that the server is running. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199368)
Get help: http://help/MSSQL_REPL-2147199368

Another merge agent for the subscription(s) is running or the server is working on a previous request by the same agent. (Source: MSSQLServer, Error number: 21036)
Get help: http://help/21036

looking inside the sp_MSensure_single_instance stored procedure, it's trying to obtain an exclusive lock on resource 'Merge Agent Name' but fails and returns -1

this is the stored procedure executed by sp_MSensure_single_instance and @.retcode = -1 and thus cannot obtain exclusive lock on resource

EXEC @.retcode = sys.sp_getapplock @.Resource = 'Merge Agent Name',

@.LockMode = 'Exclusive',

@.LockOwner = 'Session',

@.LockTimeout = 0,

@.DbPrincipal = 'MSmerge_PAL_role'

so i think it's failing because for some reason MSmerge_PAL_role database role does not have enough rights to obtain exclusive lock on necessary resources

i've tried many things to fix this, including scripting out and dropping all merge rep, turning off replication db option and reapplying replication create scripts on the server, and even manually deleting the MSmerge_PAL_role database role but still doesn't work

can anyone help?

Thanks

anyone?|||

Looks to me like the upgrade did not happen correctly on the subscriber machine.

Can you check the upgrade log for any failures?

Also would dropping the subscriber db and recreating the subscription help?

If you create a new database and subscriber, do you still see the same error?

|||

Thanks for the reply

however the error with the database role occured at the publisher/distributor and not the subscriber

have went back to check the installation logs for both the publisher/distributor and the subscriber and didn't find any errors

also, both instances did not report any errors during upgrade

any other ideas why this might happen?

thanks

|||

We have the same error under similar circumstances. We upgraded a data from an SQL Server 2000 SP4 machine to a new machine of the same name running SQL Server 2005 (9.0.1399). Prior to the upgrade I dropped all subscriptions for this database from the publisher (SQL Server 2005 9.0.) and then copied the MDF and LDF files to the new server and attached them.

Snapshot and Transactional replication run fine, but Merge replication does not run at all. As per the original messenger I have tried to initialize the subscriptions, delete the subscriptions and re-create them, and nothing is working.

Any ideas would be gratefully received.

|||Sorry. The publisher is version 9..3054.

problems with merge rep after upgrading from sql server 2000 sp3a to sql server 2005 build 2153

Hi,

We just upgraded 2 sql servers from sql server 2000 sp3a to sql server 2005 build 2153, and merge rep exists between these 2 servers.

However, after sql server upgrade, we had to reinitialize merge replication and now the merge agent is reporting 2 errors

1)

Error messages:

The Merge Agent failed to upgrade triggers, metadata and stored procedures on the Subscriber to versions compatible with SQL Server 2005. Restart synchronization, and if this failure continues to occur reinitialize the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199403)
Get help: http://help/MSSQL_REPL-2147199403

Invalid column name 'metadata_select_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207

Invalid column name 'delete_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207

2)

Command attempted:

{call sp_MSensure_single_instance (N'Merge Agent Name', 4)}

Error messages:

The merge process could not connect to the Publisher 'Server:database'. Check to ensure that the server is running. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199368)
Get help: http://help/MSSQL_REPL-2147199368

Another merge agent for the subscription(s) is running or the server is working on a previous request by the same agent. (Source: MSSQLServer, Error number: 21036)
Get help: http://help/21036

looking inside the sp_MSensure_single_instance stored procedure, it's trying to obtain an exclusive lock on resource 'Merge Agent Name' but fails and returns -1

this is the stored procedure executed by sp_MSensure_single_instance and @.retcode = -1 and thus cannot obtain exclusive lock on resource

EXEC @.retcode = sys.sp_getapplock @.Resource = 'Merge Agent Name',

@.LockMode = 'Exclusive',

@.LockOwner = 'Session',

@.LockTimeout = 0,

@.DbPrincipal = 'MSmerge_PAL_role'

so i think it's failing because for some reason MSmerge_PAL_role database role does not have enough rights to obtain exclusive lock on necessary resources

i've tried many things to fix this, including scripting out and dropping all merge rep, turning off replication db option and reapplying replication create scripts on the server, and even manually deleting the MSmerge_PAL_role database role but still doesn't work

can anyone help?

Thanks

anyone?|||

Looks to me like the upgrade did not happen correctly on the subscriber machine.

Can you check the upgrade log for any failures?

Also would dropping the subscriber db and recreating the subscription help?

If you create a new database and subscriber, do you still see the same error?

|||

Thanks for the reply

however the error with the database role occured at the publisher/distributor and not the subscriber

have went back to check the installation logs for both the publisher/distributor and the subscriber and didn't find any errors

also, both instances did not report any errors during upgrade

any other ideas why this might happen?

thanks

|||

We have the same error under similar circumstances. We upgraded a data from an SQL Server 2000 SP4 machine to a new machine of the same name running SQL Server 2005 (9.0.1399). Prior to the upgrade I dropped all subscriptions for this database from the publisher (SQL Server 2005 9.0.) and then copied the MDF and LDF files to the new server and attached them.

Snapshot and Transactional replication run fine, but Merge replication does not run at all. As per the original messenger I have tried to initialize the subscriptions, delete the subscriptions and re-create them, and nothing is working.

Any ideas would be gratefully received.

|||Sorry. The publisher is version 9..3054.|||Im having this problem as well, anybody mange to solve it?

Problems when trying to build Connection to SQL Server Express from ASP.NET application

Hi,
I have a problem, when I want to access to my SQL Server Express
database from my ASP.NET application.
My workstation ID is KITOLAP-HP
My username is user01

Now I built the following connection String (VB.NET):
Dim workstation As String =
System.Environment.GetEnvironmentVariable("computername")
connectionString = "workstation id=""" & workstation & """;packet
size=4096;user id=user01;integrated security=SSPI;data source=""" &
workstation & "\SQLExpress"";persist security info=True;initial
catalog=webshop"
connection = New SqlConnection(connectionString)

Although I put as user id "user01" the application makes an error when
I try to open the connection, saying that the login with user "aspnet"
failed.

How can I change it so that as login-user "user01" is taken and not
"aspnet" or otherwise, how can I create a new user in the SQL Server
database with which I could access the DB??

thanks,
kitoYour connection string contains a mix of both SQL authentication and Windows
authentication methods. For SQL authentication, specify User ID and
Password and omit the Integrated Security keyword. For Windows
Authentication, specify only Integrated Security=SSPI and omit the User ID
and Password so that the Windows process identity is used.

Quote:

Originally Posted by

How can I change it so that as login-user "user01" is taken and not
"aspnet" or otherwise, how can I create a new user in the SQL Server
database with which I could access the DB??

It looks like you want to use SQL Authentication so specify 'user01' and the
corresponding password as described above. Below is a script to add the
login to SQL Server and corresponding database user:

USE webshop
GO
CREATE LOGIN user01 WITH PASSWORD = 'mypassword';
CREATE USER user01;
GO

Note that you'll also need to grant object permissions to complete your
security configuration. The Best Practice is to grant permissions only to
roles so that you can easily control access via role membership. For
example:

--setup security on each object
CREATE ROLE WebRole;
GRANT EXECUTE ON dbo.MyProc TO WebRole;

--assign users to role(s)
EXEC sp_addrolemember 'WebRole', 'user01'

--
Hope this helps.

Dan Guzman
SQL Server MVP

"kito" <juri.strumpflohner@.gmail.comwrote in message
news:1154517199.822958.63630@.p79g2000cwp.googlegro ups.com...

Quote:

Originally Posted by

Hi,
I have a problem, when I want to access to my SQL Server Express
database from my ASP.NET application.
My workstation ID is KITOLAP-HP
My username is user01
>
Now I built the following connection String (VB.NET):
Dim workstation As String =
System.Environment.GetEnvironmentVariable("computername")
connectionString = "workstation id=""" & workstation & """;packet
size=4096;user id=user01;integrated security=SSPI;data source=""" &
workstation & "\SQLExpress"";persist security info=True;initial
catalog=webshop"
connection = New SqlConnection(connectionString)
>
Although I put as user id "user01" the application makes an error when
I try to open the connection, saying that the login with user "aspnet"
failed.
>
How can I change it so that as login-user "user01" is taken and not
"aspnet" or otherwise, how can I create a new user in the SQL Server
database with which I could access the DB??
>
thanks,
kito
>