Hi Good Day everybody,
Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
below:
Current Server (Server A)
a) Windows NT4 SP6a
b) SQL 7 + SP4
c) Default Collation: SQL_Latin1_General_CP1_CI_AS
d) Default Data Location: E:\MSSQL7
New Server (Server B)
a) Window 2000 Server SP4
b) SQL 2000 + SP3a
c) Default Collation: Latin1_General_CP1_CI_AS (required to set as default)
d) Default Data Location: D:\Program Files\Microsoft SQL Server
Authentication Mode:
a) Mixed Mode
b) SQL and Windows Authentication
* Both server are login with same userid and password.
Problem:
I have create and new user database "PA_CCCTemp" in the SQL2000 server.
Besides, I also backup user database "PA_CCC" from SQL7.
However, during I restore databases that I have backup into the SQL2000
server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The backup
set holds a backup of a database other than the existing 'PA_CCCTemp"
database. Restore Databse is terminating abnormally.
I do not know what is the problem caused. Either the database is different
name, or the restoration location are different from the original place, or
the collation is different.
I also need help on how I can migrate the database from SQL7 to SQL 2000,
includes user id and logon password.
Regards,
Polar Bear
Hi,
It seems you have given a physical location which is not in the new server
(Drive and directory) while loading in SQL 2000.
Please follow the below steps in query analyzer:-
Restore filelistonly from disk='c:\backup\dbname.bak'
( replace the 'c:\backup\dbname.bak' with the actual backup file name with
path where the file resides.)
This will give you the Logical and Physical file names of the Backup file
name. While loading you should give the
correct logical file name and the place to keep the physical file. But
Physical file name can be a diffrent one.
Restore Database <dbname> from disk= 'c:\backup\dbname.bak' with
move 'logical_mdf_name' to 'c:\mssql\data\phys_data_name.Xmdf',
move 'logical_ldf_name' to 'c:\mssql\data\phys_log_name.lXdf'
(Replace the logical_mdf_name and logical_ldf_name with the logical name you
got from RESTORE FILELISTONLY command.
Ensure that the directory give in physical file name is there in the server)
Thanks
Hari
SQL Server MVP
Thanks
Hari
SQL Server MVP
"Polar Bear" <Polar Bear@.discussions.microsoft.com> wrote in message
news:227A549B-7D5A-48DA-A4F5-1850CE31B84B@.microsoft.com...
> Hi Good Day everybody,
> Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
> below:
> Current Server (Server A)
> a) Windows NT4 SP6a
> b) SQL 7 + SP4
> c) Default Collation: SQL_Latin1_General_CP1_CI_AS
> d) Default Data Location: E:\MSSQL7
> New Server (Server B)
> a) Window 2000 Server SP4
> b) SQL 2000 + SP3a
> c) Default Collation: Latin1_General_CP1_CI_AS (required to set as
> default)
> d) Default Data Location: D:\Program Files\Microsoft SQL Server
> Authentication Mode:
> a) Mixed Mode
> b) SQL and Windows Authentication
> * Both server are login with same userid and password.
> Problem:
> I have create and new user database "PA_CCCTemp" in the SQL2000 server.
> Besides, I also backup user database "PA_CCC" from SQL7.
> However, during I restore databases that I have backup into the SQL2000
> server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The backup
> set holds a backup of a database other than the existing 'PA_CCCTemp"
> database. Restore Databse is terminating abnormally.
> I do not know what is the problem caused. Either the database is different
> name, or the restoration location are different from the original place,
> or
> the collation is different.
> I also need help on how I can migrate the database from SQL7 to SQL 2000,
> includes user id and logon password.
> Regards,
> Polar Bear
>
Showing posts with label upgrade. Show all posts
Showing posts with label upgrade. Show all posts
Wednesday, March 28, 2012
Help! Unable to restore DB from SQL7 to SQL2000
Hi Good Day everybody,
Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
below:
Current Server (Server A)
a) Windows NT4 SP6a
b) SQL 7 + SP4
c) Default Collation: SQL_Latin1_General_CP1_CI_AS
d) Default Data Location: E:\MSSQL7
New Server (Server B)
a) Window 2000 Server SP4
b) SQL 2000 + SP3a
c) Default Collation: Latin1_General_CP1_CI_AS (required to set as default)
d) Default Data Location: D:\Program Files\Microsoft SQL Server
Authentication Mode:
a) Mixed Mode
b) SQL and Windows Authentication
* Both server are login with same userid and password.
Problem:
I have create and new user database "PA_CCCTemp" in the SQL2000 server.
Besides, I also backup user database "PA_CCC" from SQL7.
However, during I restore databases that I have backup into the SQL2000
server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The backup
set holds a backup of a database other than the existing 'PA_CCCTemp"
database. Restore Databse is terminating abnormally.
I do not know what is the problem caused. Either the database is different
name, or the restoration location are different from the original place, or
the collation is different.
I also need help on how I can migrate the database from SQL7 to SQL 2000,
includes user id and logon password.
Regards,
Polar BearHi,
It seems you have given a physical location which is not in the new server
(Drive and directory) while loading in SQL 2000.
Please follow the below steps in query analyzer:-
Restore filelistonly from disk='c:\backup\dbname.bak'
( replace the 'c:\backup\dbname.bak' with the actual backup file name with
path where the file resides.)
This will give you the Logical and Physical file names of the Backup file
name. While loading you should give the
correct logical file name and the place to keep the physical file. But
Physical file name can be a diffrent one.
Restore Database <dbname> from disk= 'c:\backup\dbname.bak' with
move 'logical_mdf_name' to 'c:\mssql\data\phys_data_name.mdf',
move 'logical_ldf_name' to 'c:\mssql\data\phys_log_name.ldf'
(Replace the logical_mdf_name and logical_ldf_name with the logical name you
got from RESTORE FILELISTONLY command.
Ensure that the directory give in physical file name is there in the server)
Thanks
Hari
SQL Server MVP
Thanks
Hari
SQL Server MVP
"Polar Bear" <Polar Bear@.discussions.microsoft.com> wrote in message
news:227A549B-7D5A-48DA-A4F5-1850CE31B84B@.microsoft.com...
> Hi Good Day everybody,
> Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
> below:
> Current Server (Server A)
> a) Windows NT4 SP6a
> b) SQL 7 + SP4
> c) Default Collation: SQL_Latin1_General_CP1_CI_AS
> d) Default Data Location: E:\MSSQL7
> New Server (Server B)
> a) Window 2000 Server SP4
> b) SQL 2000 + SP3a
> c) Default Collation: Latin1_General_CP1_CI_AS (required to set as
> default)
> d) Default Data Location: D:\Program Files\Microsoft SQL Server
> Authentication Mode:
> a) Mixed Mode
> b) SQL and Windows Authentication
> * Both server are login with same userid and password.
> Problem:
> I have create and new user database "PA_CCCTemp" in the SQL2000 server.
> Besides, I also backup user database "PA_CCC" from SQL7.
> However, during I restore databases that I have backup into the SQL2000
> server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The backup
> set holds a backup of a database other than the existing 'PA_CCCTemp"
> database. Restore Databse is terminating abnormally.
> I do not know what is the problem caused. Either the database is different
> name, or the restoration location are different from the original place,
> or
> the collation is different.
> I also need help on how I can migrate the database from SQL7 to SQL 2000,
> includes user id and logon password.
> Regards,
> Polar Bear
>sql
Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
below:
Current Server (Server A)
a) Windows NT4 SP6a
b) SQL 7 + SP4
c) Default Collation: SQL_Latin1_General_CP1_CI_AS
d) Default Data Location: E:\MSSQL7
New Server (Server B)
a) Window 2000 Server SP4
b) SQL 2000 + SP3a
c) Default Collation: Latin1_General_CP1_CI_AS (required to set as default)
d) Default Data Location: D:\Program Files\Microsoft SQL Server
Authentication Mode:
a) Mixed Mode
b) SQL and Windows Authentication
* Both server are login with same userid and password.
Problem:
I have create and new user database "PA_CCCTemp" in the SQL2000 server.
Besides, I also backup user database "PA_CCC" from SQL7.
However, during I restore databases that I have backup into the SQL2000
server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The backup
set holds a backup of a database other than the existing 'PA_CCCTemp"
database. Restore Databse is terminating abnormally.
I do not know what is the problem caused. Either the database is different
name, or the restoration location are different from the original place, or
the collation is different.
I also need help on how I can migrate the database from SQL7 to SQL 2000,
includes user id and logon password.
Regards,
Polar BearHi,
It seems you have given a physical location which is not in the new server
(Drive and directory) while loading in SQL 2000.
Please follow the below steps in query analyzer:-
Restore filelistonly from disk='c:\backup\dbname.bak'
( replace the 'c:\backup\dbname.bak' with the actual backup file name with
path where the file resides.)
This will give you the Logical and Physical file names of the Backup file
name. While loading you should give the
correct logical file name and the place to keep the physical file. But
Physical file name can be a diffrent one.
Restore Database <dbname> from disk= 'c:\backup\dbname.bak' with
move 'logical_mdf_name' to 'c:\mssql\data\phys_data_name.mdf',
move 'logical_ldf_name' to 'c:\mssql\data\phys_log_name.ldf'
(Replace the logical_mdf_name and logical_ldf_name with the logical name you
got from RESTORE FILELISTONLY command.
Ensure that the directory give in physical file name is there in the server)
Thanks
Hari
SQL Server MVP
Thanks
Hari
SQL Server MVP
"Polar Bear" <Polar Bear@.discussions.microsoft.com> wrote in message
news:227A549B-7D5A-48DA-A4F5-1850CE31B84B@.microsoft.com...
> Hi Good Day everybody,
> Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
> below:
> Current Server (Server A)
> a) Windows NT4 SP6a
> b) SQL 7 + SP4
> c) Default Collation: SQL_Latin1_General_CP1_CI_AS
> d) Default Data Location: E:\MSSQL7
> New Server (Server B)
> a) Window 2000 Server SP4
> b) SQL 2000 + SP3a
> c) Default Collation: Latin1_General_CP1_CI_AS (required to set as
> default)
> d) Default Data Location: D:\Program Files\Microsoft SQL Server
> Authentication Mode:
> a) Mixed Mode
> b) SQL and Windows Authentication
> * Both server are login with same userid and password.
> Problem:
> I have create and new user database "PA_CCCTemp" in the SQL2000 server.
> Besides, I also backup user database "PA_CCC" from SQL7.
> However, during I restore databases that I have backup into the SQL2000
> server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The backup
> set holds a backup of a database other than the existing 'PA_CCCTemp"
> database. Restore Databse is terminating abnormally.
> I do not know what is the problem caused. Either the database is different
> name, or the restoration location are different from the original place,
> or
> the collation is different.
> I also need help on how I can migrate the database from SQL7 to SQL 2000,
> includes user id and logon password.
> Regards,
> Polar Bear
>sql
Help! Unable to restore DB from SQL7 to SQL2000
Hi Good Day everybody,
Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
below:
Current Server (Server A)
a) Windows NT4 SP6a
b) SQL 7 + SP4
c) Default Collation: SQL_Latin1_General_CP1_CI_AS
d) Default Data Location: E:\MSSQL7
New Server (Server B)
a) Window 2000 Server SP4
b) SQL 2000 + SP3a
c) Default Collation: Latin1_General_CP1_CI_AS (required to set as default)
d) Default Data Location: D:\Program Files\Microsoft SQL Server
Authentication Mode:
a) Mixed Mode
b) SQL and Windows Authentication
* Both server are login with same userid and password.
Problem:
I have create and new user database "PA_CCCTemp" in the SQL2000 server.
Besides, I also backup user database "PA_CCC" from SQL7.
However, during I restore databases that I have backup into the SQL2000
server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The back
up
set holds a backup of a database other than the existing 'PA_CCCTemp"
database. Restore Databse is terminating abnormally.
I do not know what is the problem caused. Either the database is different
name, or the restoration location are different from the original place, or
the collation is different.
I also need help on how I can migrate the database from SQL7 to SQL 2000,
includes user id and logon password.
Regards,
Polar BearHi,
It seems you have given a physical location which is not in the new server
(Drive and directory) while loading in SQL 2000.
Please follow the below steps in query analyzer:-
Restore filelistonly from disk='c:\backup\dbname.bak'
( replace the 'c:\backup\dbname.bak' with the actual backup file name with
path where the file resides.)
This will give you the Logical and Physical file names of the Backup file
name. While loading you should give the
correct logical file name and the place to keep the physical file. But
Physical file name can be a diffrent one.
Restore Database <dbname> from disk= 'c:\backup\dbname.bak' with
move 'logical_mdf_name' to 'c:\mssql\data\phys_data_name._mdf',
move 'logical_ldf_name' to 'c:\mssql\data\phys_log_name.l_df'
(Replace the logical_mdf_name and logical_ldf_name with the logical name you
got from RESTORE FILELISTONLY command.
Ensure that the directory give in physical file name is there in the server)
Thanks
Hari
SQL Server MVP
Thanks
Hari
SQL Server MVP
"Polar Bear" <Polar Bear@.discussions.microsoft.com> wrote in message
news:227A549B-7D5A-48DA-A4F5-1850CE31B84B@.microsoft.com...
> Hi Good Day everybody,
> Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
> below:
> Current Server (Server A)
> a) Windows NT4 SP6a
> b) SQL 7 + SP4
> c) Default Collation: SQL_Latin1_General_CP1_CI_AS
> d) Default Data Location: E:\MSSQL7
> New Server (Server B)
> a) Window 2000 Server SP4
> b) SQL 2000 + SP3a
> c) Default Collation: Latin1_General_CP1_CI_AS (required to set as
> default)
> d) Default Data Location: D:\Program Files\Microsoft SQL Server
> Authentication Mode:
> a) Mixed Mode
> b) SQL and Windows Authentication
> * Both server are login with same userid and password.
> Problem:
> I have create and new user database "PA_CCCTemp" in the SQL2000 server.
> Besides, I also backup user database "PA_CCC" from SQL7.
> However, during I restore databases that I have backup into the SQL2000
> server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The ba
ckup
> set holds a backup of a database other than the existing 'PA_CCCTemp"
> database. Restore Databse is terminating abnormally.
> I do not know what is the problem caused. Either the database is different
> name, or the restoration location are different from the original place,
> or
> the collation is different.
> I also need help on how I can migrate the database from SQL7 to SQL 2000,
> includes user id and logon password.
> Regards,
> Polar Bear
>
Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
below:
Current Server (Server A)
a) Windows NT4 SP6a
b) SQL 7 + SP4
c) Default Collation: SQL_Latin1_General_CP1_CI_AS
d) Default Data Location: E:\MSSQL7
New Server (Server B)
a) Window 2000 Server SP4
b) SQL 2000 + SP3a
c) Default Collation: Latin1_General_CP1_CI_AS (required to set as default)
d) Default Data Location: D:\Program Files\Microsoft SQL Server
Authentication Mode:
a) Mixed Mode
b) SQL and Windows Authentication
* Both server are login with same userid and password.
Problem:
I have create and new user database "PA_CCCTemp" in the SQL2000 server.
Besides, I also backup user database "PA_CCC" from SQL7.
However, during I restore databases that I have backup into the SQL2000
server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The back
up
set holds a backup of a database other than the existing 'PA_CCCTemp"
database. Restore Databse is terminating abnormally.
I do not know what is the problem caused. Either the database is different
name, or the restoration location are different from the original place, or
the collation is different.
I also need help on how I can migrate the database from SQL7 to SQL 2000,
includes user id and logon password.
Regards,
Polar BearHi,
It seems you have given a physical location which is not in the new server
(Drive and directory) while loading in SQL 2000.
Please follow the below steps in query analyzer:-
Restore filelistonly from disk='c:\backup\dbname.bak'
( replace the 'c:\backup\dbname.bak' with the actual backup file name with
path where the file resides.)
This will give you the Logical and Physical file names of the Backup file
name. While loading you should give the
correct logical file name and the place to keep the physical file. But
Physical file name can be a diffrent one.
Restore Database <dbname> from disk= 'c:\backup\dbname.bak' with
move 'logical_mdf_name' to 'c:\mssql\data\phys_data_name._mdf',
move 'logical_ldf_name' to 'c:\mssql\data\phys_log_name.l_df'
(Replace the logical_mdf_name and logical_ldf_name with the logical name you
got from RESTORE FILELISTONLY command.
Ensure that the directory give in physical file name is there in the server)
Thanks
Hari
SQL Server MVP
Thanks
Hari
SQL Server MVP
"Polar Bear" <Polar Bear@.discussions.microsoft.com> wrote in message
news:227A549B-7D5A-48DA-A4F5-1850CE31B84B@.microsoft.com...
> Hi Good Day everybody,
> Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
> below:
> Current Server (Server A)
> a) Windows NT4 SP6a
> b) SQL 7 + SP4
> c) Default Collation: SQL_Latin1_General_CP1_CI_AS
> d) Default Data Location: E:\MSSQL7
> New Server (Server B)
> a) Window 2000 Server SP4
> b) SQL 2000 + SP3a
> c) Default Collation: Latin1_General_CP1_CI_AS (required to set as
> default)
> d) Default Data Location: D:\Program Files\Microsoft SQL Server
> Authentication Mode:
> a) Mixed Mode
> b) SQL and Windows Authentication
> * Both server are login with same userid and password.
> Problem:
> I have create and new user database "PA_CCCTemp" in the SQL2000 server.
> Besides, I also backup user database "PA_CCC" from SQL7.
> However, during I restore databases that I have backup into the SQL2000
> server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The ba
ckup
> set holds a backup of a database other than the existing 'PA_CCCTemp"
> database. Restore Databse is terminating abnormally.
> I do not know what is the problem caused. Either the database is different
> name, or the restoration location are different from the original place,
> or
> the collation is different.
> I also need help on how I can migrate the database from SQL7 to SQL 2000,
> includes user id and logon password.
> Regards,
> Polar Bear
>
Monday, March 26, 2012
Help! SQL Mail
We have SQL mail set up and running for a while, recently we upgrade our
exchange from 2000 to 2003 (in same domain but different servers), and mail
client software is still Outlook 2000 in SQL Server box. I update the mail
profile to using new mail server. No we experience a problem when we tried to
send email from SQL server. Following is error message
xp_sendmail :failed with mail error 0x8004011d. SQL mail session started.
I tested sent email from outlook, it worked fine, and also tested in SQL
mail configuration page, it stopped and started email session fine. I also
tried re-boot server, still get that error. Does anyone know how to solve of
this issue?
ThanksZou,
Have you updated the SQL Mail profile in SQL Agent as well?
May be you have to cofigure sql mail and test it out there
"Yong Zou" wrote:
> We have SQL mail set up and running for a while, recently we upgrade our
> exchange from 2000 to 2003 (in same domain but different servers), and mail
> client software is still Outlook 2000 in SQL Server box. I update the mail
> profile to using new mail server. No we experience a problem when we tried to
> send email from SQL server. Following is error message
> xp_sendmail :failed with mail error 0x8004011d. SQL mail session started.
> I tested sent email from outlook, it worked fine, and also tested in SQL
> mail configuration page, it stopped and started email session fine. I also
> tried re-boot server, still get that error. Does anyone know how to solve of
> this issue?
> Thanks|||I tried to update SQL Mail profile in SQL Agent, and I got following error
when I click test
Error 22022: SQLServerAgent Error: Unable to get the default MAPI Message
Store due to MAPI error 285: The attempt to log on to the Microsoft Exchange
Server Computer has failed.
Again, I can send and receive emails using outlook 2000 in that box. Any
idea about this error
Thanks
Yong
"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
message news:77449052-536C-4A72-8A76-027A0842BE02@.microsoft.com...
> Zou,
> Have you updated the SQL Mail profile in SQL Agent as well?
> May be you have to cofigure sql mail and test it out there
>
> "Yong Zou" wrote:
> > We have SQL mail set up and running for a while, recently we upgrade our
> > exchange from 2000 to 2003 (in same domain but different servers), and
mail
> > client software is still Outlook 2000 in SQL Server box. I update the
mail
> > profile to using new mail server. No we experience a problem when we
tried to
> > send email from SQL server. Following is error message
> >
> > xp_sendmail :failed with mail error 0x8004011d. SQL mail session
started.
> >
> > I tested sent email from outlook, it worked fine, and also tested in SQL
> > mail configuration page, it stopped and started email session fine. I
also
> > tried re-boot server, still get that error. Does anyone know how to
solve of
> > this issue?
> >
> > Thanks|||The first error indicates that SQL Mail cannot logon to your
mail server with the information you have provided in your
mail profile. The second error on the test is the same
issue. The mail profiles aren't configured properly. You can
find information on configuring mail in the following
article:
INF: How to Configure SQL Mail
http://support.microsoft.com/?id=263556
-Sue
On Mon, 8 Nov 2004 10:39:00 -0500, "Yong Zou
\(SearchIgnite\)" <yz@.yz.com> wrote:
>I tried to update SQL Mail profile in SQL Agent, and I got following error
>when I click test
>Error 22022: SQLServerAgent Error: Unable to get the default MAPI Message
>Store due to MAPI error 285: The attempt to log on to the Microsoft Exchange
>Server Computer has failed.
>Again, I can send and receive emails using outlook 2000 in that box. Any
>idea about this error
>Thanks
>Yong
>"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
>message news:77449052-536C-4A72-8A76-027A0842BE02@.microsoft.com...
>> Zou,
>> Have you updated the SQL Mail profile in SQL Agent as well?
>> May be you have to cofigure sql mail and test it out there
>>
>> "Yong Zou" wrote:
>> > We have SQL mail set up and running for a while, recently we upgrade our
>> > exchange from 2000 to 2003 (in same domain but different servers), and
>mail
>> > client software is still Outlook 2000 in SQL Server box. I update the
>mail
>> > profile to using new mail server. No we experience a problem when we
>tried to
>> > send email from SQL server. Following is error message
>> >
>> > xp_sendmail :failed with mail error 0x8004011d. SQL mail session
>started.
>> >
>> > I tested sent email from outlook, it worked fine, and also tested in SQL
>> > mail configuration page, it stopped and started email session fine. I
>also
>> > tried re-boot server, still get that error. Does anyone know how to
>solve of
>> > this issue?
>> >
>> > Thanks
>
exchange from 2000 to 2003 (in same domain but different servers), and mail
client software is still Outlook 2000 in SQL Server box. I update the mail
profile to using new mail server. No we experience a problem when we tried to
send email from SQL server. Following is error message
xp_sendmail :failed with mail error 0x8004011d. SQL mail session started.
I tested sent email from outlook, it worked fine, and also tested in SQL
mail configuration page, it stopped and started email session fine. I also
tried re-boot server, still get that error. Does anyone know how to solve of
this issue?
ThanksZou,
Have you updated the SQL Mail profile in SQL Agent as well?
May be you have to cofigure sql mail and test it out there
"Yong Zou" wrote:
> We have SQL mail set up and running for a while, recently we upgrade our
> exchange from 2000 to 2003 (in same domain but different servers), and mail
> client software is still Outlook 2000 in SQL Server box. I update the mail
> profile to using new mail server. No we experience a problem when we tried to
> send email from SQL server. Following is error message
> xp_sendmail :failed with mail error 0x8004011d. SQL mail session started.
> I tested sent email from outlook, it worked fine, and also tested in SQL
> mail configuration page, it stopped and started email session fine. I also
> tried re-boot server, still get that error. Does anyone know how to solve of
> this issue?
> Thanks|||I tried to update SQL Mail profile in SQL Agent, and I got following error
when I click test
Error 22022: SQLServerAgent Error: Unable to get the default MAPI Message
Store due to MAPI error 285: The attempt to log on to the Microsoft Exchange
Server Computer has failed.
Again, I can send and receive emails using outlook 2000 in that box. Any
idea about this error
Thanks
Yong
"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
message news:77449052-536C-4A72-8A76-027A0842BE02@.microsoft.com...
> Zou,
> Have you updated the SQL Mail profile in SQL Agent as well?
> May be you have to cofigure sql mail and test it out there
>
> "Yong Zou" wrote:
> > We have SQL mail set up and running for a while, recently we upgrade our
> > exchange from 2000 to 2003 (in same domain but different servers), and
> > client software is still Outlook 2000 in SQL Server box. I update the
> > profile to using new mail server. No we experience a problem when we
tried to
> > send email from SQL server. Following is error message
> >
> > xp_sendmail :failed with mail error 0x8004011d. SQL mail session
started.
> >
> > I tested sent email from outlook, it worked fine, and also tested in SQL
> > mail configuration page, it stopped and started email session fine. I
also
> > tried re-boot server, still get that error. Does anyone know how to
solve of
> > this issue?
> >
> > Thanks|||The first error indicates that SQL Mail cannot logon to your
mail server with the information you have provided in your
mail profile. The second error on the test is the same
issue. The mail profiles aren't configured properly. You can
find information on configuring mail in the following
article:
INF: How to Configure SQL Mail
http://support.microsoft.com/?id=263556
-Sue
On Mon, 8 Nov 2004 10:39:00 -0500, "Yong Zou
\(SearchIgnite\)" <yz@.yz.com> wrote:
>I tried to update SQL Mail profile in SQL Agent, and I got following error
>when I click test
>Error 22022: SQLServerAgent Error: Unable to get the default MAPI Message
>Store due to MAPI error 285: The attempt to log on to the Microsoft Exchange
>Server Computer has failed.
>Again, I can send and receive emails using outlook 2000 in that box. Any
>idea about this error
>Thanks
>Yong
>"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
>message news:77449052-536C-4A72-8A76-027A0842BE02@.microsoft.com...
>> Zou,
>> Have you updated the SQL Mail profile in SQL Agent as well?
>> May be you have to cofigure sql mail and test it out there
>>
>> "Yong Zou" wrote:
>> > We have SQL mail set up and running for a while, recently we upgrade our
>> > exchange from 2000 to 2003 (in same domain but different servers), and
>> > client software is still Outlook 2000 in SQL Server box. I update the
>> > profile to using new mail server. No we experience a problem when we
>tried to
>> > send email from SQL server. Following is error message
>> >
>> > xp_sendmail :failed with mail error 0x8004011d. SQL mail session
>started.
>> >
>> > I tested sent email from outlook, it worked fine, and also tested in SQL
>> > mail configuration page, it stopped and started email session fine. I
>also
>> > tried re-boot server, still get that error. Does anyone know how to
>solve of
>> > this issue?
>> >
>> > Thanks
>
Help! SQL Mail
We have SQL mail set up and running for a while, recently we upgrade our
exchange from 2000 to 2003 (in same domain but different servers), and mail
client software is still Outlook 2000 in SQL Server box. I update the mail
profile to using new mail server. No we experience a problem when we tried t
o
send email from SQL server. Following is error message
xp_sendmail :failed with mail error 0x8004011d. SQL mail session started.
I tested sent email from outlook, it worked fine, and also tested in SQL
mail configuration page, it stopped and started email session fine. I also
tried re-boot server, still get that error. Does anyone know how to solve of
this issue?
ThanksZou,
Have you updated the SQL Mail profile in SQL Agent as well?
May be you have to cofigure sql mail and test it out there
"Yong Zou" wrote:
> We have SQL mail set up and running for a while, recently we upgrade our
> exchange from 2000 to 2003 (in same domain but different servers), and mai
l
> client software is still Outlook 2000 in SQL Server box. I update the mail
> profile to using new mail server. No we experience a problem when we tried
to
> send email from SQL server. Following is error message
> xp_sendmail :failed with mail error 0x8004011d. SQL mail session started.
> I tested sent email from outlook, it worked fine, and also tested in SQL
> mail configuration page, it stopped and started email session fine. I also
> tried re-boot server, still get that error. Does anyone know how to solve
of
> this issue?
> Thanks|||I tried to update SQL Mail profile in SQL Agent, and I got following error
when I click test
Error 22022: SQLServerAgent Error: Unable to get the default MAPI Message
Store due to MAPI error 285: The attempt to log on to the Microsoft Exchange
Server Computer has failed.
Again, I can send and receive emails using outlook 2000 in that box. Any
idea about this error
Thanks
Yong
"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
message news:77449052-536C-4A72-8A76-027A0842BE02@.microsoft.com...[vbcol=seagreen]
> Zou,
> Have you updated the SQL Mail profile in SQL Agent as well?
> May be you have to cofigure sql mail and test it out there
>
> "Yong Zou" wrote:
>
mail[vbcol=seagreen]
mail[vbcol=seagreen]
tried to[vbcol=seagreen]
started.[vbcol=seagreen]
also[vbcol=seagreen]
solve of[vbcol=seagreen]|||The first error indicates that SQL Mail cannot logon to your
mail server with the information you have provided in your
mail profile. The second error on the test is the same
issue. The mail profiles aren't configured properly. You can
find information on configuring mail in the following
article:
INF: How to Configure SQL Mail
http://support.microsoft.com/?id=263556
-Sue
On Mon, 8 Nov 2004 10:39:00 -0500, "Yong Zou
\(SearchIgnite\)" <yz@.yz.com> wrote:
>I tried to update SQL Mail profile in SQL Agent, and I got following error
>when I click test
>Error 22022: SQLServerAgent Error: Unable to get the default MAPI Message
>Store due to MAPI error 285: The attempt to log on to the Microsoft Exchang
e
>Server Computer has failed.
>Again, I can send and receive emails using outlook 2000 in that box. Any
>idea about this error
>Thanks
>Yong
>"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
>message news:77449052-536C-4A72-8A76-027A0842BE02@.microsoft.com...
>mail
>mail
>tried to
>started.
>also
>solve of
>
exchange from 2000 to 2003 (in same domain but different servers), and mail
client software is still Outlook 2000 in SQL Server box. I update the mail
profile to using new mail server. No we experience a problem when we tried t
o
send email from SQL server. Following is error message
xp_sendmail :failed with mail error 0x8004011d. SQL mail session started.
I tested sent email from outlook, it worked fine, and also tested in SQL
mail configuration page, it stopped and started email session fine. I also
tried re-boot server, still get that error. Does anyone know how to solve of
this issue?
ThanksZou,
Have you updated the SQL Mail profile in SQL Agent as well?
May be you have to cofigure sql mail and test it out there
"Yong Zou" wrote:
> We have SQL mail set up and running for a while, recently we upgrade our
> exchange from 2000 to 2003 (in same domain but different servers), and mai
l
> client software is still Outlook 2000 in SQL Server box. I update the mail
> profile to using new mail server. No we experience a problem when we tried
to
> send email from SQL server. Following is error message
> xp_sendmail :failed with mail error 0x8004011d. SQL mail session started.
> I tested sent email from outlook, it worked fine, and also tested in SQL
> mail configuration page, it stopped and started email session fine. I also
> tried re-boot server, still get that error. Does anyone know how to solve
of
> this issue?
> Thanks|||I tried to update SQL Mail profile in SQL Agent, and I got following error
when I click test
Error 22022: SQLServerAgent Error: Unable to get the default MAPI Message
Store due to MAPI error 285: The attempt to log on to the Microsoft Exchange
Server Computer has failed.
Again, I can send and receive emails using outlook 2000 in that box. Any
idea about this error
Thanks
Yong
"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
message news:77449052-536C-4A72-8A76-027A0842BE02@.microsoft.com...[vbcol=seagreen]
> Zou,
> Have you updated the SQL Mail profile in SQL Agent as well?
> May be you have to cofigure sql mail and test it out there
>
> "Yong Zou" wrote:
>
mail[vbcol=seagreen]
mail[vbcol=seagreen]
tried to[vbcol=seagreen]
started.[vbcol=seagreen]
also[vbcol=seagreen]
solve of[vbcol=seagreen]|||The first error indicates that SQL Mail cannot logon to your
mail server with the information you have provided in your
mail profile. The second error on the test is the same
issue. The mail profiles aren't configured properly. You can
find information on configuring mail in the following
article:
INF: How to Configure SQL Mail
http://support.microsoft.com/?id=263556
-Sue
On Mon, 8 Nov 2004 10:39:00 -0500, "Yong Zou
\(SearchIgnite\)" <yz@.yz.com> wrote:
>I tried to update SQL Mail profile in SQL Agent, and I got following error
>when I click test
>Error 22022: SQLServerAgent Error: Unable to get the default MAPI Message
>Store due to MAPI error 285: The attempt to log on to the Microsoft Exchang
e
>Server Computer has failed.
>Again, I can send and receive emails using outlook 2000 in that box. Any
>idea about this error
>Thanks
>Yong
>"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
>message news:77449052-536C-4A72-8A76-027A0842BE02@.microsoft.com...
>tried to
>started.
>also
>solve of
>
Help! SQL Mail
We have SQL mail set up and running for a while, recently we upgrade our
exchange from 2000 to 2003 (in same domain but different servers), and mail
client software is still Outlook 2000 in SQL Server box. I update the mail
profile to using new mail server. No we experience a problem when we tried to
send email from SQL server. Following is error message
xp_sendmail :failed with mail error 0x8004011d. SQL mail session started.
I tested sent email from outlook, it worked fine, and also tested in SQL
mail configuration page, it stopped and started email session fine. I also
tried re-boot server, still get that error. Does anyone know how to solve of
this issue?
Thanks
Zou,
Have you updated the SQL Mail profile in SQL Agent as well?
May be you have to cofigure sql mail and test it out there
"Yong Zou" wrote:
> We have SQL mail set up and running for a while, recently we upgrade our
> exchange from 2000 to 2003 (in same domain but different servers), and mail
> client software is still Outlook 2000 in SQL Server box. I update the mail
> profile to using new mail server. No we experience a problem when we tried to
> send email from SQL server. Following is error message
> xp_sendmail :failed with mail error 0x8004011d. SQL mail session started.
> I tested sent email from outlook, it worked fine, and also tested in SQL
> mail configuration page, it stopped and started email session fine. I also
> tried re-boot server, still get that error. Does anyone know how to solve of
> this issue?
> Thanks
|||I tried to update SQL Mail profile in SQL Agent, and I got following error
when I click test
Error 22022: SQLServerAgent Error: Unable to get the default MAPI Message
Store due to MAPI error 285: The attempt to log on to the Microsoft Exchange
Server Computer has failed.
Again, I can send and receive emails using outlook 2000 in that box. Any
idea about this error
Thanks
Yong
"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
message news:77449052-536C-4A72-8A76-027A0842BE02@.microsoft.com...[vbcol=seagreen]
> Zou,
> Have you updated the SQL Mail profile in SQL Agent as well?
> May be you have to cofigure sql mail and test it out there
>
> "Yong Zou" wrote:
mail[vbcol=seagreen]
mail[vbcol=seagreen]
tried to[vbcol=seagreen]
started.[vbcol=seagreen]
also[vbcol=seagreen]
solve of[vbcol=seagreen]
|||The first error indicates that SQL Mail cannot logon to your
mail server with the information you have provided in your
mail profile. The second error on the test is the same
issue. The mail profiles aren't configured properly. You can
find information on configuring mail in the following
article:
INF: How to Configure SQL Mail
http://support.microsoft.com/?id=263556
-Sue
On Mon, 8 Nov 2004 10:39:00 -0500, "Yong Zou
\(SearchIgnite\)" <yz@.yz.com> wrote:
>I tried to update SQL Mail profile in SQL Agent, and I got following error
>when I click test
>Error 22022: SQLServerAgent Error: Unable to get the default MAPI Message
>Store due to MAPI error 285: The attempt to log on to the Microsoft Exchange
>Server Computer has failed.
>Again, I can send and receive emails using outlook 2000 in that box. Any
>idea about this error
>Thanks
>Yong
>"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
>message news:77449052-536C-4A72-8A76-027A0842BE02@.microsoft.com...
>mail
>mail
>tried to
>started.
>also
>solve of
>
sql
exchange from 2000 to 2003 (in same domain but different servers), and mail
client software is still Outlook 2000 in SQL Server box. I update the mail
profile to using new mail server. No we experience a problem when we tried to
send email from SQL server. Following is error message
xp_sendmail :failed with mail error 0x8004011d. SQL mail session started.
I tested sent email from outlook, it worked fine, and also tested in SQL
mail configuration page, it stopped and started email session fine. I also
tried re-boot server, still get that error. Does anyone know how to solve of
this issue?
Thanks
Zou,
Have you updated the SQL Mail profile in SQL Agent as well?
May be you have to cofigure sql mail and test it out there
"Yong Zou" wrote:
> We have SQL mail set up and running for a while, recently we upgrade our
> exchange from 2000 to 2003 (in same domain but different servers), and mail
> client software is still Outlook 2000 in SQL Server box. I update the mail
> profile to using new mail server. No we experience a problem when we tried to
> send email from SQL server. Following is error message
> xp_sendmail :failed with mail error 0x8004011d. SQL mail session started.
> I tested sent email from outlook, it worked fine, and also tested in SQL
> mail configuration page, it stopped and started email session fine. I also
> tried re-boot server, still get that error. Does anyone know how to solve of
> this issue?
> Thanks
|||I tried to update SQL Mail profile in SQL Agent, and I got following error
when I click test
Error 22022: SQLServerAgent Error: Unable to get the default MAPI Message
Store due to MAPI error 285: The attempt to log on to the Microsoft Exchange
Server Computer has failed.
Again, I can send and receive emails using outlook 2000 in that box. Any
idea about this error
Thanks
Yong
"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
message news:77449052-536C-4A72-8A76-027A0842BE02@.microsoft.com...[vbcol=seagreen]
> Zou,
> Have you updated the SQL Mail profile in SQL Agent as well?
> May be you have to cofigure sql mail and test it out there
>
> "Yong Zou" wrote:
mail[vbcol=seagreen]
mail[vbcol=seagreen]
tried to[vbcol=seagreen]
started.[vbcol=seagreen]
also[vbcol=seagreen]
solve of[vbcol=seagreen]
|||The first error indicates that SQL Mail cannot logon to your
mail server with the information you have provided in your
mail profile. The second error on the test is the same
issue. The mail profiles aren't configured properly. You can
find information on configuring mail in the following
article:
INF: How to Configure SQL Mail
http://support.microsoft.com/?id=263556
-Sue
On Mon, 8 Nov 2004 10:39:00 -0500, "Yong Zou
\(SearchIgnite\)" <yz@.yz.com> wrote:
>I tried to update SQL Mail profile in SQL Agent, and I got following error
>when I click test
>Error 22022: SQLServerAgent Error: Unable to get the default MAPI Message
>Store due to MAPI error 285: The attempt to log on to the Microsoft Exchange
>Server Computer has failed.
>Again, I can send and receive emails using outlook 2000 in that box. Any
>idea about this error
>Thanks
>Yong
>"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
>message news:77449052-536C-4A72-8A76-027A0842BE02@.microsoft.com...
>tried to
>started.
>also
>solve of
>
sql
Help! SQL errors after Win 2003 Upgrade
Help! I am in a jam and need help suggestions and ideas ASAP!
After performing an in-service operating system upgrade from Win 2000 to Win
2003 both of our SQL Server applications are behaving very badly. The SQL
applications are either giving us errors or unable to run at all. Veritas
Backup Exec is unablel to b
rowse the SQL Database and after working with them for several hours they ar
e stumped.
Has anyone else heard of this issue? Would a reinstall of SQL SP3a fix thi
s mess? Or is the best fix going to be an all night server format and reins
tall of Windows 2003, SQL 2000, and all of the applications?
Thanks! in advance for anything you can give me.
NC Beach BumReapply SP3a.
Uninstall Veritas agent.
Reinstall Veritas agent.
What other application connectivity errors are you getting?
Check your alias settings in Client Network Utility. You may need remove
any alias settings that force named pipes connection to a local instance. I
have seen some problems with SQL Agent on those circumstances
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"NC Beach Bum" <anonymous@.discussions.microsoft.com> wrote in message
news:66808E92-5A64-45AB-91C0-25321EC56C6C@.microsoft.com...
> Help! I am in a jam and need help suggestions and ideas ASAP!
> After performing an in-service operating system upgrade from Win 2000 to
Win 2003 both of our SQL Server applications are behaving very badly. The
SQL applications are either giving us errors or unable to run at all.
Veritas Backup Exec is unablel to browse the SQL Database and after working
with them for several hours they are stumped.
> Has anyone else heard of this issue? Would a reinstall of SQL SP3a fix
this mess? Or is the best fix going to be an all night server format and
reinstall of Windows 2003, SQL 2000, and all of the applications?
> Thanks! in advance for anything you can give me.
> NC Beach Bum
>|||Jeff,
THANKS! for your quick reply.
What I see in the applications are unable to make connections.
The web application is getting this error "Method '~' of object '~' failed."
It looks like the SQL Connections have been trashed.
One Accounting product is getting an error about not being able to log onto
the database.
Another Accounting product on the same SQL Server is not allowing us to post
data to the database.
I can live with the Veritas issues but the Accounting folks are getting a bi
t nasty.
Have you heard of this before and how confident are you that SQL SP3a will p
ut us back to normal?
NC Beach Bum|||"NC Beach Bum" <anonymous@.discussions.microsoft.com> wrote in message
news:DF20331F-C553-48C8-8D31-9A5745A81F24@.microsoft.com...
> Jeff,
> THANKS! for your quick reply.
> What I see in the applications are unable to make connections.
Try to add this in your connection string:
"Network Library=DBMSSOCN"|||Geoff,
I am going to try and update MDAC and the SQL Service Pack
1) Run the MDAC 2.8 install
2) Run the SQL SP3a install
Does this make sense to you and is this the order you would suggest?
Thanks! NC Beach Bum|||That is the correct order. It shouldn't hurt.
You should start checking connectivity an dsee what does and doesn't
connect. Start with IP connectivity (Ping) and then work on SQL
connectivity with query analyzer. Try local and remote from Query Analyzer
and see what happens. Find out what connectivity works and what does not.
If you can connect locally, what does 'SELECT @.@.Version' return? Windows
2003 will disable the IP stack for SQL without SP3a to protect from the
Slammer worm.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"NC Beach Bum" <anonymous@.discussions.microsoft.com> wrote in message
news:59DBF52D-F7AE-4ACD-81A4-639C8E7E4D95@.microsoft.com...
> Geoff,
> I am going to try and update MDAC and the SQL Service Pack
> 1) Run the MDAC 2.8 install
> 2) Run the SQL SP3a install
> Does this make sense to you and is this the order you would suggest?
> Thanks! NC Beach Bum
After performing an in-service operating system upgrade from Win 2000 to Win
2003 both of our SQL Server applications are behaving very badly. The SQL
applications are either giving us errors or unable to run at all. Veritas
Backup Exec is unablel to b
rowse the SQL Database and after working with them for several hours they ar
e stumped.
Has anyone else heard of this issue? Would a reinstall of SQL SP3a fix thi
s mess? Or is the best fix going to be an all night server format and reins
tall of Windows 2003, SQL 2000, and all of the applications?
Thanks! in advance for anything you can give me.
NC Beach BumReapply SP3a.
Uninstall Veritas agent.
Reinstall Veritas agent.
What other application connectivity errors are you getting?
Check your alias settings in Client Network Utility. You may need remove
any alias settings that force named pipes connection to a local instance. I
have seen some problems with SQL Agent on those circumstances
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"NC Beach Bum" <anonymous@.discussions.microsoft.com> wrote in message
news:66808E92-5A64-45AB-91C0-25321EC56C6C@.microsoft.com...
> Help! I am in a jam and need help suggestions and ideas ASAP!
> After performing an in-service operating system upgrade from Win 2000 to
Win 2003 both of our SQL Server applications are behaving very badly. The
SQL applications are either giving us errors or unable to run at all.
Veritas Backup Exec is unablel to browse the SQL Database and after working
with them for several hours they are stumped.
> Has anyone else heard of this issue? Would a reinstall of SQL SP3a fix
this mess? Or is the best fix going to be an all night server format and
reinstall of Windows 2003, SQL 2000, and all of the applications?
> Thanks! in advance for anything you can give me.
> NC Beach Bum
>|||Jeff,
THANKS! for your quick reply.
What I see in the applications are unable to make connections.
The web application is getting this error "Method '~' of object '~' failed."
It looks like the SQL Connections have been trashed.
One Accounting product is getting an error about not being able to log onto
the database.
Another Accounting product on the same SQL Server is not allowing us to post
data to the database.
I can live with the Veritas issues but the Accounting folks are getting a bi
t nasty.
Have you heard of this before and how confident are you that SQL SP3a will p
ut us back to normal?
NC Beach Bum|||"NC Beach Bum" <anonymous@.discussions.microsoft.com> wrote in message
news:DF20331F-C553-48C8-8D31-9A5745A81F24@.microsoft.com...
> Jeff,
> THANKS! for your quick reply.
> What I see in the applications are unable to make connections.
Try to add this in your connection string:
"Network Library=DBMSSOCN"|||Geoff,
I am going to try and update MDAC and the SQL Service Pack
1) Run the MDAC 2.8 install
2) Run the SQL SP3a install
Does this make sense to you and is this the order you would suggest?
Thanks! NC Beach Bum|||That is the correct order. It shouldn't hurt.
You should start checking connectivity an dsee what does and doesn't
connect. Start with IP connectivity (Ping) and then work on SQL
connectivity with query analyzer. Try local and remote from Query Analyzer
and see what happens. Find out what connectivity works and what does not.
If you can connect locally, what does 'SELECT @.@.Version' return? Windows
2003 will disable the IP stack for SQL without SP3a to protect from the
Slammer worm.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"NC Beach Bum" <anonymous@.discussions.microsoft.com> wrote in message
news:59DBF52D-F7AE-4ACD-81A4-639C8E7E4D95@.microsoft.com...
> Geoff,
> I am going to try and update MDAC and the SQL Service Pack
> 1) Run the MDAC 2.8 install
> 2) Run the SQL SP3a install
> Does this make sense to you and is this the order you would suggest?
> Thanks! NC Beach Bum
Subscribe to:
Posts (Atom)