Error when trying to delete user

I created many test users in my application while trying to get a custom registration process to work, and now I would like to delete those users so they don't use up space in my database. When I go into the aspnet_Users table and try to delete a user, it gives me the following error:

----------

DELETE statement conflicted with COLUMN REFERENCE constraint 'FK__aspnet_Me__UserI__0F975522'. The conflict occurred in database 'DB_83996', table 'aspnet_Membership', column 'UserId'.

DELETE FROM [DB_83996].[dbo].[aspnet_Users] WHERE 1=0 OR ( [UserId] = '{7E864A07-6FE8-46EF-A2B8-354646D57C76}' )

----------

I don't know much about SQL statements, so is that statement it gave me the statement I need to use to delete that particular user? If not, how would I go about deleting these users I don't need anymore?

Thanks so much. :)

your table "aspnet_Membership" contains records that reference the user record you are trying to delete.

you will need to delete those records first.

|||Thanks. I could have sworn I tried that before because I knew those two tables were linked. Maybe it was something else I tried. Oh well. Thanks!!

Error when shrinking data file in SQL 2005

Hi,
I got the same error,
When i moved all of user tables and indexes out of primary FG and to a new
FG, my Primary is left with around 17GB of which less than a 1GB is actually
used, and when I ran shrink file on the only file on that FG, it took ages.
then I stoped it (in 2000 it would have taken max 2-3 hours, our SAN is not
that bad :-) ). when I ran it again I get the error described.
when I back up the db and restore it, then I can shrink the file.
this is a db in simle mode, dev environment. worried what happens when we go
to production with this.
error:
File ID 1 of database ID X cannot be shrunk as it is either being shrunk by
another process or is empty.
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should
be discarded.
CTS DBA
"XNMB" wrote:

> i came accross this problem too. what did was to restart the service
> and executed dbcc shrinkfile again. that time it succeeded.
>
I tried detach and re-attach the database fie and run DBCC SHRINKFILE
But I wouldn't recommend shrinking. Here's an article by the great Tibor
Karaszi on database shrinking
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
"CTS_DBA" <CTSDBA@.discussions.microsoft.com> wrote in message
news:630320F3-22A4-4D33-A245-54D14D4784FD@.microsoft.com...[vbcol=seagreen]
> Hi,
> I got the same error,
> When i moved all of user tables and indexes out of primary FG and to a new
> FG, my Primary is left with around 17GB of which less than a 1GB is
> actually
> used, and when I ran shrink file on the only file on that FG, it took
> ages.
> then I stoped it (in 2000 it would have taken max 2-3 hours, our SAN is
> not
> that bad :-) ). when I ran it again I get the error described.
> when I back up the db and restore it, then I can shrink the file.
> this is a db in simle mode, dev environment. worried what happens when we
> go
> to production with this.
> error:
> File ID 1 of database ID X cannot be shrunk as it is either being shrunk
> by
> another process or is empty.
> Msg 0, Level 11, State 0, Line 0
> A severe error occurred on the current command. The results, if any,
> should
> be discarded.
> --
> CTS DBA
>
> "XNMB" wrote:
|||hi,
thanks for the reply.
I know what you mean, but what I don't understand is why shrinkfile wouldn't
work when there's so much free space in the file.
over 8GB
if the original database shrunk in SQL 2000 it works perfectly.
Thanks
CTS DBA
"bass_player [SBS-MVP]" wrote:

> I tried detach and re-attach the database fie and run DBCC SHRINKFILE
> But I wouldn't recommend shrinking. Here's an article by the great Tibor
> Karaszi on database shrinking
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
> "CTS_DBA" <CTSDBA@.discussions.microsoft.com> wrote in message
> news:630320F3-22A4-4D33-A245-54D14D4784FD@.microsoft.com...
>
>

Error when logging on to sql server proper

I am getting the following error.

"The user instance login flag is not supported on this version of SQL Server. The connection will be closed."

