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 windows. Show all posts
Showing posts with label windows. 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 Service Manager is not connected
After completing a successful installing of MSDE build 2000.80.760.0
on my Windows XP Version 5.1.2600 Service Pack 1 Build 2600 I am
encountering the following issue:
The SQL Service Manager Tray icon indicator is in solid white state and when I
mouse over, it displays "Not Connected = \\".
Attempting to double click the guy results with both the Server and the
Service textboxes being empty. Same when I collapse their drop down
menus, they do not list any database instances. Refresh does not
solve the problem either.
I get the following error in the event log:
Event Type:Warning
Event Source:MSSQL$VSDOTNET
Event Category:(8)
Event ID:19011
Date:4/13/2004
Time:10:59:05 AM
User:N/A
Computer:TOOTI
Description:
The description for Event ID ( 19011 ) in Source ( MSSQL$VSDOTNET
) cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages from a
remote computer. You may be able to use the /AUXSOURCE= flag to
retrieve this description; see Help and Support for details. The
following information is part of the event: (SpnRegister) : Error 1231.
Some notes:
* I have installed MSDE using the following command-line:
setup INSTANCENAME=VSDOTNET SAPWD=<my password>
* My system has Office 2003 Pro and Visual Studio 2003.net
* I removed Business Contact Manager and attempted to install MSDE
once again, however the issue remains.
* I am running file and print sharing on my internal (disconnected) nic
adapter
My configuration is:
OS NameMicrosoft Windows XP Professional
Version5.1.2600 Service Pack 1 Build 2600
OS ManufacturerMicrosoft Corporation
System ManufacturerAcer
System ModelTravelMate 800
System TypeX86-based PC
Processorx86 Family 6 Model 9 Stepping 5 GenuineIntel
~1598 Mhz
BIOS Version/DateACER 4A14, 9/19/2003
SMBIOS Version2.31
Windows DirectoryC:\WINDOWS
System DirectoryC:\WINDOWS\System32
Boot Device\Device\HarddiskVolume1
LocaleUnited States
Hardware Abstraction LayerVersion = "5.1.2600.1106
(xpsp1.020828-1920)"
Total Physical Memory512.00 MB
Available Physical Memory265.73 MB
Total Virtual Memory1.72 GB
Available Virtual Memory1.27 GB
Page File Space1.22 GB
Page FileC:\pagefile.sys
LOG\ERROR.LOG:
2004-04-13 10:59:01.71 server Microsoft SQL Server 2000 -
8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service
Pack 1)
2004-04-13 10:59:01.76 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-04-13 10:59:01.76 server All rights reserved.
2004-04-13 10:59:01.76 server Server Process ID is 652.
2004-04-13 10:59:01.76 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL
Server\MSSQL$VSDOTNET\LOG\ERRORLOG'.
2004-04-13 10:59:01.89 server SQL Server is starting at priority
class 'normal'(1 CPU detected).
2004-04-13 10:59:03.67 server SQL Server configured for thread
mode processing.
2004-04-13 10:59:03.83 server Using dynamic lock allocation. [500]
Lock Blocks, [1000] Lock Owner Blocks.
2004-04-13 10:59:04.77 spid3 Starting up database 'master'.
2004-04-13 10:59:05.51 server Using 'SSNETLIB.DLL' version
'8.0.766'.
2004-04-13 10:59:05.51 spid5 Starting up database 'model'.
2004-04-13 10:59:05.75 spid3 Server name is 'TOOTI\VSDOTNET'.
2004-04-13 10:59:05.75 spid3 Skipping startup of clean database id
4
2004-04-13 10:59:05.90 server SQL server listening on Shared
Memory.
2004-04-13 10:59:05.92 server SQL Server is ready for client
connections
2004-04-13 10:59:07.20 spid5 Clearing tempdb database.
2004-04-13 10:59:12.75 spid5 Starting up database 'tempdb'.
2004-04-13 10:59:13.44 spid3 Recovery complete.
2004-04-13 10:59:13.44 spid3 SQL global counter collection task is
created.
I thank anyone in advance for a quick response.
-Itai
hi Itai,
"Itai" <itaindia2002@.yahoo.com> ha scritto nel messaggio
news:ab661ff4.0404130215.18d18b5c@.posting.google.c om...
> After completing a successful installing of MSDE build 2000.80.760.0
> on my Windows XP Version 5.1.2600 Service Pack 1 Build 2600 I am
> encountering the following issue:
> The SQL Service Manager Tray icon indicator is in solid white state and
when I
> mouse over, it displays "Not Connected = \\".
> Attempting to double click the guy results with both the Server and the
> Service textboxes being empty. Same when I collapse their drop down
> menus, they do not list any database instances. Refresh does not
> solve the problem either.
> I get the following error in the event log:
sometimes the service manager fails to load the combo with the available SQL
Server instances when they are installed with disabled network protocols,
due to ODBC related "features" at this regard... but your logs seems to
show your instance is running... try typing the server instance name in the
combobox like YourComputerName\VSDOTNET ...
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
on my Windows XP Version 5.1.2600 Service Pack 1 Build 2600 I am
encountering the following issue:
The SQL Service Manager Tray icon indicator is in solid white state and when I
mouse over, it displays "Not Connected = \\".
Attempting to double click the guy results with both the Server and the
Service textboxes being empty. Same when I collapse their drop down
menus, they do not list any database instances. Refresh does not
solve the problem either.
I get the following error in the event log:
Event Type:Warning
Event Source:MSSQL$VSDOTNET
Event Category:(8)
Event ID:19011
Date:4/13/2004
Time:10:59:05 AM
User:N/A
Computer:TOOTI
Description:
The description for Event ID ( 19011 ) in Source ( MSSQL$VSDOTNET
) cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages from a
remote computer. You may be able to use the /AUXSOURCE= flag to
retrieve this description; see Help and Support for details. The
following information is part of the event: (SpnRegister) : Error 1231.
Some notes:
* I have installed MSDE using the following command-line:
setup INSTANCENAME=VSDOTNET SAPWD=<my password>
* My system has Office 2003 Pro and Visual Studio 2003.net
* I removed Business Contact Manager and attempted to install MSDE
once again, however the issue remains.
* I am running file and print sharing on my internal (disconnected) nic
adapter
My configuration is:
OS NameMicrosoft Windows XP Professional
Version5.1.2600 Service Pack 1 Build 2600
OS ManufacturerMicrosoft Corporation
System ManufacturerAcer
System ModelTravelMate 800
System TypeX86-based PC
Processorx86 Family 6 Model 9 Stepping 5 GenuineIntel
~1598 Mhz
BIOS Version/DateACER 4A14, 9/19/2003
SMBIOS Version2.31
Windows DirectoryC:\WINDOWS
System DirectoryC:\WINDOWS\System32
Boot Device\Device\HarddiskVolume1
LocaleUnited States
Hardware Abstraction LayerVersion = "5.1.2600.1106
(xpsp1.020828-1920)"
Total Physical Memory512.00 MB
Available Physical Memory265.73 MB
Total Virtual Memory1.72 GB
Available Virtual Memory1.27 GB
Page File Space1.22 GB
Page FileC:\pagefile.sys
LOG\ERROR.LOG:
2004-04-13 10:59:01.71 server Microsoft SQL Server 2000 -
8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service
Pack 1)
2004-04-13 10:59:01.76 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-04-13 10:59:01.76 server All rights reserved.
2004-04-13 10:59:01.76 server Server Process ID is 652.
2004-04-13 10:59:01.76 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL
Server\MSSQL$VSDOTNET\LOG\ERRORLOG'.
2004-04-13 10:59:01.89 server SQL Server is starting at priority
class 'normal'(1 CPU detected).
2004-04-13 10:59:03.67 server SQL Server configured for thread
mode processing.
2004-04-13 10:59:03.83 server Using dynamic lock allocation. [500]
Lock Blocks, [1000] Lock Owner Blocks.
2004-04-13 10:59:04.77 spid3 Starting up database 'master'.
2004-04-13 10:59:05.51 server Using 'SSNETLIB.DLL' version
'8.0.766'.
2004-04-13 10:59:05.51 spid5 Starting up database 'model'.
2004-04-13 10:59:05.75 spid3 Server name is 'TOOTI\VSDOTNET'.
2004-04-13 10:59:05.75 spid3 Skipping startup of clean database id
4
2004-04-13 10:59:05.90 server SQL server listening on Shared
Memory.
2004-04-13 10:59:05.92 server SQL Server is ready for client
connections
2004-04-13 10:59:07.20 spid5 Clearing tempdb database.
2004-04-13 10:59:12.75 spid5 Starting up database 'tempdb'.
2004-04-13 10:59:13.44 spid3 Recovery complete.
2004-04-13 10:59:13.44 spid3 SQL global counter collection task is
created.
I thank anyone in advance for a quick response.
-Itai
hi Itai,
"Itai" <itaindia2002@.yahoo.com> ha scritto nel messaggio
news:ab661ff4.0404130215.18d18b5c@.posting.google.c om...
> After completing a successful installing of MSDE build 2000.80.760.0
> on my Windows XP Version 5.1.2600 Service Pack 1 Build 2600 I am
> encountering the following issue:
> The SQL Service Manager Tray icon indicator is in solid white state and
when I
> mouse over, it displays "Not Connected = \\".
> Attempting to double click the guy results with both the Server and the
> Service textboxes being empty. Same when I collapse their drop down
> menus, they do not list any database instances. Refresh does not
> solve the problem either.
> I get the following error in the event log:
sometimes the service manager fails to load the combo with the available SQL
Server instances when they are installed with disabled network protocols,
due to ODBC related "features" at this regard... but your logs seems to
show your instance is running... try typing the server instance name in the
combobox like YourComputerName\VSDOTNET ...
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Help! SQL Server 2000 extended stored procedure hangs in Windows 98
I am trying to run xp_cmdshell from the Query Analyzer using SQL
Server 2000 running on Windows 98.
Server 2000 running on Windows 98.
It seems like it should be simple - I'm typing
xp_cmdshell 'dir *.exe'
in the Query Analyzer in the Master db. I'm logged in as sa.
The timer starts running and never stops. No error message.
Can anyone PLEASE help me with this? Any suggestions would be
appreciated. Are SQL Server 2000 extended stored procedures not
supported in Windows 98? I've tried searching the Knowledge Base but
can't find anything.
Thanks!sylmart7 (sylmart7@.aol.com) writes:
> I am trying to run xp_cmdshell from the Query Analyzer using SQL
> Server 2000 running on Windows 98.
> It seems like it should be simple - I'm typing
> xp_cmdshell 'dir *.exe'
> in the Query Analyzer in the Master db. I'm logged in as sa.
> The timer starts running and never stops. No error message.
> Can anyone PLEASE help me with this? Any suggestions would be
> appreciated. Are SQL Server 2000 extended stored procedures not
> supported in Windows 98? I've tried searching the Knowledge Base but
> can't find anything.
As I have no experience at all of Windows 98, I cannot really help. What
I can say, though, after having read the topic on xp_cmdshell in Books
Online is: yes, xp_cmdshell is supported on Win98. The article mentions
several restrictions with regards to security context and return value
on Win 98, so obviously you should be able to use it.
--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
Help! Set up Windows Group to access application
I am sorry for cross-posting, but I'm used to posting in the programming
section and posted there as a force of habit.
I have an application written in VB6 that is hooked up to Sql Server 2005.
I can't seem to get a regular user to be able to access it. There's a Sql
Server error:
"Login failed for user ''. The user is not associated with a trusted Sql
Server connection." Note that it doesn't name the user; just supplies blank
single quotes together.
I want to use Windows Authentication. I set up a group in Active Directory
called CustomerService.
Can someone show me step by step how I set up the CustomerService group to
access the database MyDatabase?
Any help will be greatly appreciated!!
Sandy> "Login failed for user ''. The user is not associated with a trusted Sql
> Server connection." Note that it doesn't name the user; just supplies
> blank
> single quotes together.
I'm not sure of the significance of the empty string. Most often, the
message specifies user "(NULL)" and that means that the users Windows
credentials could not be verified and may be due to a number of different
reasons. For example, I've seen that happen when the client computer clock
was significantly different that the domain controller.
> Can someone show me step by step how I set up the CustomerService group to
> access the database MyDatabase?
You can grant all members of that AD group access to the database as
follows:
SQL 7 and SQL 2000:
EXEC sp_grantlogin 'MyDomain\CustomerService'
USE MyDatabase
EXEC sp_grantdbaccess 'MyDomain\CustomerService'
SQL 2005:
CREATE LOGIN [MyDomain\CustomerService]
FROM WINDOWS
USE MyDatabase
CREATE USER [MyDomain\CustomerService]
Hope this helps.
Dan Guzman
SQL Server MVP
"Sandy" <Sandy@.discussions.microsoft.com> wrote in message
news:A3D05D3B-79C1-4318-AFE7-E65604A0EFE5@.microsoft.com...
>I am sorry for cross-posting, but I'm used to posting in the programming
> section and posted there as a force of habit.
> I have an application written in VB6 that is hooked up to Sql Server 2005.
> I can't seem to get a regular user to be able to access it. There's a Sql
> Server error:
> "Login failed for user ''. The user is not associated with a trusted Sql
> Server connection." Note that it doesn't name the user; just supplies
> blank
> single quotes together.
> I want to use Windows Authentication. I set up a group in Active
> Directory
> called CustomerService.
> Can someone show me step by step how I set up the CustomerService group to
> access the database MyDatabase?
> Any help will be greatly appreciated!!
> --
> Sandy|||You would execute something like the following:
USE master
GO
CREATE LOGIN [YourDomain\SomeGroup]
FROM WINDOWS
WITH DEFAULT_DATABASE= YourDefaultDatabaseName
GO
USE YourDatabase
GO
CREATE USER [YourDomain\SomeGroup]
FOR LOGIN [YourDomain\SomeGroup]
WITH DEFAULT_SCHEMA= YourDefaultSchemaName
That's just to access the database. Then you need to figure
out permissions in the database.
-Sue
On Mon, 14 May 2007 17:45:01 -0700, Sandy
<Sandy@.discussions.microsoft.com> wrote:
>I am sorry for cross-posting, but I'm used to posting in the programming
>section and posted there as a force of habit.
>I have an application written in VB6 that is hooked up to Sql Server 2005.
>I can't seem to get a regular user to be able to access it. There's a Sql
>Server error:
>"Login failed for user ''. The user is not associated with a trusted Sql
>Server connection." Note that it doesn't name the user; just supplies blan
k
>single quotes together.
>I want to use Windows Authentication. I set up a group in Active Directory
>called CustomerService.
>Can someone show me step by step how I set up the CustomerService group to
>access the database MyDatabase?
>Any help will be greatly appreciated!!|||Thanks for your reply, Sue.
Would I use dbo as YourDefaultSchemaName?
I need all the users in YourDomain/SomeGroup to be able to execute stored
procedures, insert, update and delete on all tables in the database. How
would I word that?
Again, any help is greatly appreciated!
--
Sandy
"Sue Hoegemeier" wrote:
> You would execute something like the following:
> USE master
> GO
> CREATE LOGIN [YourDomain\SomeGroup]
> FROM WINDOWS
> WITH DEFAULT_DATABASE= YourDefaultDatabaseName
> GO
> USE YourDatabase
> GO
> CREATE USER [YourDomain\SomeGroup]
> FOR LOGIN [YourDomain\SomeGroup]
> WITH DEFAULT_SCHEMA= YourDefaultSchemaName
> That's just to access the database. Then you need to figure
> out permissions in the database.
> -Sue
> On Mon, 14 May 2007 17:45:01 -0700, Sandy
> <Sandy@.discussions.microsoft.com> wrote:
>
>
section and posted there as a force of habit.
I have an application written in VB6 that is hooked up to Sql Server 2005.
I can't seem to get a regular user to be able to access it. There's a Sql
Server error:
"Login failed for user ''. The user is not associated with a trusted Sql
Server connection." Note that it doesn't name the user; just supplies blank
single quotes together.
I want to use Windows Authentication. I set up a group in Active Directory
called CustomerService.
Can someone show me step by step how I set up the CustomerService group to
access the database MyDatabase?
Any help will be greatly appreciated!!
Sandy> "Login failed for user ''. The user is not associated with a trusted Sql
> Server connection." Note that it doesn't name the user; just supplies
> blank
> single quotes together.
I'm not sure of the significance of the empty string. Most often, the
message specifies user "(NULL)" and that means that the users Windows
credentials could not be verified and may be due to a number of different
reasons. For example, I've seen that happen when the client computer clock
was significantly different that the domain controller.
> Can someone show me step by step how I set up the CustomerService group to
> access the database MyDatabase?
You can grant all members of that AD group access to the database as
follows:
SQL 7 and SQL 2000:
EXEC sp_grantlogin 'MyDomain\CustomerService'
USE MyDatabase
EXEC sp_grantdbaccess 'MyDomain\CustomerService'
SQL 2005:
CREATE LOGIN [MyDomain\CustomerService]
FROM WINDOWS
USE MyDatabase
CREATE USER [MyDomain\CustomerService]
Hope this helps.
Dan Guzman
SQL Server MVP
"Sandy" <Sandy@.discussions.microsoft.com> wrote in message
news:A3D05D3B-79C1-4318-AFE7-E65604A0EFE5@.microsoft.com...
>I am sorry for cross-posting, but I'm used to posting in the programming
> section and posted there as a force of habit.
> I have an application written in VB6 that is hooked up to Sql Server 2005.
> I can't seem to get a regular user to be able to access it. There's a Sql
> Server error:
> "Login failed for user ''. The user is not associated with a trusted Sql
> Server connection." Note that it doesn't name the user; just supplies
> blank
> single quotes together.
> I want to use Windows Authentication. I set up a group in Active
> Directory
> called CustomerService.
> Can someone show me step by step how I set up the CustomerService group to
> access the database MyDatabase?
> Any help will be greatly appreciated!!
> --
> Sandy|||You would execute something like the following:
USE master
GO
CREATE LOGIN [YourDomain\SomeGroup]
FROM WINDOWS
WITH DEFAULT_DATABASE= YourDefaultDatabaseName
GO
USE YourDatabase
GO
CREATE USER [YourDomain\SomeGroup]
FOR LOGIN [YourDomain\SomeGroup]
WITH DEFAULT_SCHEMA= YourDefaultSchemaName
That's just to access the database. Then you need to figure
out permissions in the database.
-Sue
On Mon, 14 May 2007 17:45:01 -0700, Sandy
<Sandy@.discussions.microsoft.com> wrote:
>I am sorry for cross-posting, but I'm used to posting in the programming
>section and posted there as a force of habit.
>I have an application written in VB6 that is hooked up to Sql Server 2005.
>I can't seem to get a regular user to be able to access it. There's a Sql
>Server error:
>"Login failed for user ''. The user is not associated with a trusted Sql
>Server connection." Note that it doesn't name the user; just supplies blan
k
>single quotes together.
>I want to use Windows Authentication. I set up a group in Active Directory
>called CustomerService.
>Can someone show me step by step how I set up the CustomerService group to
>access the database MyDatabase?
>Any help will be greatly appreciated!!|||Thanks for your reply, Sue.
Would I use dbo as YourDefaultSchemaName?
I need all the users in YourDomain/SomeGroup to be able to execute stored
procedures, insert, update and delete on all tables in the database. How
would I word that?
Again, any help is greatly appreciated!
--
Sandy
"Sue Hoegemeier" wrote:
> You would execute something like the following:
> USE master
> GO
> CREATE LOGIN [YourDomain\SomeGroup]
> FROM WINDOWS
> WITH DEFAULT_DATABASE= YourDefaultDatabaseName
> GO
> USE YourDatabase
> GO
> CREATE USER [YourDomain\SomeGroup]
> FOR LOGIN [YourDomain\SomeGroup]
> WITH DEFAULT_SCHEMA= YourDefaultSchemaName
> That's just to access the database. Then you need to figure
> out permissions in the database.
> -Sue
> On Mon, 14 May 2007 17:45:01 -0700, Sandy
> <Sandy@.discussions.microsoft.com> wrote:
>
>
Wednesday, March 21, 2012
Help! Need to migrate Windows 2000 Server/SQL Server to Windows 2003 Advanced Server/SQL A
We have existing machine runing Windows 2000 Server and SQL Server
2000. We will be buying a larger machine and would like to migrate all
data/processes/DTSs/jobs into new machine which will be running
Windows 2003 Advanced Server + SQL 2000 Advanced Server edition.
Our goal is not only preserve all jobs/data/packages but also leve the
same name of the SQL server.
How can we do that? are there any reliable recepies?
Thanks in advance!
Gene.See if this helps:
http://vyaskn.tripod.com/moving_sql_server.htm
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Gene Fichtenholz" <gfichten@.hotmail.com> wrote in message
news:6c807745.0402231156.2abf1586@.posting.google.com...
We have existing machine runing Windows 2000 Server and SQL Server
2000. We will be buying a larger machine and would like to migrate all
data/processes/DTSs/jobs into new machine which will be running
Windows 2003 Advanced Server + SQL 2000 Advanced Server edition.
Our goal is not only preserve all jobs/data/packages but also leve the
same name of the SQL server.
How can we do that? are there any reliable recepies?
Thanks in advance!
Gene.
2000. We will be buying a larger machine and would like to migrate all
data/processes/DTSs/jobs into new machine which will be running
Windows 2003 Advanced Server + SQL 2000 Advanced Server edition.
Our goal is not only preserve all jobs/data/packages but also leve the
same name of the SQL server.
How can we do that? are there any reliable recepies?
Thanks in advance!
Gene.See if this helps:
http://vyaskn.tripod.com/moving_sql_server.htm
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Gene Fichtenholz" <gfichten@.hotmail.com> wrote in message
news:6c807745.0402231156.2abf1586@.posting.google.com...
We have existing machine runing Windows 2000 Server and SQL Server
2000. We will be buying a larger machine and would like to migrate all
data/processes/DTSs/jobs into new machine which will be running
Windows 2003 Advanced Server + SQL 2000 Advanced Server edition.
Our goal is not only preserve all jobs/data/packages but also leve the
same name of the SQL server.
How can we do that? are there any reliable recepies?
Thanks in advance!
Gene.
Monday, March 19, 2012
Help! How to install Sql Svr 2k to Win2k3 Least Privilege Acct?
We are trying to install SQLSever2000 on a Windows 2003 Standard Server to an
account other than Administrator.
We used this guide (which works fine for Win2k Svr)
http://support.microsoft.com/default...;en-us;Q283811
We get an Error 5: Access Denied message when starting SQL Server Agent, but
we don't get enough information to determine what has been denied.
It is obvious that there is some other setting that must be applied in
WinSvr 2k3 that we are not doing - but we didn't see it in the guide. We have
attempted to give the "SQLAdmin" account access to all files and directories
that are related to MS SQL Server.
Unfortunately, our fall back is to install SQL Server to run as
Administrator - because that works.
Any ideas/info is greatly appreciated.
email: hal.hayes@.REMOVE_CAPS_AND_INVALIDacritech.com
I think something else must be wrong or you would not be able to start SQL
Server. Check your event logs, SQL errorlogs and SQL Agent logs for
additional information.
Use SQL Enterprise Manager whenever possible to change the start-up account
for SQL Server and SQL Agent services. SEM will set file and registry
permissions whereas Service Control Manager won't.
Most importantly, ensure that non-admin start-up accounts have following
user privileges:
. Act as Part of the Operating System = SeTcbPrivilege
. Bypass Traverse Checking = SeChangeNotify
. Lock Pages In Memory = SeLockMemory
. Log on as a Batch Job = SeBatchLogonRight
. Log on as a Service = SeServiceLogonRight
. Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
If this is a cluster follow the instructions in
http://support.microsoft.com/kb/239885.
Adrian
"Hal" <Hal@.discussions.microsoft.com> wrote in message
news:D2E25E17-DE30-4AD9-AD55-96BBB5D78ABE@.microsoft.com...
> We are trying to install SQLSever2000 on a Windows 2003 Standard Server to
> an
> account other than Administrator.
> We used this guide (which works fine for Win2k Svr)
> http://support.microsoft.com/default...;en-us;Q283811
> We get an Error 5: Access Denied message when starting SQL Server Agent,
> but
> we don't get enough information to determine what has been denied.
> It is obvious that there is some other setting that must be applied in
> WinSvr 2k3 that we are not doing - but we didn't see it in the guide. We
> have
> attempted to give the "SQLAdmin" account access to all files and
> directories
> that are related to MS SQL Server.
> Unfortunately, our fall back is to install SQL Server to run as
> Administrator - because that works.
> Any ideas/info is greatly appreciated.
> email: hal.hayes@.REMOVE_CAPS_AND_INVALIDacritech.com
account other than Administrator.
We used this guide (which works fine for Win2k Svr)
http://support.microsoft.com/default...;en-us;Q283811
We get an Error 5: Access Denied message when starting SQL Server Agent, but
we don't get enough information to determine what has been denied.
It is obvious that there is some other setting that must be applied in
WinSvr 2k3 that we are not doing - but we didn't see it in the guide. We have
attempted to give the "SQLAdmin" account access to all files and directories
that are related to MS SQL Server.
Unfortunately, our fall back is to install SQL Server to run as
Administrator - because that works.
Any ideas/info is greatly appreciated.
email: hal.hayes@.REMOVE_CAPS_AND_INVALIDacritech.com
I think something else must be wrong or you would not be able to start SQL
Server. Check your event logs, SQL errorlogs and SQL Agent logs for
additional information.
Use SQL Enterprise Manager whenever possible to change the start-up account
for SQL Server and SQL Agent services. SEM will set file and registry
permissions whereas Service Control Manager won't.
Most importantly, ensure that non-admin start-up accounts have following
user privileges:
. Act as Part of the Operating System = SeTcbPrivilege
. Bypass Traverse Checking = SeChangeNotify
. Lock Pages In Memory = SeLockMemory
. Log on as a Batch Job = SeBatchLogonRight
. Log on as a Service = SeServiceLogonRight
. Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
If this is a cluster follow the instructions in
http://support.microsoft.com/kb/239885.
Adrian
"Hal" <Hal@.discussions.microsoft.com> wrote in message
news:D2E25E17-DE30-4AD9-AD55-96BBB5D78ABE@.microsoft.com...
> We are trying to install SQLSever2000 on a Windows 2003 Standard Server to
> an
> account other than Administrator.
> We used this guide (which works fine for Win2k Svr)
> http://support.microsoft.com/default...;en-us;Q283811
> We get an Error 5: Access Denied message when starting SQL Server Agent,
> but
> we don't get enough information to determine what has been denied.
> It is obvious that there is some other setting that must be applied in
> WinSvr 2k3 that we are not doing - but we didn't see it in the guide. We
> have
> attempted to give the "SQLAdmin" account access to all files and
> directories
> that are related to MS SQL Server.
> Unfortunately, our fall back is to install SQL Server to run as
> Administrator - because that works.
> Any ideas/info is greatly appreciated.
> email: hal.hayes@.REMOVE_CAPS_AND_INVALIDacritech.com
Help! How to install Sql Svr 2k to Win2k3 Least Privilege Acct?
We are trying to install SQLSever2000 on a Windows 2003 Standard Server to an
account other than Administrator.
We used this guide (which works fine for Win2k Svr)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q283811
We get an Error 5: Access Denied message when starting SQL Server Agent, but
we don't get enough information to determine what has been denied.
It is obvious that there is some other setting that must be applied in
WinSvr 2k3 that we are not doing - but we didn't see it in the guide. We have
attempted to give the "SQLAdmin" account access to all files and directories
that are related to MS SQL Server.
Unfortunately, our fall back is to install SQL Server to run as
Administrator - because that works.
Any ideas/info is greatly appreciated.
email: hal.hayes@.REMOVE_CAPS_AND_INVALIDacritech.comI think something else must be wrong or you would not be able to start SQL
Server. Check your event logs, SQL errorlogs and SQL Agent logs for
additional information.
Use SQL Enterprise Manager whenever possible to change the start-up account
for SQL Server and SQL Agent services. SEM will set file and registry
permissions whereas Service Control Manager won't.
Most importantly, ensure that non-admin start-up accounts have following
user privileges:
. Act as Part of the Operating System = SeTcbPrivilege
. Bypass Traverse Checking = SeChangeNotify
. Lock Pages In Memory = SeLockMemory
. Log on as a Batch Job = SeBatchLogonRight
. Log on as a Service = SeServiceLogonRight
. Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
If this is a cluster follow the instructions in
http://support.microsoft.com/kb/239885.
Adrian
"Hal" <Hal@.discussions.microsoft.com> wrote in message
news:D2E25E17-DE30-4AD9-AD55-96BBB5D78ABE@.microsoft.com...
> We are trying to install SQLSever2000 on a Windows 2003 Standard Server to
> an
> account other than Administrator.
> We used this guide (which works fine for Win2k Svr)
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q283811
> We get an Error 5: Access Denied message when starting SQL Server Agent,
> but
> we don't get enough information to determine what has been denied.
> It is obvious that there is some other setting that must be applied in
> WinSvr 2k3 that we are not doing - but we didn't see it in the guide. We
> have
> attempted to give the "SQLAdmin" account access to all files and
> directories
> that are related to MS SQL Server.
> Unfortunately, our fall back is to install SQL Server to run as
> Administrator - because that works.
> Any ideas/info is greatly appreciated.
> email: hal.hayes@.REMOVE_CAPS_AND_INVALIDacritech.com
account other than Administrator.
We used this guide (which works fine for Win2k Svr)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q283811
We get an Error 5: Access Denied message when starting SQL Server Agent, but
we don't get enough information to determine what has been denied.
It is obvious that there is some other setting that must be applied in
WinSvr 2k3 that we are not doing - but we didn't see it in the guide. We have
attempted to give the "SQLAdmin" account access to all files and directories
that are related to MS SQL Server.
Unfortunately, our fall back is to install SQL Server to run as
Administrator - because that works.
Any ideas/info is greatly appreciated.
email: hal.hayes@.REMOVE_CAPS_AND_INVALIDacritech.comI think something else must be wrong or you would not be able to start SQL
Server. Check your event logs, SQL errorlogs and SQL Agent logs for
additional information.
Use SQL Enterprise Manager whenever possible to change the start-up account
for SQL Server and SQL Agent services. SEM will set file and registry
permissions whereas Service Control Manager won't.
Most importantly, ensure that non-admin start-up accounts have following
user privileges:
. Act as Part of the Operating System = SeTcbPrivilege
. Bypass Traverse Checking = SeChangeNotify
. Lock Pages In Memory = SeLockMemory
. Log on as a Batch Job = SeBatchLogonRight
. Log on as a Service = SeServiceLogonRight
. Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
If this is a cluster follow the instructions in
http://support.microsoft.com/kb/239885.
Adrian
"Hal" <Hal@.discussions.microsoft.com> wrote in message
news:D2E25E17-DE30-4AD9-AD55-96BBB5D78ABE@.microsoft.com...
> We are trying to install SQLSever2000 on a Windows 2003 Standard Server to
> an
> account other than Administrator.
> We used this guide (which works fine for Win2k Svr)
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q283811
> We get an Error 5: Access Denied message when starting SQL Server Agent,
> but
> we don't get enough information to determine what has been denied.
> It is obvious that there is some other setting that must be applied in
> WinSvr 2k3 that we are not doing - but we didn't see it in the guide. We
> have
> attempted to give the "SQLAdmin" account access to all files and
> directories
> that are related to MS SQL Server.
> Unfortunately, our fall back is to install SQL Server to run as
> Administrator - because that works.
> Any ideas/info is greatly appreciated.
> email: hal.hayes@.REMOVE_CAPS_AND_INVALIDacritech.com
Help! How to install Sql Svr 2k to Win2k3 Least Privilege Acct?
We are trying to install SQLSever2000 on a Windows 2003 Standard Server to a
n
account other than Administrator.
We used this guide (which works fine for Win2k Svr)
http://support.microsoft.com/defaul...b;en-us;Q283811
We get an Error 5: Access Denied message when starting SQL Server Agent, but
we don't get enough information to determine what has been denied.
It is obvious that there is some other setting that must be applied in
WinSvr 2k3 that we are not doing - but we didn't see it in the guide. We hav
e
attempted to give the "SQLAdmin" account access to all files and directories
that are related to MS SQL Server.
Unfortunately, our fall back is to install SQL Server to run as
Administrator - because that works.
Any ideas/info is greatly appreciated.
email: hal.hayes@.REMOVE_CAPS_AND_INVALIDacritech.comI think something else must be wrong or you would not be able to start SQL
Server. Check your event logs, SQL errorlogs and SQL Agent logs for
additional information.
Use SQL Enterprise Manager whenever possible to change the start-up account
for SQL Server and SQL Agent services. SEM will set file and registry
permissions whereas Service Control Manager won't.
Most importantly, ensure that non-admin start-up accounts have following
user privileges:
. Act as Part of the Operating System = SeTcbPrivilege
. Bypass Traverse Checking = SeChangeNotify
. Lock Pages In Memory = SeLockMemory
. Log on as a Batch Job = SeBatchLogonRight
. Log on as a Service = SeServiceLogonRight
. Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
If this is a cluster follow the instructions in
http://support.microsoft.com/kb/239885.
Adrian
"Hal" <Hal@.discussions.microsoft.com> wrote in message
news:D2E25E17-DE30-4AD9-AD55-96BBB5D78ABE@.microsoft.com...
> We are trying to install SQLSever2000 on a Windows 2003 Standard Server to
> an
> account other than Administrator.
> We used this guide (which works fine for Win2k Svr)
> http://support.microsoft.com/defaul...b;en-us;Q283811
> We get an Error 5: Access Denied message when starting SQL Server Agent,
> but
> we don't get enough information to determine what has been denied.
> It is obvious that there is some other setting that must be applied in
> WinSvr 2k3 that we are not doing - but we didn't see it in the guide. We
> have
> attempted to give the "SQLAdmin" account access to all files and
> directories
> that are related to MS SQL Server.
> Unfortunately, our fall back is to install SQL Server to run as
> Administrator - because that works.
> Any ideas/info is greatly appreciated.
> email: hal.hayes@.REMOVE_CAPS_AND_INVALIDacritech.com
n
account other than Administrator.
We used this guide (which works fine for Win2k Svr)
http://support.microsoft.com/defaul...b;en-us;Q283811
We get an Error 5: Access Denied message when starting SQL Server Agent, but
we don't get enough information to determine what has been denied.
It is obvious that there is some other setting that must be applied in
WinSvr 2k3 that we are not doing - but we didn't see it in the guide. We hav
e
attempted to give the "SQLAdmin" account access to all files and directories
that are related to MS SQL Server.
Unfortunately, our fall back is to install SQL Server to run as
Administrator - because that works.
Any ideas/info is greatly appreciated.
email: hal.hayes@.REMOVE_CAPS_AND_INVALIDacritech.comI think something else must be wrong or you would not be able to start SQL
Server. Check your event logs, SQL errorlogs and SQL Agent logs for
additional information.
Use SQL Enterprise Manager whenever possible to change the start-up account
for SQL Server and SQL Agent services. SEM will set file and registry
permissions whereas Service Control Manager won't.
Most importantly, ensure that non-admin start-up accounts have following
user privileges:
. Act as Part of the Operating System = SeTcbPrivilege
. Bypass Traverse Checking = SeChangeNotify
. Lock Pages In Memory = SeLockMemory
. Log on as a Batch Job = SeBatchLogonRight
. Log on as a Service = SeServiceLogonRight
. Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
If this is a cluster follow the instructions in
http://support.microsoft.com/kb/239885.
Adrian
"Hal" <Hal@.discussions.microsoft.com> wrote in message
news:D2E25E17-DE30-4AD9-AD55-96BBB5D78ABE@.microsoft.com...
> We are trying to install SQLSever2000 on a Windows 2003 Standard Server to
> an
> account other than Administrator.
> We used this guide (which works fine for Win2k Svr)
> http://support.microsoft.com/defaul...b;en-us;Q283811
> We get an Error 5: Access Denied message when starting SQL Server Agent,
> but
> we don't get enough information to determine what has been denied.
> It is obvious that there is some other setting that must be applied in
> WinSvr 2k3 that we are not doing - but we didn't see it in the guide. We
> have
> attempted to give the "SQLAdmin" account access to all files and
> directories
> that are related to MS SQL Server.
> Unfortunately, our fall back is to install SQL Server to run as
> Administrator - because that works.
> Any ideas/info is greatly appreciated.
> email: hal.hayes@.REMOVE_CAPS_AND_INVALIDacritech.com
Help! How do I create an SQL database on my machine? + Access -> SQL ?
According to my technical support for web hosting, for database format they only use "MS SQL" operating on a windows system, usualy clients create they're sites on their local machines using "MS SQL".
I'm just wondering....
Is 'MS SQL' free? where can I get it?
I also have the option of creating the site round an access databse but I'm worried about the security issues,
do you think it would be wise to use access?
Is it easy to convert a site written in ASP.NET&ACCESS into a site using ASP.NET&"ms sql"?
because then I could code a site in the former on my machine and then change the code to link to an sql server.when my suport persons talking about "MS SQL" does he actually mean "msde"?
I've been having some trouble with that too:
http://www.gotdotnet.com/Community/MessageBoard/Thread.aspx?id=181961&Page=1#183129|||'MS SQL Server' is not free. The good news are that MS has released a scaled down version of MS Sql Server which is. It's called MSDE (MS Desktop Edition) and is ideal for developing on your local machine, as well as OK for low traffic production servers. Download ithere.|||thanks for the reply andre,
that last post went up before I read your replied,
MSDE wont install because it says I need a strong SA password but I have no idea how to set one up for my account.|||more info, I think i downloaded the wrong package file before "sql2kdesksp3" I'm now downloading sql2ksp3 is that the right onw? is the other stuff I need to download to?|||downloading msde2000a now aswell|||its still having the same SAPWD option,
Is there a detailed explanation anywhere on using the SAPWD switch or have I goy my wires crossed.
help! H/W spec for SQL Server 2000
Hi,
I have a SQL server 2000 database running in Windows Server 2000. The database only consists of a handful of tables and is taking multiple inserts from @.40 client PCs.
The server exists on two servers with half the clients talking to each. The databases use transactional replication to stay synchronised.
Each PC generates about 100 SQL transactions per busy hour, each being an insert.
The customer is expanding the number of client PCs from 40, through 300 to, ultimately, about 3000. They are asking me what hardware spec is required and want to be told it in a for each additional 50 client applications you need XYZ type of format to allow for gradual growth.
I have to say I am unsure how to go about scaling and configuring the servers!
So, is there such a thing as an automatic configurator which automatically produces a required spec for a given number of transactions and clients? Are there other criteria they/I need to take into account such as number of logins etc? For archiving I am guessing that a CD/RW drive is the way to go?
Also, in terms of design between the two servers they have. With clustering, mirroring, replication etc I am unsure as to which is most appropriate.
The thing I do know is that they are willing to spend serious $$$ for the right design and need 99.9% up time.
They also pull significant amount of reports which I think logically equates to a third server to keep this traffic away from the live database. So, is replication the best way to go? Say replication every 15 minutes to a reports server?
I am also of the opinion that they need to move from Windows 2000 Server to Advanced Server for added scalability but will pursue that elsewhere.
Any input MUCH appreciated.
Out of my depth! :confused:
PaulThe thing I do know is that they are willing to spend serious $$$ for the right design and need 99.9% up time.
Then they better be willing to spend some money. They'll need it.
I would try to get them to move to Advanced Server or wait for 2003 SP1 to come out. Enterprise Edition will be needed for many of the features you are talking about. It's impossible to answer your question without knowing the database. You need to figure out how many rows in the tables will be taken at different levels of users, what the average fill ratio will be on those tables, then how much size you'll need along the way. In addition, you need to figure out how many transactions, and how much those will cost you as the database grows do to increased size of the tables.
I would purchase the Microsoft Press book: Permformance Tuning Manual technical reference if I was you and have a look at the worksheets and formulas in the book.
I have a SQL server 2000 database running in Windows Server 2000. The database only consists of a handful of tables and is taking multiple inserts from @.40 client PCs.
The server exists on two servers with half the clients talking to each. The databases use transactional replication to stay synchronised.
Each PC generates about 100 SQL transactions per busy hour, each being an insert.
The customer is expanding the number of client PCs from 40, through 300 to, ultimately, about 3000. They are asking me what hardware spec is required and want to be told it in a for each additional 50 client applications you need XYZ type of format to allow for gradual growth.
I have to say I am unsure how to go about scaling and configuring the servers!
So, is there such a thing as an automatic configurator which automatically produces a required spec for a given number of transactions and clients? Are there other criteria they/I need to take into account such as number of logins etc? For archiving I am guessing that a CD/RW drive is the way to go?
Also, in terms of design between the two servers they have. With clustering, mirroring, replication etc I am unsure as to which is most appropriate.
The thing I do know is that they are willing to spend serious $$$ for the right design and need 99.9% up time.
They also pull significant amount of reports which I think logically equates to a third server to keep this traffic away from the live database. So, is replication the best way to go? Say replication every 15 minutes to a reports server?
I am also of the opinion that they need to move from Windows 2000 Server to Advanced Server for added scalability but will pursue that elsewhere.
Any input MUCH appreciated.
Out of my depth! :confused:
PaulThe thing I do know is that they are willing to spend serious $$$ for the right design and need 99.9% up time.
Then they better be willing to spend some money. They'll need it.
I would try to get them to move to Advanced Server or wait for 2003 SP1 to come out. Enterprise Edition will be needed for many of the features you are talking about. It's impossible to answer your question without knowing the database. You need to figure out how many rows in the tables will be taken at different levels of users, what the average fill ratio will be on those tables, then how much size you'll need along the way. In addition, you need to figure out how many transactions, and how much those will cost you as the database grows do to increased size of the tables.
I would purchase the Microsoft Press book: Permformance Tuning Manual technical reference if I was you and have a look at the worksheets and formulas in the book.
Help! getting errors when trying to connect to SQL Server Management Studio
Hi All,
I have Windows 2003 Server with MSSQL 2005 Standard.
I am able to connect via Windows Authentication, but when I try to change it to SQL Server Authentication with user 'sa' I'm then being prompted with the error msg:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (.Net SqlClient Data Provider)
Here is the entire list of msgs that are showing up:
===================================
Cannot connect to SOLELL-QGL5PG9D.
===================================
A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
Server Name: SOLELL-QGL5PG9D
Error Number: 233
Severity: 20
State: 0
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
Any pointers?
-Alon.
Hi,
didi you enable mixed authentication or did you just enable the Windows Authentication ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||Hi Jens,
I installed the MSSQL a week and a half ago, and I believe it was set to Mixed. I simply don't remember.
Is there a way to know?
Can it be changed to Mixed mode in the event that I missed that? or do I need to uninstall and re-install from scratch?
thanks,
-Alon.
|||Hi Jens,
Since I didn't have any database created yet, I've uninstalled MSSQL and Re-installed it.
This time, I made sure it was set to the Mixed Mode.
I don't know if there was a way to verify an early install or if there is a way to change from
Windows Auth Only to Mixed mode, but Uninstalling and Re-installing took only 30 minutes and I had no databases that I needed to check previously,. so that was my solution.
Thanks for the interest.
-Alon.
|||
Hi,
just for the completion of your answer, the authentication mode can be investigated by using the SQL Server Management Studio and right clicking on the server, choosing the properties and viewing the setting in the Security pane. If you don′t have any visual tool for editing this you can use the registry key
Default instance:
"HKEY_LOCAL_MACHINE\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode"
to 2 for mixed-mode or 1 for integrated.
Have in mind that changing the setting will need a restart of the server to apply.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||Hey,I had this same issue. My MSSQL 2005 server was setup on a port other than the default 1433. Once I added the port number to the connect string, I was able to connect. ie.: SERVERNAME, 9999
Good Luck.
Monday, March 12, 2012
Help! getting errors when trying to connect to SQL Server Management Studio
Hi All,
I have Windows 2003 Server with MSSQL 2005 Standard.
I am able to connect via Windows Authentication, but when I try to change it to SQL Server Authentication with user 'sa' I'm then being prompted with the error msg:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (.Net SqlClient Data Provider)
Here is the entire list of msgs that are showing up:
===================================
Cannot connect to SOLELL-QGL5PG9D.
===================================
A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
Server Name: SOLELL-QGL5PG9D
Error Number: 233
Severity: 20
State: 0
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
Any pointers?
-Alon.
Hi,
didi you enable mixed authentication or did you just enable the Windows Authentication ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||Hi Jens,
I installed the MSSQL a week and a half ago, and I believe it was set to Mixed. I simply don't remember.
Is there a way to know?
Can it be changed to Mixed mode in the event that I missed that? or do I need to uninstall and re-install from scratch?
thanks,
-Alon.
|||Hi Jens,
Since I didn't have any database created yet, I've uninstalled MSSQL and Re-installed it.
This time, I made sure it was set to the Mixed Mode.
I don't know if there was a way to verify an early install or if there is a way to change from
Windows Auth Only to Mixed mode, but Uninstalling and Re-installing took only 30 minutes and I had no databases that I needed to check previously,. so that was my solution.
Thanks for the interest.
-Alon.
|||
Hi,
just for the completion of your answer, the authentication mode can be investigated by using the SQL Server Management Studio and right clicking on the server, choosing the properties and viewing the setting in the Security pane. If you don′t have any visual tool for editing this you can use the registry key
Default instance:
"HKEY_LOCAL_MACHINE\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode"
to 2 for mixed-mode or 1 for integrated.
Have in mind that changing the setting will need a restart of the server to apply.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||Hey,I had this same issue. My MSSQL 2005 server was setup on a port other than the default 1433. Once I added the port number to the connect string, I was able to connect. ie.: SERVERNAME, 9999
Good Luck.
HELP! EM wont connect after apply sp3a,reporting services and VS.net 2003
Install SQL 2000 on a completelyu up to date windows 2003 advanced server,
then applied sp3a, then a installed reporting service developer addition,
then installed VS .net 2003 the reinstalled reporting services to get the
Report Developer.
Now I can't connect to the Server using EM.
Get SQL_alloc_handle on SQL_handle_env failed.
Tried all types of registrations.
Any suggestions short of starting from scratch?Make an ODBC trace of the connection attempt & open a case with the Webdata
team. They handle the MDAC problems with SQL.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Will do that if re-install of tools SQL fails. How do I open a case with the
WEBdata Team.
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:XWmAGmZ9DHA.704@.cpmsftngxa07.phx.gbl...
> Make an ODBC trace of the connection attempt & open a case with the
Webdata
> team. They handle the MDAC problems with SQL.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
then applied sp3a, then a installed reporting service developer addition,
then installed VS .net 2003 the reinstalled reporting services to get the
Report Developer.
Now I can't connect to the Server using EM.
Get SQL_alloc_handle on SQL_handle_env failed.
Tried all types of registrations.
Any suggestions short of starting from scratch?Make an ODBC trace of the connection attempt & open a case with the Webdata
team. They handle the MDAC problems with SQL.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Will do that if re-install of tools SQL fails. How do I open a case with the
WEBdata Team.
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:XWmAGmZ9DHA.704@.cpmsftngxa07.phx.gbl...
> Make an ODBC trace of the connection attempt & open a case with the
Webdata
> team. They handle the MDAC problems with SQL.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
Help! Db-library network communications layer not loaded.
Hi,
We are using a windows application that uses MSDE 2000 on an XP Pro Machine
as a server.
Everthing was fine until last Friday. Suddenly, the XP server computer
started to give this error "Db-library network communications layer not
loaded." when we started to run application on it.
From other client computers we can succesfully connect and run the
application, but somehow the main machine does not work. I thought the
automatic update was on and it updated some MDAC drivers or may be Net
framework. I tried to install MDAC 2.7, but still no change. (I tired some
web searches but still nothing)
I really appreciate if you can give any suggestions/solutions.
Thanks.
Onur Baser
DB-Library is not part of MDAC or MSDE, so probably you had it on your other
machine because you installed the client tools or something.
Anyhow I also hope you realize that DB-Library is a dead API since the
introduction of SQL Server 7.0 in 1998 and it does not allow you to connect
to named instances for example (without using an alias or protocol prefix),
Unicode, strings longer then 255 or any of the other new data types
introduced in SQL Server 7.0 or 2000.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"Onur Baser" <onur@.baserler.com> wrote in message
news:u18HnHVlEHA.596@.TK2MSFTNGP11.phx.gbl...
> Hi,
> We are using a windows application that uses MSDE 2000 on an XP Pro
> Machine as a server.
> Everthing was fine until last Friday. Suddenly, the XP server computer
> started to give this error "Db-library network communications layer not
> loaded." when we started to run application on it.
> From other client computers we can succesfully connect and run the
> application, but somehow the main machine does not work. I thought the
> automatic update was on and it updated some MDAC drivers or may be Net
> framework. I tried to install MDAC 2.7, but still no change. (I tired some
> web searches but still nothing)
> I really appreciate if you can give any suggestions/solutions.
> Thanks.
> Onur Baser
>
|||Thank you,
I will see what I can do, but is really wierd that it just happened.
Best Regards,
OnuR
"Gert E.R. Drapers" <GertD@.SQLDev.Net> wrote in message
news:uLSRUJWlEHA.3432@.TK2MSFTNGP14.phx.gbl...
> DB-Library is not part of MDAC or MSDE, so probably you had it on your
> other machine because you installed the client tools or something.
> Anyhow I also hope you realize that DB-Library is a dead API since the
> introduction of SQL Server 7.0 in 1998 and it does not allow you to
> connect to named instances for example (without using an alias or protocol
> prefix), Unicode, strings longer then 255 or any of the other new data
> types introduced in SQL Server 7.0 or 2000.
> GertD@.SQLDev.Net
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use.
> Copyright SQLDev.Net 1991-2004 All rights reserved.
> "Onur Baser" <onur@.baserler.com> wrote in message
> news:u18HnHVlEHA.596@.TK2MSFTNGP11.phx.gbl...
>
We are using a windows application that uses MSDE 2000 on an XP Pro Machine
as a server.
Everthing was fine until last Friday. Suddenly, the XP server computer
started to give this error "Db-library network communications layer not
loaded." when we started to run application on it.
From other client computers we can succesfully connect and run the
application, but somehow the main machine does not work. I thought the
automatic update was on and it updated some MDAC drivers or may be Net
framework. I tried to install MDAC 2.7, but still no change. (I tired some
web searches but still nothing)
I really appreciate if you can give any suggestions/solutions.
Thanks.
Onur Baser
DB-Library is not part of MDAC or MSDE, so probably you had it on your other
machine because you installed the client tools or something.
Anyhow I also hope you realize that DB-Library is a dead API since the
introduction of SQL Server 7.0 in 1998 and it does not allow you to connect
to named instances for example (without using an alias or protocol prefix),
Unicode, strings longer then 255 or any of the other new data types
introduced in SQL Server 7.0 or 2000.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"Onur Baser" <onur@.baserler.com> wrote in message
news:u18HnHVlEHA.596@.TK2MSFTNGP11.phx.gbl...
> Hi,
> We are using a windows application that uses MSDE 2000 on an XP Pro
> Machine as a server.
> Everthing was fine until last Friday. Suddenly, the XP server computer
> started to give this error "Db-library network communications layer not
> loaded." when we started to run application on it.
> From other client computers we can succesfully connect and run the
> application, but somehow the main machine does not work. I thought the
> automatic update was on and it updated some MDAC drivers or may be Net
> framework. I tried to install MDAC 2.7, but still no change. (I tired some
> web searches but still nothing)
> I really appreciate if you can give any suggestions/solutions.
> Thanks.
> Onur Baser
>
|||Thank you,
I will see what I can do, but is really wierd that it just happened.
Best Regards,
OnuR
"Gert E.R. Drapers" <GertD@.SQLDev.Net> wrote in message
news:uLSRUJWlEHA.3432@.TK2MSFTNGP14.phx.gbl...
> DB-Library is not part of MDAC or MSDE, so probably you had it on your
> other machine because you installed the client tools or something.
> Anyhow I also hope you realize that DB-Library is a dead API since the
> introduction of SQL Server 7.0 in 1998 and it does not allow you to
> connect to named instances for example (without using an alias or protocol
> prefix), Unicode, strings longer then 255 or any of the other new data
> types introduced in SQL Server 7.0 or 2000.
> GertD@.SQLDev.Net
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use.
> Copyright SQLDev.Net 1991-2004 All rights reserved.
> "Onur Baser" <onur@.baserler.com> wrote in message
> news:u18HnHVlEHA.596@.TK2MSFTNGP11.phx.gbl...
>
Help! Databases are in "Loading" state after Restore from tape!
I run MS SQL Server 2000 (8.00.194) on a Windows 2000 Server.
After having problems with extremely large logfiles, I was told to stop the SQL Service, and delete the logs, and when I restarted the SQL Service the Server would recreate the log files. That did not happend, and the databases had "Suspect" state. After I've tried a few things found on this forum among others, I ended up restoring the db's from my last tape backup.
This was successfully (with Veritas Backup Exec), but now the databases have "Loading" state. I've searched the forums, but haven't found a solution, please help!
Thank you in advance!In Query Analyzer, issue the following command:
restore database yourdatabase with recovery
Substitute your database's name with "yourdatabase".
That should clear up the loading state. I trust you have resolved to never again take advice from the guy that told you to delete the log files?|||Originally posted by MCrowley
In Query Analyzer, issue the following command:
restore database yourdatabase with recovery
Substitute your database's name with "yourdatabase".
That should clear up the loading state. I trust you have resolved to never again take advice from the guy that told you to delete the log files?
Thanks for your answer. I tried it, and got this msg back:
Server: Msg 4331, Level 16, State 1, Line 1
The database cannot be recovered because the files have been restored to inconsistent points in time.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
:(
Yes, I will not delete them again, but I seriously need to get these databases up and running.|||As you can see, I have full backup of the databases on tape.
So If anyone could give me info on how to do a restore correctly, that will also solve my problem.
Thanks, again.|||here is a link to an article at Veritas that may help you out:
http://seer.support.veritas.com/docs/258895.htm
do you only have the backups done through the Veritas agent? or do you also have files from a SQL Server initiated backup (like from a maintenance plan)? If you have backup files you can restore those to disk and then restore through SQL Server.
It might not help now, but you might want to consider scheduling a backup to disk (either standalone or through a maintenance plan) in addition to your agent backups. I personally don't trust backups that go straight to tape, they're good to have as additional insurance, but I wouldn't rely on them alone.
If you are running 8.00.194 (RTM) you might also want to look into getting that server up to SP3a or at least to a point where you're covered against the various vulnerabilities like slammer, etc.. that is of course if your application will run correctly|||Originally posted by drew
here is a link to an article at Veritas that may help you out:
http://seer.support.veritas.com/docs/258895.htm
do you only have the backups done through the Veritas agent? or do you also have files from a SQL Server initiated backup (like from a maintenance plan)? If you have backup files you can restore those to disk and then restore through SQL Server.
It might not help now, but you might want to consider scheduling a backup to disk (either standalone or through a maintenance plan) in addition to your agent backups. I personally don't trust backups that go straight to tape, they're good to have as additional insurance, but I wouldn't rely on them alone.
If you are running 8.00.194 (RTM) you might also want to look into getting that server up to SP3a or at least to a point where you're covered against the various vulnerabilities like slammer, etc.. that is of course if your application will run correctly
Thanks for your answer, I'll look into what the article describes. I've understand that this backup isn't good enought, sp it will be changed as soon as I have my data up and running again. About the upgrade, it has not been done due to compatibility problems. Hopefully it will soon be patched with latest sp.|||You can try this code to force your database out of the loading state, but because it modifies system tables use it at your own risk:
sp_configure 'allow updates', 1
RECONFIGURE WITH OVERRIDE
go
update master..sysdatabases
set status = status - 32
where name = 'YourDatabaseName' and status & 32 > 0
go
sp_configure 'allow updates', 0
RECONFIGURE WITH OVERRIDE
go
If this does not work, try dropping and recreating your databases prior to running MCrowley's RESTORE DATABASE suggestion.
blindman|||Seems like the veritas article was what I needed to at least get the first backup database back :D
Thanks a lot everyone...one db to go, hopefully that's goes okay as well.
This forum is awesome. Helping a n00b who started with sql a few hours ago, thanks again!
- Everything is back and up and running from the backup.
Good night ppl!
After having problems with extremely large logfiles, I was told to stop the SQL Service, and delete the logs, and when I restarted the SQL Service the Server would recreate the log files. That did not happend, and the databases had "Suspect" state. After I've tried a few things found on this forum among others, I ended up restoring the db's from my last tape backup.
This was successfully (with Veritas Backup Exec), but now the databases have "Loading" state. I've searched the forums, but haven't found a solution, please help!
Thank you in advance!In Query Analyzer, issue the following command:
restore database yourdatabase with recovery
Substitute your database's name with "yourdatabase".
That should clear up the loading state. I trust you have resolved to never again take advice from the guy that told you to delete the log files?|||Originally posted by MCrowley
In Query Analyzer, issue the following command:
restore database yourdatabase with recovery
Substitute your database's name with "yourdatabase".
That should clear up the loading state. I trust you have resolved to never again take advice from the guy that told you to delete the log files?
Thanks for your answer. I tried it, and got this msg back:
Server: Msg 4331, Level 16, State 1, Line 1
The database cannot be recovered because the files have been restored to inconsistent points in time.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
:(
Yes, I will not delete them again, but I seriously need to get these databases up and running.|||As you can see, I have full backup of the databases on tape.
So If anyone could give me info on how to do a restore correctly, that will also solve my problem.
Thanks, again.|||here is a link to an article at Veritas that may help you out:
http://seer.support.veritas.com/docs/258895.htm
do you only have the backups done through the Veritas agent? or do you also have files from a SQL Server initiated backup (like from a maintenance plan)? If you have backup files you can restore those to disk and then restore through SQL Server.
It might not help now, but you might want to consider scheduling a backup to disk (either standalone or through a maintenance plan) in addition to your agent backups. I personally don't trust backups that go straight to tape, they're good to have as additional insurance, but I wouldn't rely on them alone.
If you are running 8.00.194 (RTM) you might also want to look into getting that server up to SP3a or at least to a point where you're covered against the various vulnerabilities like slammer, etc.. that is of course if your application will run correctly|||Originally posted by drew
here is a link to an article at Veritas that may help you out:
http://seer.support.veritas.com/docs/258895.htm
do you only have the backups done through the Veritas agent? or do you also have files from a SQL Server initiated backup (like from a maintenance plan)? If you have backup files you can restore those to disk and then restore through SQL Server.
It might not help now, but you might want to consider scheduling a backup to disk (either standalone or through a maintenance plan) in addition to your agent backups. I personally don't trust backups that go straight to tape, they're good to have as additional insurance, but I wouldn't rely on them alone.
If you are running 8.00.194 (RTM) you might also want to look into getting that server up to SP3a or at least to a point where you're covered against the various vulnerabilities like slammer, etc.. that is of course if your application will run correctly
Thanks for your answer, I'll look into what the article describes. I've understand that this backup isn't good enought, sp it will be changed as soon as I have my data up and running again. About the upgrade, it has not been done due to compatibility problems. Hopefully it will soon be patched with latest sp.|||You can try this code to force your database out of the loading state, but because it modifies system tables use it at your own risk:
sp_configure 'allow updates', 1
RECONFIGURE WITH OVERRIDE
go
update master..sysdatabases
set status = status - 32
where name = 'YourDatabaseName' and status & 32 > 0
go
sp_configure 'allow updates', 0
RECONFIGURE WITH OVERRIDE
go
If this does not work, try dropping and recreating your databases prior to running MCrowley's RESTORE DATABASE suggestion.
blindman|||Seems like the veritas article was what I needed to at least get the first backup database back :D
Thanks a lot everyone...one db to go, hopefully that's goes okay as well.
This forum is awesome. Helping a n00b who started with sql a few hours ago, thanks again!
- Everything is back and up and running from the backup.
Good night ppl!
Friday, March 9, 2012
Help! [Microsoft][ODBC SQL Server Driver]Timeout expired
Hi all...
Environment
OS : Windows 2000 Advanced Server(SP4)
SQL Server : Microsoft SQL Server 2000(SP3)
DB Accessing : MSDTC, ODBC, COM+(VC++) calling Stored Procedure through
firewall
i have four databases, each size are 8G, 400M, 18G, 500M
there is a firewall between COM+ Server and SQL Server
so, i have configured port configuration for MSDTC as recommended by
Microsoft Support site
http://support.microsoft.com/kb/250367
almost for the past 1.5 years. my com+ application has worked 99.9999% fine
but from about a month ago i got this error at every particular NIGHT
time(ie. 22:00)
on particular database
[Microsoft][ODBC SQL Server Driver]Timeout expired
Com Error : DESC-->[Microsoft][ODBC SQL Server Driver]Timeout expired
MSG-->OR_20001_SN_ReceiptOrder
IDispatch error #3121 Error Count:1 GetLastError Number:0.
once this error occurrs, all other components which are using "transaction"
get the same error over and over and over again till i restart MSDTC service
or
SQL Server Database.
really strange thing is that this error NEVER occurrs at a daytime
i found the fact that sp starts and never completed after tracing by using
query profiler
is this related to network resource or table locking?
has anybody seen this case? or any ideas?
Hi
Sounds like blocking at table level. If network connection issues occur, DTC
notices it and aborts.
Regards
Mike
"Chan" wrote:
> Hi all...
> Environment
> OS : Windows 2000 Advanced Server(SP4)
> SQL Server : Microsoft SQL Server 2000(SP3)
> DB Accessing : MSDTC, ODBC, COM+(VC++) calling Stored Procedure through
> firewall
> i have four databases, each size are 8G, 400M, 18G, 500M
> there is a firewall between COM+ Server and SQL Server
> so, i have configured port configuration for MSDTC as recommended by
> Microsoft Support site
> http://support.microsoft.com/kb/250367
> almost for the past 1.5 years. my com+ application has worked 99.9999% fine
> but from about a month ago i got this error at every particular NIGHT
> time(ie. 22:00)
> on particular database
> [Microsoft][ODBC SQL Server Driver]Timeout expired
> Com Error : DESC-->[Microsoft][ODBC SQL Server Driver]Timeout expired
> MSG-->OR_20001_SN_ReceiptOrder
> IDispatch error #3121 Error Count:1 GetLastError Number:0.
> once this error occurrs, all other components which are using "transaction"
> get the same error over and over and over again till i restart MSDTC service
> or
> SQL Server Database.
> really strange thing is that this error NEVER occurrs at a daytime
> i found the fact that sp starts and never completed after tracing by using
> query profiler
> is this related to network resource or table locking?
> has anybody seen this case? or any ideas?
|||Hi Mike
i am a litlte bit newbie for mssql
just typed "'sp_lock" to see if there is a table level lock in query analyzer
and no table lock information found on the target database which causing
troubles
would you please let me know how you find lock information?
one more thing i did not mention
number of ports opened is 10, not microsofts' recommendation minimum of 15~20
any comments helps me
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> Sounds like blocking at table level. If network connection issues occur, DTC
> notices it and aborts.
> Regards
> Mike
> "Chan" wrote:
Environment
OS : Windows 2000 Advanced Server(SP4)
SQL Server : Microsoft SQL Server 2000(SP3)
DB Accessing : MSDTC, ODBC, COM+(VC++) calling Stored Procedure through
firewall
i have four databases, each size are 8G, 400M, 18G, 500M
there is a firewall between COM+ Server and SQL Server
so, i have configured port configuration for MSDTC as recommended by
Microsoft Support site
http://support.microsoft.com/kb/250367
almost for the past 1.5 years. my com+ application has worked 99.9999% fine
but from about a month ago i got this error at every particular NIGHT
time(ie. 22:00)
on particular database
[Microsoft][ODBC SQL Server Driver]Timeout expired
Com Error : DESC-->[Microsoft][ODBC SQL Server Driver]Timeout expired
MSG-->OR_20001_SN_ReceiptOrder
IDispatch error #3121 Error Count:1 GetLastError Number:0.
once this error occurrs, all other components which are using "transaction"
get the same error over and over and over again till i restart MSDTC service
or
SQL Server Database.
really strange thing is that this error NEVER occurrs at a daytime
i found the fact that sp starts and never completed after tracing by using
query profiler
is this related to network resource or table locking?
has anybody seen this case? or any ideas?
Hi
Sounds like blocking at table level. If network connection issues occur, DTC
notices it and aborts.
Regards
Mike
"Chan" wrote:
> Hi all...
> Environment
> OS : Windows 2000 Advanced Server(SP4)
> SQL Server : Microsoft SQL Server 2000(SP3)
> DB Accessing : MSDTC, ODBC, COM+(VC++) calling Stored Procedure through
> firewall
> i have four databases, each size are 8G, 400M, 18G, 500M
> there is a firewall between COM+ Server and SQL Server
> so, i have configured port configuration for MSDTC as recommended by
> Microsoft Support site
> http://support.microsoft.com/kb/250367
> almost for the past 1.5 years. my com+ application has worked 99.9999% fine
> but from about a month ago i got this error at every particular NIGHT
> time(ie. 22:00)
> on particular database
> [Microsoft][ODBC SQL Server Driver]Timeout expired
> Com Error : DESC-->[Microsoft][ODBC SQL Server Driver]Timeout expired
> MSG-->OR_20001_SN_ReceiptOrder
> IDispatch error #3121 Error Count:1 GetLastError Number:0.
> once this error occurrs, all other components which are using "transaction"
> get the same error over and over and over again till i restart MSDTC service
> or
> SQL Server Database.
> really strange thing is that this error NEVER occurrs at a daytime
> i found the fact that sp starts and never completed after tracing by using
> query profiler
> is this related to network resource or table locking?
> has anybody seen this case? or any ideas?
|||Hi Mike
i am a litlte bit newbie for mssql
just typed "'sp_lock" to see if there is a table level lock in query analyzer
and no table lock information found on the target database which causing
troubles
would you please let me know how you find lock information?
one more thing i did not mention
number of ports opened is 10, not microsofts' recommendation minimum of 15~20
any comments helps me
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> Sounds like blocking at table level. If network connection issues occur, DTC
> notices it and aborts.
> Regards
> Mike
> "Chan" wrote:
Help! [Microsoft][ODBC SQL Server Driver]Timeout expired
Hi all...
Environment
OS : Windows 2000 Advanced Server(SP4)
SQL Server : Microsoft SQL Server 2000(SP3)
DB Accessing : MSDTC, ODBC, COM+(VC++) calling Stored Procedure through
firewall
i have four databases, each size are 8G, 400M, 18G, 500M
there is a firewall between COM+ Server and SQL Server
so, i have configured port configuration for MSDTC as recommended by
Microsoft Support site
http://support.microsoft.com/kb/250367
almost for the past 1.5 years. my com+ application has worked 99.9999% fine
but from about a month ago i got this error at every particular NIGHT
time(ie. 22:00)
on particular database
[Microsoft][ODBC SQL Server Driver]Timeout expired
Com Error : DESC-->[Microsoft][ODBC SQL Server Driver]Timeout expire
d
MSG-->OR_20001_SN_ReceiptOrder
IDispatch error #3121 Error Count:1 GetLastError Number:0.
once this error occurrs, all other components which are using "transaction"
get the same error over and over and over again till i restart MSDTC service
or
SQL Server Database.
really strange thing is that this error NEVER occurrs at a daytime
i found the fact that sp starts and never completed after tracing by using
query profiler
is this related to network resource or table locking?
has anybody seen this case? or any ideas?Chan,
You should probably call MS product support and let them take a look at
this. It's hard to determine what can cause these errors without some heavy
duty troubleshooting. It could be a leak in the provider or some other
MSDTC-related problem.
Adrian
"Chan" <Chan@.discussions.microsoft.com> wrote in message
news:E472A035-D0A2-49E1-AD2A-373FE573AB5E@.microsoft.com...
> Hi all...
> Environment
> OS : Windows 2000 Advanced Server(SP4)
> SQL Server : Microsoft SQL Server 2000(SP3)
> DB Accessing : MSDTC, ODBC, COM+(VC++) calling Stored Procedure through
> firewall
> i have four databases, each size are 8G, 400M, 18G, 500M
> there is a firewall between COM+ Server and SQL Server
> so, i have configured port configuration for MSDTC as recommended by
> Microsoft Support site
> http://support.microsoft.com/kb/250367
> almost for the past 1.5 years. my com+ application has worked 99.9999%
> fine
> but from about a month ago i got this error at every particular NIGHT
> time(ie. 22:00)
> on particular database
> [Microsoft][ODBC SQL Server Driver]Timeout expired
> Com Error : DESC-->[Microsoft][ODBC SQL Server Driver]Timeout expi
red
> MSG-->OR_20001_SN_ReceiptOrder
> IDispatch error #3121 Error Count:1 GetLastError Number:0.
> once this error occurrs, all other components which are using
> "transaction"
> get the same error over and over and over again till i restart MSDTC
> service
> or
> SQL Server Database.
> really strange thing is that this error NEVER occurrs at a daytime
> i found the fact that sp starts and never completed after tracing by using
> query profiler
> is this related to network resource or table locking?
> has anybody seen this case? or any ideas?
Environment
OS : Windows 2000 Advanced Server(SP4)
SQL Server : Microsoft SQL Server 2000(SP3)
DB Accessing : MSDTC, ODBC, COM+(VC++) calling Stored Procedure through
firewall
i have four databases, each size are 8G, 400M, 18G, 500M
there is a firewall between COM+ Server and SQL Server
so, i have configured port configuration for MSDTC as recommended by
Microsoft Support site
http://support.microsoft.com/kb/250367
almost for the past 1.5 years. my com+ application has worked 99.9999% fine
but from about a month ago i got this error at every particular NIGHT
time(ie. 22:00)
on particular database
[Microsoft][ODBC SQL Server Driver]Timeout expired
Com Error : DESC-->[Microsoft][ODBC SQL Server Driver]Timeout expire
d
MSG-->OR_20001_SN_ReceiptOrder
IDispatch error #3121 Error Count:1 GetLastError Number:0.
once this error occurrs, all other components which are using "transaction"
get the same error over and over and over again till i restart MSDTC service
or
SQL Server Database.
really strange thing is that this error NEVER occurrs at a daytime
i found the fact that sp starts and never completed after tracing by using
query profiler
is this related to network resource or table locking?
has anybody seen this case? or any ideas?Chan,
You should probably call MS product support and let them take a look at
this. It's hard to determine what can cause these errors without some heavy
duty troubleshooting. It could be a leak in the provider or some other
MSDTC-related problem.
Adrian
"Chan" <Chan@.discussions.microsoft.com> wrote in message
news:E472A035-D0A2-49E1-AD2A-373FE573AB5E@.microsoft.com...
> Hi all...
> Environment
> OS : Windows 2000 Advanced Server(SP4)
> SQL Server : Microsoft SQL Server 2000(SP3)
> DB Accessing : MSDTC, ODBC, COM+(VC++) calling Stored Procedure through
> firewall
> i have four databases, each size are 8G, 400M, 18G, 500M
> there is a firewall between COM+ Server and SQL Server
> so, i have configured port configuration for MSDTC as recommended by
> Microsoft Support site
> http://support.microsoft.com/kb/250367
> almost for the past 1.5 years. my com+ application has worked 99.9999%
> fine
> but from about a month ago i got this error at every particular NIGHT
> time(ie. 22:00)
> on particular database
> [Microsoft][ODBC SQL Server Driver]Timeout expired
> Com Error : DESC-->[Microsoft][ODBC SQL Server Driver]Timeout expi
red
> MSG-->OR_20001_SN_ReceiptOrder
> IDispatch error #3121 Error Count:1 GetLastError Number:0.
> once this error occurrs, all other components which are using
> "transaction"
> get the same error over and over and over again till i restart MSDTC
> service
> or
> SQL Server Database.
> really strange thing is that this error NEVER occurrs at a daytime
> i found the fact that sp starts and never completed after tracing by using
> query profiler
> is this related to network resource or table locking?
> has anybody seen this case? or any ideas?
Help! [Microsoft][ODBC SQL Server Driver]Timeout expired
Hi all...
Environment
OS : Windows 2000 Advanced Server(SP4)
SQL Server : Microsoft SQL Server 2000(SP3)
DB Accessing : MSDTC, ODBC, COM+(VC++) calling Stored Procedure through
firewall
i have four databases, each size are 8G, 400M, 18G, 500M
there is a firewall between COM+ Server and SQL Server
so, i have configured port configuration for MSDTC as recommended by
Microsoft Support site
http://support.microsoft.com/kb/250367
almost for the past 1.5 years. my com+ application has worked 99.9999% fine
but from about a month ago i got this error at every particular NIGHT
time(ie. 22:00)
on particular database
[Microsoft][ODBC SQL Server Driver]Timeout expired
Com Error : DESC-->[Microsoft][ODBC SQL Server Driver]Timeout expired
MSG-->OR_20001_SN_ReceiptOrder
IDispatch error #3121 Error Count:1 GetLastError Number:0.
once this error occurrs, all other components which are using "transaction"
get the same error over and over and over again till i restart MSDTC service
or
SQL Server Database.
really strange thing is that this error NEVER occurrs at a daytime
i found the fact that sp starts and never completed after tracing by using
query profiler
is this related to network resource or table locking?
has anybody seen this case? or any ideas?Chan,
You should probably call MS product support and let them take a look at
this. It's hard to determine what can cause these errors without some heavy
duty troubleshooting. It could be a leak in the provider or some other
MSDTC-related problem.
Adrian
"Chan" <Chan@.discussions.microsoft.com> wrote in message
news:E472A035-D0A2-49E1-AD2A-373FE573AB5E@.microsoft.com...
> Hi all...
> Environment
> OS : Windows 2000 Advanced Server(SP4)
> SQL Server : Microsoft SQL Server 2000(SP3)
> DB Accessing : MSDTC, ODBC, COM+(VC++) calling Stored Procedure through
> firewall
> i have four databases, each size are 8G, 400M, 18G, 500M
> there is a firewall between COM+ Server and SQL Server
> so, i have configured port configuration for MSDTC as recommended by
> Microsoft Support site
> http://support.microsoft.com/kb/250367
> almost for the past 1.5 years. my com+ application has worked 99.9999%
> fine
> but from about a month ago i got this error at every particular NIGHT
> time(ie. 22:00)
> on particular database
> [Microsoft][ODBC SQL Server Driver]Timeout expired
> Com Error : DESC-->[Microsoft][ODBC SQL Server Driver]Timeout expired
> MSG-->OR_20001_SN_ReceiptOrder
> IDispatch error #3121 Error Count:1 GetLastError Number:0.
> once this error occurrs, all other components which are using
> "transaction"
> get the same error over and over and over again till i restart MSDTC
> service
> or
> SQL Server Database.
> really strange thing is that this error NEVER occurrs at a daytime
> i found the fact that sp starts and never completed after tracing by using
> query profiler
> is this related to network resource or table locking?
> has anybody seen this case? or any ideas?
Environment
OS : Windows 2000 Advanced Server(SP4)
SQL Server : Microsoft SQL Server 2000(SP3)
DB Accessing : MSDTC, ODBC, COM+(VC++) calling Stored Procedure through
firewall
i have four databases, each size are 8G, 400M, 18G, 500M
there is a firewall between COM+ Server and SQL Server
so, i have configured port configuration for MSDTC as recommended by
Microsoft Support site
http://support.microsoft.com/kb/250367
almost for the past 1.5 years. my com+ application has worked 99.9999% fine
but from about a month ago i got this error at every particular NIGHT
time(ie. 22:00)
on particular database
[Microsoft][ODBC SQL Server Driver]Timeout expired
Com Error : DESC-->[Microsoft][ODBC SQL Server Driver]Timeout expired
MSG-->OR_20001_SN_ReceiptOrder
IDispatch error #3121 Error Count:1 GetLastError Number:0.
once this error occurrs, all other components which are using "transaction"
get the same error over and over and over again till i restart MSDTC service
or
SQL Server Database.
really strange thing is that this error NEVER occurrs at a daytime
i found the fact that sp starts and never completed after tracing by using
query profiler
is this related to network resource or table locking?
has anybody seen this case? or any ideas?Chan,
You should probably call MS product support and let them take a look at
this. It's hard to determine what can cause these errors without some heavy
duty troubleshooting. It could be a leak in the provider or some other
MSDTC-related problem.
Adrian
"Chan" <Chan@.discussions.microsoft.com> wrote in message
news:E472A035-D0A2-49E1-AD2A-373FE573AB5E@.microsoft.com...
> Hi all...
> Environment
> OS : Windows 2000 Advanced Server(SP4)
> SQL Server : Microsoft SQL Server 2000(SP3)
> DB Accessing : MSDTC, ODBC, COM+(VC++) calling Stored Procedure through
> firewall
> i have four databases, each size are 8G, 400M, 18G, 500M
> there is a firewall between COM+ Server and SQL Server
> so, i have configured port configuration for MSDTC as recommended by
> Microsoft Support site
> http://support.microsoft.com/kb/250367
> almost for the past 1.5 years. my com+ application has worked 99.9999%
> fine
> but from about a month ago i got this error at every particular NIGHT
> time(ie. 22:00)
> on particular database
> [Microsoft][ODBC SQL Server Driver]Timeout expired
> Com Error : DESC-->[Microsoft][ODBC SQL Server Driver]Timeout expired
> MSG-->OR_20001_SN_ReceiptOrder
> IDispatch error #3121 Error Count:1 GetLastError Number:0.
> once this error occurrs, all other components which are using
> "transaction"
> get the same error over and over and over again till i restart MSDTC
> service
> or
> SQL Server Database.
> really strange thing is that this error NEVER occurrs at a daytime
> i found the fact that sp starts and never completed after tracing by using
> query profiler
> is this related to network resource or table locking?
> has anybody seen this case? or any ideas?
Subscribe to:
Posts (Atom)