I was using SQL 7. I uninstalled this and started installing SQL Server 2000 DEsktop Engine. However, install never goes thru and I get this message.
Any ideas would be appreciated.
ThanksHave you tried what the message says?|||This is what the READ ME file says.
3.1.4 Desktop Engine Setup Parameters
SQL Server Books Online topics "Merging the Desktop Engine into
Windows Installer" and "SQL Server 2000 Desktop Engine Setup"
document two parameters that are ignored by the final version
of the Desktop Engine Setup: USEDEFAULTSAPWD and SAPASSWORD.
By default, when run on the Microsoft Windows NT 4.0 or Windows
2000 operating system, the Desktop Engine Setup configures the
installed instance of Microsoft SQL Server to use Windows
Authentication, and places the Windows local administrator's group
in the SQL Server sysadmin fixed server role. When running Desktop
Engine Setup on the Windows NT 4.0 or Windows 2000 operating
system, you can specify a SECURITYMODE=SQL parameter to have the
installed instance configured to use SQL Server Authentication
with a null sa password. When run on the Windows 98 operating
system, the Desktop Engine Setup always configures the installed
instance to use SQL Server Authentication, regardless of whether
or not SECURITYMODE=SQL is specified.
A set of Desktop Engine merge modules that have been merged into
a Windows Installer setup has the same behavior. On the Windows
NT 4.0 and Windows 2000 operating systems, the instance of SQL
Server is configured to use Windows Authentication if
SECURITYMODE=SQL is not specified, and is configured to use SQL
Server Authentication if SECURITYMODE=SQL is specified. The
instance is always configured to use SQL Server Authentication
on the Windows 98 operating system.
You can specify SECURITYMODE=SQL in the same locations where you
can use USEDEFAULTSAPWD or SAPASSWORD. For more information, see
the SQL Server Books Online topics "Merging the Desktop Engine
into Windows Installer" and "SQL Server 2000 Desktop Engine Setup."
Anyway, under the SETUP.INI file, I placed SAPWD=<PASSWORD> and the installation went through.
:)
Showing posts with label thru. Show all posts
Showing posts with label thru. Show all posts
Wednesday, March 21, 2012
Friday, March 9, 2012
Inserts not committing
A user entered 20 debit memos thru the application. For each db memo, 1 - th
e
data is inserted into two SQL Server 2000 tables, 2- a commit is issued
(Begin Trans / Commit Trans), 3 - a Select is used to retrieve data to
display on the db memo thru Crystal Reports and is printed. For each of the
20 entered, a db memo was printed but when the application closed, only data
for the first four db memos was saved / committed in the database. The other
16 had not been saved / committed in the database. We know the data for the
16 were inserted or else the Select would not have retrieved the data to
display and print the DB memo. There were no error messages and the
application did not crash. This happened only three times in 18 months and w
e
cannot duplicate the error. The commits are all processed in the same VB for
m
flow code. Anyone ever have a similar issue? Anyone have an idea on what
might have occurred? Thanx.Are you printing inside the transaction?
AMB
"Inserts not committing" wrote:
> A user entered 20 debit memos thru the application. For each db memo, 1 -
the
> data is inserted into two SQL Server 2000 tables, 2- a commit is issued
> (Begin Trans / Commit Trans), 3 - a Select is used to retrieve data to
> display on the db memo thru Crystal Reports and is printed. For each of th
e
> 20 entered, a db memo was printed but when the application closed, only da
ta
> for the first four db memos was saved / committed in the database. The oth
er
> 16 had not been saved / committed in the database. We know the data for th
e
> 16 were inserted or else the Select would not have retrieved the data to
> display and print the DB memo. There were no error messages and the
> application did not crash. This happened only three times in 18 months and
we
> cannot duplicate the error. The commits are all processed in the same VB f
orm
> flow code. Anyone ever have a similar issue? Anyone have an idea on what
> might have occurred? Thanx.
e
data is inserted into two SQL Server 2000 tables, 2- a commit is issued
(Begin Trans / Commit Trans), 3 - a Select is used to retrieve data to
display on the db memo thru Crystal Reports and is printed. For each of the
20 entered, a db memo was printed but when the application closed, only data
for the first four db memos was saved / committed in the database. The other
16 had not been saved / committed in the database. We know the data for the
16 were inserted or else the Select would not have retrieved the data to
display and print the DB memo. There were no error messages and the
application did not crash. This happened only three times in 18 months and w
e
cannot duplicate the error. The commits are all processed in the same VB for
m
flow code. Anyone ever have a similar issue? Anyone have an idea on what
might have occurred? Thanx.Are you printing inside the transaction?
AMB
"Inserts not committing" wrote:
> A user entered 20 debit memos thru the application. For each db memo, 1 -
the
> data is inserted into two SQL Server 2000 tables, 2- a commit is issued
> (Begin Trans / Commit Trans), 3 - a Select is used to retrieve data to
> display on the db memo thru Crystal Reports and is printed. For each of th
e
> 20 entered, a db memo was printed but when the application closed, only da
ta
> for the first four db memos was saved / committed in the database. The oth
er
> 16 had not been saved / committed in the database. We know the data for th
e
> 16 were inserted or else the Select would not have retrieved the data to
> display and print the DB memo. There were no error messages and the
> application did not crash. This happened only three times in 18 months and
we
> cannot duplicate the error. The commits are all processed in the same VB f
orm
> flow code. Anyone ever have a similar issue? Anyone have an idea on what
> might have occurred? Thanx.
Subscribe to:
Posts (Atom)