Background i created a site on my development machine, and every thing worked, this computer is running sql EX. I uploaded the site to the production server (running sql 2005 standard) and changed the connection string (i have used this connection string with other dB's to display data only, and it works) but i tried it with the ASPNETDB.mdf in the AppData folder and i get the above message.

Do i have to set some special permissions in the db for it to work. I need to be able to insert, update, and delete in this app.

The definition for the 'User Instance' attribute in connection string is as following:

User Instance

A value that indicates whether to redirect the connection from the default SQL Server Express instance to a runtime-initiated instance running under the account of the caller.

So I guess this attribute only make sense todefault SQL Server Express intance? I've tried to set 'User Instance' to true and connect to SQL of other versions(2000 and 2005), all failed with the smae error as you got.|||

I have been able to setup a db that will allow me to do the updates and inserts but with the ASPNETDB.MDF no go. This is the string i'm using:

<connectionStrings>

<addname="ConnectionString"connectionString="server=serversName\XPRESS;uid=aspuser;pwd=aspuserPassworkd;database=DATABName" />

</connectionStrings>

|||

It was a problem with permissions and use. Needed to set user to odb

Thanks for the help though

Error when getting data from the database. VWDE/SQL/Asp.Net/C#

I get the error:
Index out of range exception was unhandled by user code.
At the line:
Label4.Text += reader["RelativeLN"].ToString();

The two lines above it:
Label4.Text += reader["Relation"].ToString() + ": ";
Label4.Text += reader["RelativeFN"].ToString();

will read just fine if I comment out that third line. I don'tunderstand why this could be happening. There is data in the db for theRelativeLN column and it has the same data type as the previous twocolumns.

private void getRelatives()
{
//Define database connection
SqlConnection conn = new SqlConnection(
"Server=localhost\\SqlExpress;Database=MyDB;" + "Integrated Security=True");
//Create command
SqlCommand comm = new SqlCommand("SELECT Relation, RelativeFN FROMRelativeTable WHERE RelativeTable.UserID IN (SELECT UserID FROM UsrTblWHERE UserName = @.usrnmeLbl)", conn);
comm.Parameters.AddWithValue("@.usrnmeLbl", usrNmeLbl.Text);
conn.Open();
SqlDataReader reader = comm.ExecuteReader();
while (reader.Read())
{
Label4.Text += reader["Relation"].ToString() + ": ";
Label4.Text += reader["RelativeFN"].ToString();
Label4.Text += reader["RelativeLN"].ToString();
}
}

I'm hoping someone can provide me some info on what could possibly be going wrong.
Thank you so much in advance.

Hello my friend,

There may be data in the database for it but you are not including this column in your query.

Your query starts with: SELECT Relation, RelativeFN FROM RelativeTable

Change it to start with: SELECT Relation, RelativeFN, RelativeLN FROM RelativeTable

Kind regards

Scotty

|||

OMG, thank you so much. I have been finagling around with this code so much I missed my changes.

THANK YOU THANK YOU!

Error when creating new database user

When I try to create a new database user (on any database) I get this error
message: Cannot resolve
collation conflict for equal to operation.
I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
database has another collation: Danish_Norwegian_CI_AI and the tempdb
database. I don't know why the tempdb has this collation, and if that is the
problem?
I'd start checking the collation for below databases:
master
model
tempdb
msdb
If they aren't the same, you have a problem. It isn't supported to have different collations for the
system databases. Somebody made a "hack" to get you there. You would need to sort it out. Suitable
actions depend on what collation each system database has.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
> When I try to create a new database user (on any database) I get this error
> message: Cannot resolve
> collation conflict for equal to operation.
> I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
> database has another collation: Danish_Norwegian_CI_AI and the tempdb
> database. I don't know why the tempdb has this collation, and if that is the
> problem?
|||The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_AI
It is not possible to change collation in tempdb with alter
database...because it is a system database. What can I do?
"Tibor Karaszi" wrote:

> I'd start checking the collation for below databases:
> master
> model
> tempdb
> msdb
> If they aren't the same, you have a problem. It isn't supported to have different collations for the
> system databases. Somebody made a "hack" to get you there. You would need to sort it out. Suitable
> actions depend on what collation each system database has.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "blaairis" <blaairis@.discussions.microsoft.com> wrote in message
> news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
>
|||Probably somebody moved files for the model database from another installation. Tempdb is created
based on model on each startup. Hunt down database files from an installation that matches system
and msdb for your model database. You can try to just stop SQL Server and replace the files (backup
first, and save a copy of original model database files).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...[vbcol=seagreen]
> The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_AI
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
|||Also, you could try bringing up the instance in master recovery only and
then attempt to modify the collation using the ALTER DATABASE command.
-T3608
ALTER DATABASE model
COLLATE <collation name>
This may only be a pseudo fix, if it works at all. You will probably need
to do as Tibor suggest, but it is worth a shot if you have trouble finding
such a database.
Another way to acquire a model database with the collation you want would be
to install SQL Server Developer Edition on your workstation and specifying
the collation of the system databases during the installation. You would
then need to patch you workstation installation to the same level as your
production database before you tried to copy the files from your workstation
to the server.
Hope this helps.
Sincerely,
Anthony Thomas

"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%239R%23RH3ZFHA.1040@.TK2MSFTNGP10.phx.gbl...
Probably somebody moved files for the model database from another
installation. Tempdb is created
based on model on each startup. Hunt down database files from an
installation that matches system
and msdb for your model database. You can try to just stop SQL Server and
replace the files (backup
first, and save a copy of original model database files).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...
> The master and msdb is ok, but tempdb and model have
Danish_Norwegian_CI_AI[vbcol=seagreen]
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
different collations for[vbcol=seagreen]
to sort it out.[vbcol=seagreen]
error[vbcol=seagreen]
is the[vbcol=seagreen]

Error when creating new database user

When I try to create a new database user (on any database) I get this error
message: Cannot resolve
collation conflict for equal to operation.
I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
database has another collation: Danish_Norwegian_CI_AI and the tempdb
database. I don't know why the tempdb has this collation, and if that is the
problem?I'd start checking the collation for below databases:
master
model
tempdb
msdb
If they aren't the same, you have a problem. It isn't supported to have diff
erent collations for the
system databases. Somebody made a "hack" to get you there. You would need to
sort it out. Suitable
actions depend on what collation each system database has.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
> When I try to create a new database user (on any database) I get this erro
r
> message: Cannot resolve
> collation conflict for equal to operation.
> I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
> database has another collation: Danish_Norwegian_CI_AI and the tempdb
> database. I don't know why the tempdb has this collation, and if that is t
he
> problem?|||The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_AI
It is not possible to change collation in tempdb with alter
database...because it is a system database. What can I do?
"Tibor Karaszi" wrote:

> I'd start checking the collation for below databases:
> master
> model
> tempdb
> msdb
> If they aren't the same, you have a problem. It isn't supported to have di
fferent collations for the
> system databases. Somebody made a "hack" to get you there. You would need
to sort it out. Suitable
> actions depend on what collation each system database has.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "blaairis" <blaairis@.discussions.microsoft.com> wrote in message
> news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
>|||Probably somebody moved files for the model database from another installati
on. Tempdb is created
based on model on each startup. Hunt down database files from an installatio
n that matches system
and msdb for your model database. You can try to just stop SQL Server and re
place the files (backup
first, and save a copy of original model database files).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...[vbcol=seagreen]
> The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_A
I
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
>|||Also, you could try bringing up the instance in master recovery only and
then attempt to modify the collation using the ALTER DATABASE command.
-T3608
ALTER DATABASE model
COLLATE <collation name>
This may only be a pseudo fix, if it works at all. You will probably need
to do as Tibor suggest, but it is worth a shot if you have trouble finding
such a database.
Another way to acquire a model database with the collation you want would be
to install SQL Server Developer Edition on your workstation and specifying
the collation of the system databases during the installation. You would
then need to patch you workstation installation to the same level as your
production database before you tried to copy the files from your workstation
to the server.
Hope this helps.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%239R%23RH3ZFHA.1040@.TK2MSFTNGP10.phx.gbl...
Probably somebody moved files for the model database from another
installation. Tempdb is created
based on model on each startup. Hunt down database files from an
installation that matches system
and msdb for your model database. You can try to just stop SQL Server and
replace the files (backup
first, and save a copy of original model database files).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...
> The master and msdb is ok, but tempdb and model have
Danish_Norwegian_CI_AI[vbcol=seagreen]
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
>
different collations for[vbcol=seagreen]
to sort it out.[vbcol=seagreen]
error[vbcol=seagreen]
is the[vbcol=seagreen]

Error when creating new database user

When I try to create a new database user (on any database) I get this error
message: Cannot resolve
collation conflict for equal to operation.
I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
database has another collation: Danish_Norwegian_CI_AI and the tempdb
database. I don't know why the tempdb has this collation, and if that is the
problem?I'd start checking the collation for below databases:
master
model
tempdb
msdb
If they aren't the same, you have a problem. It isn't supported to have different collations for the
system databases. Somebody made a "hack" to get you there. You would need to sort it out. Suitable
actions depend on what collation each system database has.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
> When I try to create a new database user (on any database) I get this error
> message: Cannot resolve
> collation conflict for equal to operation.
> I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
> database has another collation: Danish_Norwegian_CI_AI and the tempdb
> database. I don't know why the tempdb has this collation, and if that is the
> problem?|||The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_AI
It is not possible to change collation in tempdb with alter
database...because it is a system database. What can I do?
"Tibor Karaszi" wrote:
> I'd start checking the collation for below databases:
> master
> model
> tempdb
> msdb
> If they aren't the same, you have a problem. It isn't supported to have different collations for the
> system databases. Somebody made a "hack" to get you there. You would need to sort it out. Suitable
> actions depend on what collation each system database has.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "blaairis" <blaairis@.discussions.microsoft.com> wrote in message
> news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
> > When I try to create a new database user (on any database) I get this error
> > message: Cannot resolve
> > collation conflict for equal to operation.
> > I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
> > database has another collation: Danish_Norwegian_CI_AI and the tempdb
> > database. I don't know why the tempdb has this collation, and if that is the
> > problem?
>|||Probably somebody moved files for the model database from another installation. Tempdb is created
based on model on each startup. Hunt down database files from an installation that matches system
and msdb for your model database. You can try to just stop SQL Server and replace the files (backup
first, and save a copy of original model database files).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...
> The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_AI
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
>> I'd start checking the collation for below databases:
>> master
>> model
>> tempdb
>> msdb
>> If they aren't the same, you have a problem. It isn't supported to have different collations for
>> the
>> system databases. Somebody made a "hack" to get you there. You would need to sort it out.
>> Suitable
>> actions depend on what collation each system database has.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "blaairis" <blaairis@.discussions.microsoft.com> wrote in message
>> news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
>> > When I try to create a new database user (on any database) I get this error
>> > message: Cannot resolve
>> > collation conflict for equal to operation.
>> > I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
>> > database has another collation: Danish_Norwegian_CI_AI and the tempdb
>> > database. I don't know why the tempdb has this collation, and if that is the
>> > problem?
>>|||Also, you could try bringing up the instance in master recovery only and
then attempt to modify the collation using the ALTER DATABASE command.
-T3608
ALTER DATABASE model
COLLATE <collation name>
This may only be a pseudo fix, if it works at all. You will probably need
to do as Tibor suggest, but it is worth a shot if you have trouble finding
such a database.
Another way to acquire a model database with the collation you want would be
to install SQL Server Developer Edition on your workstation and specifying
the collation of the system databases during the installation. You would
then need to patch you workstation installation to the same level as your
production database before you tried to copy the files from your workstation
to the server.
Hope this helps.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%239R%23RH3ZFHA.1040@.TK2MSFTNGP10.phx.gbl...
Probably somebody moved files for the model database from another
installation. Tempdb is created
based on model on each startup. Hunt down database files from an
installation that matches system
and msdb for your model database. You can try to just stop SQL Server and
replace the files (backup
first, and save a copy of original model database files).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...
> The master and msdb is ok, but tempdb and model have
Danish_Norwegian_CI_AI
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
>> I'd start checking the collation for below databases:
>> master
>> model
>> tempdb
>> msdb
>> If they aren't the same, you have a problem. It isn't supported to have
different collations for
>> the
>> system databases. Somebody made a "hack" to get you there. You would need
to sort it out.
>> Suitable
>> actions depend on what collation each system database has.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "blaairis" <blaairis@.discussions.microsoft.com> wrote in message
>> news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
>> > When I try to create a new database user (on any database) I get this
error
>> > message: Cannot resolve
>> > collation conflict for equal to operation.
>> > I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
>> > database has another collation: Danish_Norwegian_CI_AI and the tempdb
>> > database. I don't know why the tempdb has this collation, and if that
is the
>> > problem?
>>

Error trying to connect

Hello all
I am getting an error 8198 when trying to replicate from one server. It
says Could not obtain informaion about Windows NT user/group and username
problem is the user it cannot obtain information about does not exist on
either server. What else can cause this error
Warren,
as this is a validation issue, the most likely issue is the job owner - pls
try changing the job owner to sa.
The other possibility is the sql server agent account. Please make sure that
the sql server agent is run by a windows account that is in the sysadmin
role on each server.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Error sending mail SQL / Hotmail

Hi

Using SQL to send e-mail , returns the next error when sending to hotmail user.

Error,53,The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 3 (2007-03-16T09:43:38). Exception Message: Cannot send mails to mail server. (Mailbox name not allowed. The server response was: sorry<c/> that domain isn't in my list of allowed rcpthosts (#5.7.1)).
),244,79,,16.03.2007 09:43:38,sa

Any one can help?

Thanks,

Rodrigo Vieira

Hi,

which server are you sending the mail through ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Hi

Microsoft Exchange 2000 Server

|||Seems that the server is blocking the sender / rcpt combination. Some MailServer are configured not to accept outgoing mails to certain mail domains. If you are in charge of the mailserver, look at the blacklist if the hotmail domain is on the blacklist or ask your administrator to do this.

Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

I don't think so, because I can send correctly using another applications with the same Mail Server.

Using Outlook Express for example.

Any tip?

Thanks,

Rodrigo Vieira

|||

Lets clarify some things. If anything is not right, you should correct me to find the problem.

The Exchange server is inside your company, allowing SMTP relay.
You are using an account to send the emails out which is known and trusted on the SMTP server.
Your Exchange server is allowing SMTP relay with no constraints on other mail domains like hotmail.

if the above assumptions are right, you should be able to send mails to an outside mail domain, Outlook Express normally does not connect to the Exchange Server unless you allow SMTP and POP access o the mailboxes, so I guess your mailserver for sending out Outlook Express mails is anothr than the Exchange Server.

Jens K. Suessmeyer.

http://www.sqlserver2005.de