Install server2005 in LDAP machine problem: Found the problem and the solution

Hi all,

I installed June CTP on server with (already) SQL 2000 and LDAP (the idea is to check if 2005 and 2000 are good friends).
after installation I start to retrieve Errors from the LDAP: "Automation error The authentication mechanism is unknown." (error 2147016662)

more info about the proccess that failed:
ASP file (IIS5) create object (mine dll).
mine dll try to connect LDAP and retrieve data from user.

The proccess fail when it try to connect the LDAP (I debug it).

more then it: when I create the dll from VB6, every thing gone great.

Any Idea?Just to let you know:

The problem was COM+ issue.
Some how the installation couse my COM+ application to stop working (or work with limited security owner).

I build new COM+ Application, moved all my dlls to the new one, and it work.

Inserting Unicode data

Hi.

We have a sql server db that we need to store Unicode text in. The fields are of the type nvarchar, ntext and nchar. Our solution uses both Oracle and SqlServer as a backing database. In Oracle there is a connection string switch "Unicode=True" that fixes the problem. Is there something similar in SqlServer? Since the db layer is generic we'ed like to avoid using a N' prefix on text strings in query statements.

Hi Kim,

As far as I can see, when the fields types are set to such as NVarChar and the update parameters have been set to the corresponding type, the data will be updated as Unicode in SQL Server. When updating the database, the N' prefix will be added automatically by ADO.NET.

That means you don't need to add anything additional to achieve this.

Are you getting some problem when updating the data in the way I mentioned? If so, please let me know the problem. Thanks!

|||

Hi Kevin,

Thank you for the response. The problem is that this is a system that's gone into production. The code is not written by me and I'm sorry to say it doesn't use command parameters for transfering variables. I guess the fix will have to wait until the next upgrade.