MS SQL7 (Desktop) error

Hi,
I am getting error 1802, CREATE DATABASE failed. Some file
names listed could not be created. Check previous errors.
I have Windows 2000 professional installed on my PC.
I am installing remedy 5.1 that uses MSSQL server 7 and I
am getting the error above on remedy instalation...
Any idea'
ThanksI suggest you talk to the vendor of remedy. SQL Server returned more error
messages and you really need those error messages to see what the problem
is.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Taiser" <anonymous@.discussions.microsoft.com> wrote in message
news:1b8c01c3ff4d$64d17880$a601280a@.phx.gbl...
> Hi,
> I am getting error 1802, CREATE DATABASE failed. Some file
> names listed could not be created. Check previous errors.
>
> I have Windows 2000 professional installed on my PC.
> I am installing remedy 5.1 that uses MSSQL server 7 and I
> am getting the error above on remedy instalation...
> Any idea'
> Thanks

MS SQL7 (Desktop) error

Hi,
I am getting error 1802, CREATE DATABASE failed. Some file
names listed could not be created. Check previous errors.
I have Windows 2000 professional installed on my PC.
I am installing remedy 5.1 that uses MSSQL server 7 and I
am getting the error above on remedy instalation...
Any idea'
ThanksI suggest you talk to the vendor of remedy. SQL Server returned more error
messages and you really need those error messages to see what the problem
is.
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Taiser" <anonymous@.discussions.microsoft.com> wrote in message
news:1b8c01c3ff4d$64d17880$a601280a@.phx.gbl...
> Hi,
> I am getting error 1802, CREATE DATABASE failed. Some file
> names listed could not be created. Check previous errors.
>
> I have Windows 2000 professional installed on my PC.
> I am installing remedy 5.1 that uses MSSQL server 7 and I
> am getting the error above on remedy instalation...
> Any idea'
> Thankssql

MS SQL2005 Updata from SP1 to SP2 Fail

Windows 2003 SP2 Updata MS SQL 2005 from SP1 to SP2 fail.

Hotfix_5.log

07/31/2007 23:15:32.745 ================================================================================
{..........................................

.........................................

........................................}
07/31/2007 23:15:54.236
07/31/2007 23:15:54.246 Product Enumeration Results:
07/31/2007 23:15:54.246 INF File Name: c:\ace3346e16b7688715bb0ff855\HotFixSqlxml4.inf
07/31/2007 23:15:54.246 baselinebuild = 1399
07/31/2007 23:15:54.246 build = 3042
07/31/2007 23:15:54.246 description = SQLXML4
07/31/2007 23:15:54.256 details = Service Pack for Microsoft SQLXML 4.0.
07/31/2007 23:15:54.256 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
07/31/2007 23:15:54.256 kbarticle = KB921896
07/31/2007 23:15:54.256 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
07/31/2007 23:15:54.266 lcid = 1033
07/31/2007 23:15:54.266 legalproductname = SQLXML4
07/31/2007 23:15:54.266 machinetype = x86
07/31/2007 23:15:54.266 package = HotFixSqlxml4
07/31/2007 23:15:54.266 packagetype = Hotfix
07/31/2007 23:15:54.276 productcode = {A188FCCF-E929-494D-B1F1-4313E02ACD52}
07/31/2007 23:15:54.276 productname = Redist9
07/31/2007 23:15:54.276 recommendinstall = 1
07/31/2007 23:15:54.276 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
07/31/2007 23:15:54.276 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
07/31/2007 23:15:54.286 splevel = 2
07/31/2007 23:15:54.286 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
07/31/2007 23:15:54.286 supportdir = c:\ace3346e16b7688715bb0ff855
07/31/2007 23:15:54.286 upgradecode = {D9CA3D82-6F1B-41A7-8141-B90ACA8F865B}
07/31/2007 23:15:54.286 version = 9
07/31/2007 23:15:54.286
07/31/2007 23:15:54.296 File Group Details: MSI
07/31/2007 23:15:54.296 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
07/31/2007 23:15:54.296 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
07/31/2007 23:15:54.296 File Details: sqlxml4.msi
07/31/2007 23:15:54.296
07/31/2007 23:15:54.296 Instance Details: SQLXML4
07/31/2007 23:15:54.306 fullversion = 9.00.2047.00
07/31/2007 23:15:54.306 lcid = 1033
07/31/2007 23:15:54.306 productcode = {A188FCCF-E929-494D-B1F1-4313E02ACD52}
07/31/2007 23:15:54.306 qfelevel = 2047
07/31/2007 23:15:54.306 sp = -1
07/31/2007 23:15:54.316
07/31/2007 23:15:54.316 Product Enumeration Results:
07/31/2007 23:15:54.316 INF File Name: c:\ace3346e16b7688715bb0ff855\HotFixSqlxml4_x64.inf
07/31/2007 23:15:54.316 baselinebuild = 1399
07/31/2007 23:15:54.316 build = 3042
07/31/2007 23:15:54.316 description = SQLXML4
07/31/2007 23:15:54.326 details = Service Pack for Microsoft SQLXML 4.0.
07/31/2007 23:15:54.326 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
07/31/2007 23:15:54.326 kbarticle = KB921896
07/31/2007 23:15:54.326 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
07/31/2007 23:15:54.326 lcid = 1033
07/31/2007 23:15:54.336 legalproductname = SQLXML4 (64-bit)
07/31/2007 23:15:54.336 machinetype = x64
07/31/2007 23:15:54.336 package = HotFixSqlxml4_x64
07/31/2007 23:15:54.336 packagetype = Hotfix
07/31/2007 23:15:54.336 productname = Redist9
07/31/2007 23:15:54.346 recommendinstall = 1
07/31/2007 23:15:54.346 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
07/31/2007 23:15:54.346 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
07/31/2007 23:15:54.346 splevel = 2
07/31/2007 23:15:54.346 supportdir = c:\ace3346e16b7688715bb0ff855
07/31/2007 23:15:54.356 upgradecode = {F457D8E6-7686-437D-9B17-E21D45CCABD8}
07/31/2007 23:15:54.356 version = 9
07/31/2007 23:15:54.356
07/31/2007 23:15:54.356 File Group Details: MSI
07/31/2007 23:15:54.356 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
07/31/2007 23:15:54.356 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
07/31/2007 23:15:54.366 File Details: sqlxml4_x64.msi
07/31/2007 23:15:54.366
07/31/2007 23:15:54.366 Product Enumeration Results:
07/31/2007 23:15:54.366 INF File Name: c:\ace3346e16b7688715bb0ff855\HotFixSQLServer2005_BC.inf
07/31/2007 23:15:54.366 baselinebuild = 1399
07/31/2007 23:15:54.376 build = 2004
07/31/2007 23:15:54.376 description = Backward Compatibility
07/31/2007 23:15:54.376 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
07/31/2007 23:15:54.376 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
07/31/2007 23:15:54.376 kbarticle = KB921896
07/31/2007 23:15:54.386 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
07/31/2007 23:15:54.386 lcid = 1033
07/31/2007 23:15:54.386 legalproductname = Microsoft SQL Server 2005 Backward Compatibility
07/31/2007 23:15:54.386 machinetype = x86
07/31/2007 23:15:54.386 package = HotFixSQLServer2005_BC
07/31/2007 23:15:54.396 packagetype = Hotfix
07/31/2007 23:15:54.396 productcode = {2243F21A-E132-44F7-BA13-024D0845C815}
07/31/2007 23:15:54.396 productname = Redist9
07/31/2007 23:15:54.406 recommendinstall = 1
07/31/2007 23:15:54.406 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
07/31/2007 23:15:54.406 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
07/31/2007 23:15:54.406 splevel = 2
07/31/2007 23:15:54.406 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
07/31/2007 23:15:54.406 supportdir = c:\ace3346e16b7688715bb0ff855
07/31/2007 23:15:54.416 upgradecode = {1E70C6C9-E1B7-4A74-BC8C-8EB5D010CEC9}
07/31/2007 23:15:54.416 version = 9
07/31/2007 23:15:54.416
07/31/2007 23:15:54.416 File Group Details: MSI
07/31/2007 23:15:54.416 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
07/31/2007 23:15:54.416 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
07/31/2007 23:15:54.426 File Details: SQLServer2005_BC.msi
07/31/2007 23:15:54.426
07/31/2007 23:15:54.426 Instance Details: Backward Compatibility
07/31/2007 23:15:54.426 fullversion = 8.05.1704
07/31/2007 23:15:54.436 lcid = 1033
07/31/2007 23:15:54.436 productcode = {2243F21A-E132-44F7-BA13-024D0845C815}
07/31/2007 23:15:54.436 qfelevel = 1704
07/31/2007 23:15:54.436 sp = -1
07/31/2007 23:15:54.436
07/31/2007 23:15:54.446 Product Enumeration Results:
07/31/2007 23:15:54.446 INF File Name: c:\ace3346e16b7688715bb0ff855\HotFixSQLServer2005_BC_x64.inf
07/31/2007 23:15:54.446 baselinebuild = 1399
07/31/2007 23:15:54.446 build = 2004
07/31/2007 23:15:54.446 description = Backward Compatibility
07/31/2007 23:15:54.446 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
07/31/2007 23:15:54.457 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
07/31/2007 23:15:54.457 kbarticle = KB921896
07/31/2007 23:15:54.457 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
07/31/2007 23:15:54.457 lcid = 1033
07/31/2007 23:15:54.457 legalproductname = Microsoft SQL Server 2005 Backward Compatibility (64-bit)
07/31/2007 23:15:54.467 machinetype = x64
07/31/2007 23:15:54.467 package = HotFixSQLServer2005_BC_x64
07/31/2007 23:15:54.467 packagetype = Hotfix
07/31/2007 23:15:54.467 productname = Redist9
07/31/2007 23:15:54.467 recommendinstall = 1
07/31/2007 23:15:54.467 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
07/31/2007 23:15:54.477 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
07/31/2007 23:15:54.477 splevel = 2
07/31/2007 23:15:54.477 supportdir = c:\ace3346e16b7688715bb0ff855
07/31/2007 23:15:54.477 upgradecode = {7B6BF434-3C72-4DB3-8049-FEF31AEAFF9A}
07/31/2007 23:15:54.477 version = 9
07/31/2007 23:15:54.487
07/31/2007 23:15:54.487 File Group Details: MSI
07/31/2007 23:15:54.487 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
07/31/2007 23:15:54.487 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
07/31/2007 23:15:54.487 File Details: SQLServer2005_BC_x64.msi
07/31/2007 23:15:54.497
07/31/2007 23:15:54.497 Product Enumeration Results:
07/31/2007 23:15:54.497 INF File Name: c:\ace3346e16b7688715bb0ff855\HotFixSqlWriter.inf
07/31/2007 23:15:54.497 baselinebuild = 1399
07/31/2007 23:15:54.497 build = 3042
07/31/2007 23:15:54.497 description = Microsoft SQL Server VSS Writer
07/31/2007 23:15:54.507 details = Service Pack for Microsoft SQL Server VSS Writer.
07/31/2007 23:15:54.507 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
07/31/2007 23:15:54.507 kbarticle = KB921896
07/31/2007 23:15:54.507 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
07/31/2007 23:15:54.517 lcid = 1033
07/31/2007 23:15:54.517 legalproductname = Microsoft SQL Server VSS Writer
07/31/2007 23:15:54.517 machinetype = x86
07/31/2007 23:15:54.517 package = HotFixSqlWriter
07/31/2007 23:15:54.517 packagetype = Hotfix
07/31/2007 23:15:54.527 productcode = {C0D2F614-5CE5-4DCB-8678-E5C9AF7044F8}
07/31/2007 23:15:54.527 productname = Redist9
07/31/2007 23:15:54.527 recommendinstall = 1
07/31/2007 23:15:54.527 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
07/31/2007 23:15:54.527 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
07/31/2007 23:15:54.527 splevel = 2
07/31/2007 23:15:54.527 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
07/31/2007 23:15:54.537 supportdir = c:\ace3346e16b7688715bb0ff855
07/31/2007 23:15:54.537 upgradecode = {65D8E1DF-6201-4B53-A0F9-E654F8E80F97}
07/31/2007 23:15:54.537 version = 9
07/31/2007 23:15:54.537
07/31/2007 23:15:54.537 File Group Details: MSI
07/31/2007 23:15:54.547 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
07/31/2007 23:15:54.547 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
07/31/2007 23:15:54.547 File Details: SqlWriter.msi
07/31/2007 23:15:54.547
07/31/2007 23:15:54.547 Instance Details: Microsoft SQL Server VSS Writer
07/31/2007 23:15:54.547 fullversion = 9.00.2047.00
07/31/2007 23:15:54.557 lcid = 1033
07/31/2007 23:15:54.557 productcode = {C0D2F614-5CE5-4DCB-8678-E5C9AF7044F8}
07/31/2007 23:15:54.557 qfelevel = 2047
07/31/2007 23:15:54.557 sp = -1
07/31/2007 23:15:54.567
07/31/2007 23:15:54.567 Product Enumeration Results:
07/31/2007 23:15:54.567 INF File Name: c:\ace3346e16b7688715bb0ff855\HotFixSqlWriter_x64.inf
07/31/2007 23:15:54.567 baselinebuild = 1399
07/31/2007 23:15:54.567 build = 3042
07/31/2007 23:15:54.567 description = Microsoft SQL Server VSS Writer
07/31/2007 23:15:54.577 details = Service Pack for Microsoft SQL Server VSS Writer.
07/31/2007 23:15:54.577 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
07/31/2007 23:15:54.577 kbarticle = KB921896
07/31/2007 23:15:54.577 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
07/31/2007 23:15:54.577 lcid = 1033
07/31/2007 23:15:54.577 legalproductname = Microsoft SQL Server VSS Writer (64-bit)
07/31/2007 23:15:54.587 machinetype = x64
07/31/2007 23:15:54.587 package = HotFixSqlWriter_x64
07/31/2007 23:15:54.587 packagetype = Hotfix
07/31/2007 23:15:54.587 productname = Redist9
07/31/2007 23:15:54.587 recommendinstall = 1
07/31/2007 23:15:54.587 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
07/31/2007 23:15:54.597 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
07/31/2007 23:15:54.597 splevel = 2
07/31/2007 23:15:54.597 supportdir = c:\ace3346e16b7688715bb0ff855
07/31/2007 23:15:54.597 upgradecode = {E9031696-DD39-4C25-BAEB-425FF28279EA}
07/31/2007 23:15:54.597 version = 9
07/31/2007 23:15:54.607
07/31/2007 23:15:54.607 File Group Details: MSI
07/31/2007 23:15:54.607 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
07/31/2007 23:15:54.607 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
07/31/2007 23:15:54.607 File Details: SqlWriter_x64.msi
07/31/2007 23:15:54.607
07/31/2007 23:16:19.753 Registry: Opened registry key "System\CurrentControlSet\Control\Session Manager"
07/31/2007 23:16:19.783 Registry: Cannot read registry key value "PendingFileRenameOperations"
07/31/2007 23:16:19.813 Registry: Read registry key value "EnableErrorReporting", DWORD value = 1
07/31/2007 23:16:19.813 Registry: Read registry key value "CustomerFeedBack", DWORD value = 1
07/31/2007 23:16:20.714 Registry: Set registry key value "EnableErrorReporting", DWORD value = 1
07/31/2007 23:16:20.714 Registry: Set registry key value "CustomerFeedBack", DWORD value = 1
07/31/2007 23:16:20.774 Locked file: Checking for locked files
07/31/2007 23:16:45.530 Attempting to pause the 32 bit ngen queue
07/31/2007 23:16:46.371 Installing product: SQLTools9
07/31/2007 23:16:46.381 Installing instance: SQL Tools
07/31/2007 23:16:46.411 Installing target: MSTS0000
07/31/2007 23:16:46.411 Installing file: sqlrun_tools.msp
07/31/2007 23:16:46.451 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log
07/31/2007 23:16:46.451 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
07/31/2007 23:16:46.451 Registry: Cannot read registry key value "Debug"

Somebody help me in this issue..Please....

|||

did you check this,

Registry: Cannot read registry key value "PendingFileRenameOperations"
Registry: Cannot read registry key value "Debug"

dunno if this is the reason....

MS SQL2005 reporting Services + AD. Security question

Hi we run completely Windows shop. So Windows Authentication for Reporting Services is only acceptable solution. Idea is that I assign user in RS manager but they get their security check through AD using Cerberus or whatever it is. We did this setup for intranet web site which consist three machine

PC#1 Domain controller (AD)

PC#2 IIS (intranet web site)

PC#3 MS SQL server. (data)

People logon on web server newer asked for credentials on pull up data from SQL server though IIS being themselves, impersonation.

Now I have setup

PC#1 SSRS, IIS for Reports Server, MS SQL 2k5 for RS metadata etc

PC#2 Domain controller (AD)

PC#3 MS SQL2k (data)

I did same setspn procedure but when I tried to log on Report server it asked me for credentials. Moreover when I provide my logon and password it denies it, accepting only admin credentials.

I went trough few books, number article but nobody describe this scenario in spite it should be most popular solution if network based on Windows.

Any help is really appreciated

I am a way out of my league here, but I don't think it is the Report Server who prompts for credentials but IIS. If you create a web app in IIS configured for Windows authentiction and drop a simple html file in it, i bet you will be prompted for when you try to browse it. As far as what's causing it (excluding configuration issues), you may find the following article useful.|||

Teo,

Thanks a lot. I should read this article monthes ago. It is simple and nice compilation about delegation. I will try my luck with tweaking Report Server config and SPN.

I'll keep posting how I am doing, I think it will be helpfull for everybody who will decide to implement SSRS2k5 similar way

MS SQL uses 100% of my 2 CPU machine

Hello,

I just installed MS SQL 2000 Enterprise on a Windows 2000 Server machine
with 2 CPU's. After starting the MS SQL takes 2 x 100% of all CPU power.
I do NOT load the DB in any way with queries. Obviously this leads to
all kinds of software not working well anymore. Does anyone know how to
lower the CPU power used? Please help!?

regards,

Pierre Verbakel
The NetherlandsUnder the server properties in EM (right-click server name), under the
processor tab you can control the priority (to some degree), also you
can control how many processors SQL Server uses. I had a similar
problem with memory on an older server with only one processor. SQL
Server is notorious for being a memory hog regardless of how many
queries or users are on the system. For more of the advanced control
options related to memory tweaking and usage you need the high-end
versions of NT server and SQL Server. Although, I think that most low
to mid-size companies get by with the Standard Edition. I recommend
running only SQL Server on the server, not mixing other products like
IIS or or other applications.

HTH

P Verbakel <p.verbakel3@.chello.nl> wrote in message news:<3EFC0E13.5010809@.chello.nl>...
> Hello,
> I just installed MS SQL 2000 Enterprise on a Windows 2000 Server machine
> with 2 CPU's. After starting the MS SQL takes 2 x 100% of all CPU power.
> I do NOT load the DB in any way with queries. Obviously this leads to
> all kinds of software not working well anymore. Does anyone know how to
> lower the CPU power used? Please help!?
> regards,
> Pierre Verbakel
> The Netherlands|||If you have 100% CPU use on a fresh install, one possible reason is
the SQL Slammer worm. You don't mention if you've installed any
servicepacks, but if not, then you should update your installation as
a first step. If that resolves your issue, and you suspect that
Slammer is the cause, then you should investigate other MSSQL
installations on your network (including MSDE) to see if they are
infected - Microsoft has some tools to help.

But if you have everything already patched and up to date, then
perhaps you can give some more information about the server? In
particular, does it have other applications installed, or is it
dedicated to MSSQL? Do you have an antivirus scanner on the server
that might be continuously scanning the DB files?

Simon

P Verbakel <p.verbakel3@.chello.nl> wrote in message news:<3EFC0E13.5010809@.chello.nl>...
> Hello,
> I just installed MS SQL 2000 Enterprise on a Windows 2000 Server machine
> with 2 CPU's. After starting the MS SQL takes 2 x 100% of all CPU power.
> I do NOT load the DB in any way with queries. Obviously this leads to
> all kinds of software not working well anymore. Does anyone know how to
> lower the CPU power used? Please help!?
> regards,
> Pierre Verbakel
> The Netherlands|||It is really very easy.

1. Startup Enterprise Manager
2. Right click the machine that is running SQL and select the
properties menu option
3. Select the memory tab. I would probably recommend still using the
dynamic option but set a maximum

MS SQL Update Error

I have a database on a MSSQL Server 7 running on a Windows NT machine. This database works the last 4years with no problem. The database file is now 3 GB with 45 users. The last two months every single day an update error on a specific Table occurs. I cannot update a record in this table, and after this error occurs more than 100 records or more seemed to be locked. While I cannot edit the previous records I can create a new one with no problem. I have this problem once every sigle working day (ant the currious thing is that is occured from 8 to 10 in the morning every singke working day) . The table seems to work again after some hours or after one single day, or after I stop and start again the sql server service. Some times I have to wait some hours in order to manage to edit records in this table again. (I edit the records by using a program created with Microsoft Access and ODBC. When the error occurs I cannot edit the records neither by Access not by SQL Server Query Analyser).
This error doesn't occur when entering a new record, and might occur when only one user works with the specific Table. This table has 75 fields and about 70000 records. This table is the master of a table which has more than 200 fields and more than 750000 records. In the detail table I have no problems.
Similar problems not in this degree exist on a second database installation with about 25 users with the same table but running under a Windows 2000 Server machine.

Well when the problem appearead again I tried to edit the locked records by using Access ODBC, Access (adp project), Delphi with ADO-OLEDB and Delphi with native SQL drivers. The result was the same. A Timeout expired message appear. In the application log file of the MS SQLserver machine every time the the update error appears I get the following message: Could not Set Up Listen on Connection '1433'. Operating system Error 10049.

Any ideas??

Best regards,
Manolis PerrakisCan you supply the wording of the update error?

Also, since it tends to happen from 8-10 most mornings, you can check for blocking problems by running sp_who2 in Query Analyzer. If there are numbers in the "BlkBy" column, you have problems. Hopefully you will be able to figure out the blocker by the program- or host-name in the output of sp_who2.|||I don't have a solution for you. But I have experienced more than my share of timeouts and there's one thing I've learned: it's never what it says it is. But it seems to happen more the larger the number of elements there are in an index, and less on more normal databases. And we suspect it may be related to our use of EIDE drives instead of SCSI.

And I strongly suspect it has something to do with resources. For example: If you execute an update query causing SQL Server to execute a series of subqueries, and one of them hits a resource ceiling, one of the others with time out waiting for a thread to finish. The thread never finishes, because it's waiting for resources to be freed before it can continue. This happens all the time on our 1 GHZ server with 1GB of RAM.

I suggest you check all your indexes and make sure they're not clustered. Also, make sure you're not using too many connections if you can avoid it. And if you have too many tables that aren't normalized, try to fix that as well. Finally, you can do what I'm planning to do: change to MySql server or something else. IMNSHO, Sql Server isn't as robust as it could be.

I hope this helps.|||One other thing...Port 1433 is where SQL Server listens for connection requests. You're not opening the database everytime you do an update, are you?|||Thanks for the suggestions. My server is a Compaq ML350 with 3 SCSII hards disks and a Raid Controller, and about 600 MB RAM. I can see from the task manager that it uses all the resources. I might increase the RAM memory and in the next months I might get a new server.

Please tell me if there is a serious problem the fact that I also store in this server about 10000 photos with sizes about 2 GB, that are displayed as product pictures in the database program I've created.

I also have to mention that I use a lot of subqueries in the MSAccess program I use right now.

As far the connections issues, since I now use MSAccess for the clients, each table that is connected (attached) to the MSSQL Server holds internally its connection properies (datasource name, database name, username etc..), and since that I have about 200 tables attached from the SQL Server, this might create a connection problem.

I'm currently moving to Delphi 7, which has a global connection for all the tables of the same server. In this version the subqueries are replaced with optimised queries, and client datasets will be used in order to decrease the server load.

Best Regards,
Manolis Perrakis|||The data I store in image fields is usually quite a bit less than yours, but I don't think that's a problem. But I'm pretty sure the RAM is. You can improve things somewhat by making sure your logfile is on a different disk drive than the database, if you haven't done so already.

Try to get away from holding tables open where you can. Also, if you have a lot of indices on the master table, or a high number of values in the master index, I know from experience that can cause problems. Those problems can be alleviated by adding more RAM, further normalizing your database to reduce the number of keys (if that's possible), or looking at ways to reduce the amount of index storage--making sure you're not using clustered indexes, making sure that you're not using full-text indexing if you don't need it.

But I'm also wondering whether it's the bound controls that are the problem. At 8:00 is when everyone comes into work and launches the app, right? And by 10:00, app use drops down to a manageable level? Tables linked to app forms are almost always in Dynamic mode and I'm assuming that's the case here. If you were to modify your app so that the most common screens were read (releasing the recordset and holding the data in memory), and perform updates as that data was written (creating a new recordset for writing), you'd probably reduce the load on Sql Server significantly.

Not that any of this presents a panacea. I've spent the majority of my bugchasing over the past couple of years on problems with SQL Server/ADO. If I had any time at all, I would switch like a Tareyton smoker. :) But I think this problem can be solved.

MS SQL Update Error

I have a database on a MSSQL Server 7 running on a Windows NT machine. This database works the last 4years with no problem. The database file is now 3 GB. The last two months every single day an update error on a specific Table occurs. I cannot update a record in this table, and after this error occurs more than 100 records or more seemed to be locked. While I cannot edit the previous records I can create a new one with no problem. I have this problem once every sigle working day (ant the currious thing is that is occured from 8 to 10 in the morning every singke working day) . The table seems to work again after some hours or after one single day, or after I stop and start again the sql server service. Some times I have to wait some hours in order to manage to edit records in this table again. (I edit the records by using a program created with Microsoft Access and ODBC. When the error occurs I cannot edit the records neither by Access not by SQL Server Query Analyser).
This error doesn't occur when entering a new record, and might occur when only one user works with the specific Table. This table has 75 fields and about 70000 records.
Similar problems not in this degree exist on a second database installation with about 25 users with the same table but running under a Windows 2000 Server machine.
Any ideas??

Best Regards,
Manolis Perrakis
manolo_perrakis@.mail.grDoes the error occur when you try to edit the records using ONLY query analyzer?

Are you using an MS Access mdb file to edit the data, or are you using a Microsoft Access Data Project (ADP) file?

blindman|||Does the error occur when you try to edit the records using ONLY query analyzer?

Are you using an MS Access mdb file to edit the data, or are you using a Microsoft Access Data Project (ADP) file?

The error occurs both with Access (I'm using an mdb file connected with ODBC with SQL Server) and with the Query Analyser. When this error occurs I cannot edit this table from any computer in the network.
Therefore I'm trying to edit the table using ODBC. I haven't tried by using an ADP project, or by using another program like Delphi which uses another connection method like OLE DB.|||when you get to the point when "this" error occurrs again, can you switch to query analyzer and write an update query for a specific record?
after you get "that" error in query analyzer, paste it here. i suspect you can also get this error from sql server errorlog by double-clicking on the entry with the error. i suspect the error you're getting is referencing the total record length. if this is the case you'll need to either shrink a couple of fields or split the table into two to allow for all your fields to be updateable. to do that seemlessly for the front-end you'll have to write a view and reference this view in your inserts, updates, deletes, and selects.

MS SQL Std on Win 2k Pro

Hello.
Is it possible to run MS SQL 2000 Server Standart Edition on Windows 2000
Pro, not Windows 2000 Server ?
bn
> Is it possible to run MS SQL 2000 Server Standart Edition on Windows 2000
> Pro, not Windows 2000 Server ?
No - check possible combinations at
http://www.microsoft.com/sql/evaluat...0/default.asp.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
|||As stated in the link Dejan provided, you need a server OS to run Standard
Edition. However, the Developer Edition provides the same features as the
Enterprise Edition with licensing restrictions and can run on a client OS
like XP Pro.
Hope this helps.
Dan Guzman
SQL Server MVP
"bala nemate" <headq[@.]bamba.lt> wrote in message
news:%23shu6EKlEHA.2140@.TK2MSFTNGP15.phx.gbl...
> Hello.
> Is it possible to run MS SQL 2000 Server Standart Edition on Windows 2000
> Pro, not Windows 2000 Server ?
> bn
>
sql

MS SQL Std on Win 2k Pro

Hello.
Is it possible to run MS SQL 2000 Server Standart Edition on Windows 2000
Pro, not Windows 2000 Server ?
bn> Is it possible to run MS SQL 2000 Server Standart Edition on Windows 2000
> Pro, not Windows 2000 Server ?
No - check possible combinations at
http://www.microsoft.com/sql/evaluation/sysreqs/2000/default.asp.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com|||As stated in the link Dejan provided, you need a server OS to run Standard
Edition. However, the Developer Edition provides the same features as the
Enterprise Edition with licensing restrictions and can run on a client OS
like XP Pro.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"bala nemate" <headq[@.]bamba.lt> wrote in message
news:%23shu6EKlEHA.2140@.TK2MSFTNGP15.phx.gbl...
> Hello.
> Is it possible to run MS SQL 2000 Server Standart Edition on Windows 2000
> Pro, not Windows 2000 Server ?
> bn
>

MS SQL Standard Edition Memory.

I understand that MS SQL Standard Edition has a 2GB memory
limit. Windows 2000 server supports 4GB of memory. My
hardware supports two processors. If I license per
Processor method and install two processors and license
two Standard editions will there be 2GB of memory per
processor or 2GB for both processors?
Thanks2GB address space is per SQLServer process(sqlserver.exe). It is nothing to
do with the processor. You can increase the SQLServer address space by
setting /3GB switch in boot.ini
This will leave just 1 GB for OS. May interfere with some of your video
drivers
-kumar
"ddavids@.idfbins.com" wrote:
> I understand that MS SQL Standard Edition has a 2GB memory
> limit. Windows 2000 server supports 4GB of memory. My
> hardware supports two processors. If I license per
> Processor method and install two processors and license
> two Standard editions will there be 2GB of memory per
> processor or 2GB for both processors?
> Thanks
>|||This is a multi-part message in MIME format.
--=_NextPart_000_0016_01C4AB13.8A8C37F0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
Beware that Sql server 2000 standard edition does not support /3gb =switch. This is only supported in Sql server 2000 enterprise edition.
Tunji
"Kumar Part" <Kumar Part@.discussions.microsoft.com> wrote in message =news:8E572684-C9AE-4679-BC12-4B56003EB4B8@.microsoft.com...
2GB address space is per SQLServer process(sqlserver.exe). It is =nothing to do with the processor. You can increase the SQLServer address space by =
setting /3GB switch in boot.ini
This will leave just 1 GB for OS. May interfere with some of your =video drivers
-kumar
"ddavids@.idfbins.com" wrote:
> I understand that MS SQL Standard Edition has a 2GB memory > limit. Windows 2000 server supports 4GB of memory. My > hardware supports two processors. If I license per > Processor method and install two processors and license > two Standard editions will there be 2GB of memory per > processor or 2GB for both processors?
> > Thanks > >
--=_NextPart_000_0016_01C4AB13.8A8C37F0
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Beware that Sql server 2000 standard =edition does not support /3gb switch. This is only supported in Sql server 2000 =enterprise edition.
Tunji
"Kumar Part" wrote in message news:8E5=72684-C9AE-4679-BC12-4B56003EB4B8@.microsoft.com...
2GB address space is per SQLServer process(sqlserver.exe). It is nothing =to do with the processor. You can increase the SQLServer address space by setting /3GB switch in boot.iniThis will leave just 1 GB =for OS. May interfere with some of your video =drivers-kumar"ddavids@.idfbins.com" =wrote:> I understand that MS SQL Standard Edition has a 2GB memory > limit. Windows 2000 server supports 4GB of memory. My => hardware supports two processors. If I license per > =Processor method and install two processors and license > two Standard =editions will there be 2GB of memory per > processor or 2GB for both processors?> > Thanks > >

---

--=_NextPart_000_0016_01C4AB13.8A8C37F0--

MS SQL Standard Edition Memory.

I understand that MS SQL Standard Edition has a 2GB memory
limit. Windows 2000 server supports 4GB of memory. My
hardware supports two processors. If I license per
Processor method and install two processors and license
two Standard editions will there be 2GB of memory per
processor or 2GB for both processors?
Thanks
2GB address space is per SQLServer process(sqlserver.exe). It is nothing to
do with the processor. You can increase the SQLServer address space by
setting /3GB switch in boot.ini
This will leave just 1 GB for OS. May interfere with some of your video
drivers
-kumar
"ddavids@.idfbins.com" wrote:

> I understand that MS SQL Standard Edition has a 2GB memory
> limit. Windows 2000 server supports 4GB of memory. My
> hardware supports two processors. If I license per
> Processor method and install two processors and license
> two Standard editions will there be 2GB of memory per
> processor or 2GB for both processors?
> Thanks
>
|||Beware that Sql server 2000 standard edition does not support /3gb switch. This is only supported in Sql server 2000 enterprise edition.
Tunji
"Kumar Part" <Kumar Part@.discussions.microsoft.com> wrote in message news:8E572684-C9AE-4679-BC12-4B56003EB4B8@.microsoft.com...
2GB address space is per SQLServer process(sqlserver.exe). It is nothing to
do with the processor. You can increase the SQLServer address space by
setting /3GB switch in boot.ini
This will leave just 1 GB for OS. May interfere with some of your video
drivers
-kumar
"ddavids@.idfbins.com" wrote:

> I understand that MS SQL Standard Edition has a 2GB memory
> limit. Windows 2000 server supports 4GB of memory. My
> hardware supports two processors. If I license per
> Processor method and install two processors and license
> two Standard editions will there be 2GB of memory per
> processor or 2GB for both processors?
> Thanks
>

MS SQL SP3a installation failure

Dear experts!
I have MS SQL 2000 on the PC running Windows 2000 Server.
The MDAC version is 2.8, the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\Co
nnectTo\DSQUERY (REG_SZ)is set to DBNETLIB
The key NtfsDisable8dot3NameCreation under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSys
tem\ is set to 0, the user's variables TMP and TEMP are
set to c:\temp
The SP3a still fails while installation with the following
error messages:
"setup was unable to validate the password" and "setup was
unable to verify the state of the server for an upgrade"
If you know the solution please help to resolve the
problem.
Regards,
Elena.Refer to:
http://support.microsoft.com/default.aspx?scid=kb;en-us;814844
And here is a similar workaround applied to SP2
http://support.microsoft.com/default.aspx?scid=kb;en-us;328290
--
- Anith
( Please reply to newsgroups only )|||All the requirements listed in those articles have been
already met. But it does not work
Regards,
Elena.

ms sql server response is slow

Hi ,
i have ms access client program connecting to sql server 2000 wif sp3a
running on windows 2000 server
the user is complaining that the response from the client program is slow
i have check the current activity and there's no much user connected and
there's no lock/blocking process
where could i check further to determine the cause ?
tks & rdgs
You have only begun to scrape the surface of your issue.
There is a lot more that needs to be known to pinpoint anything.
1. Is MS Access using ADO to connect, or is it using the older DAO libraries
to connect?
2. If you are calling a stored procedure, is that individual sproc slow?
Are the tables indexed correctly?
You have to understand where the issue is with the user, and observe exactly
what they are doing - maybe it is the "way" they are doing the operation?
Trace it from their point of view, backwards through the various layers down
to the database. It may be something in the MS Access VBA code that is
causing the contention.
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:19F3E7F8-E9B6-4B93-8368-9B9FE46F813B@.microsoft.com...
> Hi ,
> i have ms access client program connecting to sql server 2000 wif sp3a
> running on windows 2000 server
> the user is complaining that the response from the client program is slow
> i have check the current activity and there's no much user connected and
> there's no lock/blocking process
> where could i check further to determine the cause ?
> tks & rdgs
|||Hi,
i am connected to the SQL server via odbc ver 3.52.
the problem started when the user got the connection failed error while
running the program with SQL State HYP000
i looked into the articles for theis connection failed but it seems not
related in my case
rdgs
"news.microsoft.com" wrote:

> You have only begun to scrape the surface of your issue.
> There is a lot more that needs to be known to pinpoint anything.
> 1. Is MS Access using ADO to connect, or is it using the older DAO libraries
> to connect?
> 2. If you are calling a stored procedure, is that individual sproc slow?
> Are the tables indexed correctly?
> You have to understand where the issue is with the user, and observe exactly
> what they are doing - maybe it is the "way" they are doing the operation?
> Trace it from their point of view, backwards through the various layers down
> to the database. It may be something in the MS Access VBA code that is
> causing the contention.
>
> "maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
> news:19F3E7F8-E9B6-4B93-8368-9B9FE46F813B@.microsoft.com...
>
>
sql

ms sql server response is slow

Hi ,
i have ms access client program connecting to sql server 2000 wif sp3a
running on Windows 2000 server
the user is complaining that the response from the client program is slow
i have check the current activity and there's no much user connected and
there's no lock/blocking process
where could i check further to determine the cause ?
tks & rdgsYou have only begun to scrape the surface of your issue.
There is a lot more that needs to be known to pinpoint anything.
1. Is MS Access using ADO to connect, or is it using the older DAO libraries
to connect?
2. If you are calling a stored procedure, is that individual sproc slow?
Are the tables indexed correctly?
You have to understand where the issue is with the user, and observe exactly
what they are doing - maybe it is the "way" they are doing the operation?
Trace it from their point of view, backwards through the various layers down
to the database. It may be something in the MS Access VBA code that is
causing the contention.
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:19F3E7F8-E9B6-4B93-8368-9B9FE46F813B@.microsoft.com...
> Hi ,
> i have ms access client program connecting to sql server 2000 wif sp3a
> running on Windows 2000 server
> the user is complaining that the response from the client program is slow
> i have check the current activity and there's no much user connected and
> there's no lock/blocking process
> where could i check further to determine the cause ?
> tks & rdgs|||Hi,
i am connected to the SQL server via odbc ver 3.52.
the problem started when the user got the connection failed error while
running the program with SQL State HYP000
i looked into the articles for theis connection failed but it seems not
related in my case
rdgs
"news.microsoft.com" wrote:

> You have only begun to scrape the surface of your issue.
> There is a lot more that needs to be known to pinpoint anything.
> 1. Is MS Access using ADO to connect, or is it using the older DAO librari
es
> to connect?
> 2. If you are calling a stored procedure, is that individual sproc slow?
> Are the tables indexed correctly?
> You have to understand where the issue is with the user, and observe exact
ly
> what they are doing - maybe it is the "way" they are doing the operation?
> Trace it from their point of view, backwards through the various layers do
wn
> to the database. It may be something in the MS Access VBA code that is
> causing the contention.
>
> "maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
> news:19F3E7F8-E9B6-4B93-8368-9B9FE46F813B@.microsoft.com...
>
>

ms sql server response is slow

Hi ,
i have ms access client program connecting to sql server 2000 wif sp3a
running on windows 2000 server
the user is complaining that the response from the client program is slow
i have check the current activity and there's no much user connected and
there's no lock/blocking process
where could i check further to determine the cause ?
tks & rdgsYou have only begun to scrape the surface of your issue.
There is a lot more that needs to be known to pinpoint anything.
1. Is MS Access using ADO to connect, or is it using the older DAO libraries
to connect?
2. If you are calling a stored procedure, is that individual sproc slow?
Are the tables indexed correctly?
You have to understand where the issue is with the user, and observe exactly
what they are doing - maybe it is the "way" they are doing the operation?
Trace it from their point of view, backwards through the various layers down
to the database. It may be something in the MS Access VBA code that is
causing the contention.
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:19F3E7F8-E9B6-4B93-8368-9B9FE46F813B@.microsoft.com...
> Hi ,
> i have ms access client program connecting to sql server 2000 wif sp3a
> running on windows 2000 server
> the user is complaining that the response from the client program is slow
> i have check the current activity and there's no much user connected and
> there's no lock/blocking process
> where could i check further to determine the cause ?
> tks & rdgs|||Hi,
i am connected to the SQL server via odbc ver 3.52.
the problem started when the user got the connection failed error while
running the program with SQL State HYP000
i looked into the articles for theis connection failed but it seems not
related in my case
rdgs
"news.microsoft.com" wrote:
> You have only begun to scrape the surface of your issue.
> There is a lot more that needs to be known to pinpoint anything.
> 1. Is MS Access using ADO to connect, or is it using the older DAO libraries
> to connect?
> 2. If you are calling a stored procedure, is that individual sproc slow?
> Are the tables indexed correctly?
> You have to understand where the issue is with the user, and observe exactly
> what they are doing - maybe it is the "way" they are doing the operation?
> Trace it from their point of view, backwards through the various layers down
> to the database. It may be something in the MS Access VBA code that is
> causing the contention.
>
> "maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
> news:19F3E7F8-E9B6-4B93-8368-9B9FE46F813B@.microsoft.com...
> > Hi ,
> >
> > i have ms access client program connecting to sql server 2000 wif sp3a
> > running on windows 2000 server
> >
> > the user is complaining that the response from the client program is slow
> >
> > i have check the current activity and there's no much user connected and
> > there's no lock/blocking process
> >
> > where could i check further to determine the cause ?
> >
> > tks & rdgs
>
>

MS SQL server login failed

I have MS SQL server desktop version installed localy and I have been using
it till last time I had to change my windows XP password. After that I could
not start service and I am getting an error message: "The service did not
start due to a logon failure", and "An error 1069 - The service did not start
due to a logon failure) occured while perfrorming this service operation on
the MSSQLServer service".
I have installed MS SQL server and configured to use Windows authentication,
and it worked in the past. Few months ago I have downloaded windows updates
and since then whenever I change windows password I have problem logging in
MS SQL.
Is there a way to fix that problem without reinstalling MS SQL?
DjL
It sounds like you may be running the service using your
Windows login. You can check from Services applet in the
Administrative Tools. Check the Logon tab for the
MSSQLSERVER service to see what login is being used.
If you are using your login, you need to change the password
for the MSSQLSERVER service also whenever you change your
Windows password.
-Sue
On Mon, 18 Sep 2006 07:44:02 -0700, Djordje Lekovic
<DjordjeLekovic@.discussions.microsoft.com> wrote:

>I have MS SQL server desktop version installed localy and I have been using
>it till last time I had to change my windows XP password. After that I could
>not start service and I am getting an error message: "The service did not
>start due to a logon failure", and "An error 1069 - The service did not start
>due to a logon failure) occured while perfrorming this service operation on
>the MSSQLServer service".
>I have installed MS SQL server and configured to use Windows authentication,
>and it worked in the past. Few months ago I have downloaded windows updates
>and since then whenever I change windows password I have problem logging in
>MS SQL.
>Is there a way to fix that problem without reinstalling MS SQL?
|||Thx It worked.
DjL
"Sue Hoegemeier" wrote:

> It sounds like you may be running the service using your
> Windows login. You can check from Services applet in the
> Administrative Tools. Check the Logon tab for the
> MSSQLSERVER service to see what login is being used.
> If you are using your login, you need to change the password
> for the MSSQLSERVER service also whenever you change your
> Windows password.
> -Sue
> On Mon, 18 Sep 2006 07:44:02 -0700, Djordje Lekovic
> <DjordjeLekovic@.discussions.microsoft.com> wrote:
>
>

MS SQL server login failed

I have MS SQL server desktop version installed localy and I have been using
it till last time I had to change my Windows XP password. After that I could
not start service and I am getting an error message: "The service did not
start due to a logon failure", and "An error 1069 - The service did not star
t
due to a logon failure) occured while perfrorming this service operation on
the MSSQLServer service".
I have installed MS SQL server and configured to use Windows authentication,
and it worked in the past. Few months ago I have downloaded windows updates
and since then whenever I change windows password I have problem logging in
MS SQL.
Is there a way to fix that problem without reinstalling MS SQL?
DjLIt sounds like you may be running the service using your
Windows login. You can check from Services applet in the
Administrative Tools. Check the Logon tab for the
MSSQLSERVER service to see what login is being used.
If you are using your login, you need to change the password
for the MSSQLSERVER service also whenever you change your
Windows password.
-Sue
On Mon, 18 Sep 2006 07:44:02 -0700, Djordje Lekovic
<DjordjeLekovic@.discussions.microsoft.com> wrote:

>I have MS SQL server desktop version installed localy and I have been using
>it till last time I had to change my Windows XP password. After that I coul
d
>not start service and I am getting an error message: "The service did not
>start due to a logon failure", and "An error 1069 - The service did not sta
rt
>due to a logon failure) occured while perfrorming this service operation on
>the MSSQLServer service".
>I have installed MS SQL server and configured to use Windows authentication
,
>and it worked in the past. Few months ago I have downloaded windows updates
>and since then whenever I change windows password I have problem logging in
>MS SQL.
>Is there a way to fix that problem without reinstalling MS SQL?|||Thx It worked.
DjL
"Sue Hoegemeier" wrote:

> It sounds like you may be running the service using your
> Windows login. You can check from Services applet in the
> Administrative Tools. Check the Logon tab for the
> MSSQLSERVER service to see what login is being used.
> If you are using your login, you need to change the password
> for the MSSQLSERVER service also whenever you change your
> Windows password.
> -Sue
> On Mon, 18 Sep 2006 07:44:02 -0700, Djordje Lekovic
> <DjordjeLekovic@.discussions.microsoft.com> wrote:
>
>sql

MS Sql Server and Windows 2000/XP

Hi, I have a problem.

I have two computers (clients), one with Windows 2000 and second with
Windows XP. And a third computer (server) with a Windows 2000 and MS Sql
Server 2000.

I have a TABLE with two rows: 'row' and 'row ' (space).

And SQL: 'select * from TABLE where row = 'row'

If I run this SQL on computer with Windows 2000 it works ok (return only one
row: 'row').
If I run this SQL on computer with Windows XP it works really strange
(return two rows: 'row' and 'row ' ) - it can't see this spaces.

Is there differences between MS Sql Server on W2000 and WXP?

Thanks for the help

Magdaslonk0 (slonk0_usun_to@.wp.pl) writes:
> I have two computers (clients), one with Windows 2000 and second with
> Windows XP. And a third computer (server) with a Windows 2000 and MS Sql
> Server 2000.
> I have a TABLE with two rows: 'row' and 'row ' (space).
> And SQL: 'select * from TABLE where row = 'row'
> If I run this SQL on computer with Windows 2000 it works ok (return only
> one row: 'row').
> If I run this SQL on computer with Windows XP it works really strange
> (return two rows: 'row' and 'row ' ) - it can't see this spaces.
> Is there differences between MS Sql Server on W2000 and WXP?

No, there isn't. There are however settings that you can change with
the SET command that may affect this. However, I am at loss to see
how you ever could get only one row back. You should always get two
back, because SQL does not care about trailing spaces when comparing.

Could you post a repro which demonstrates the problem? Such a repro
would have to create the table, insert the data, and then select.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||> how you ever could get only one row back. You should always get two
> back, because SQL does not care about trailing spaces when comparing.

Sorry, it was my mistake. You are right, SQL does not care about trailing
spaces when comparing.

Thanks for your help.
Magda

MS SQL Server 7.0 SP4 on Windows 2003 Server.

My regards for all on this NG!

My client need to use Windows 2003 Server, but it have some databases
and systems that use SQLServer 7.0
I need to know if MS SQL Server 7.0 can be instaled and if will run
with no problems into Windows 2003 Server.

Thanks a lot!!

LucioLucio Chiessi [VORio] (lucio@.vorio.eti.br) writes:
> My regards for all on this NG!
> My client need to use Windows 2003 Server, but it have some databases
> and systems that use SQLServer 7.0
> I need to know if MS SQL Server 7.0 can be instaled and if will run
> with no problems into Windows 2003 Server.

Microsoft does not support SQL 7.0 on Windows 2003. See further
http://support.microsoft.com/defaul...kb;en-us;810391.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thanks a lot for your response.
We are upgrading to MSDE2K and working fine.

Best Regards...|||Lucio Chiessi [VORio] (lucio@.vorio.eti.br) writes:
> Thanks a lot for your response.
> We are upgrading to MSDE2K and working fine.

Be sure to apply SP3, as this is required for Windows 2003.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

MS SQL Server 2005 64 bit CTP:[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist o

I am facing a problem with SQL Server 2005 64-bit CTP June 2005 on Windows 2003 64 Bit.

When i try to connect to the SQL Server Instance using any of Windows/SQL Server Authentication from My Application using SQLOLEDB interfaces (From Win32 Code) it is not able to connect and throws following error:

"[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."

When in the same code I use SQL Native Client (SQLNCLI), it is able to Create and Initialize the interfaces.

When i tried to research on this issue, i found out in Books Online SQL Server 2005 CTP June 2005. That this release only supports SQLNCLI and MDAC support has been removed for this release on 64 bit Windows.

The article says:
"SQL Native Client (SNAC) is available on the 64-bit platform. MDAC has been removed for this release."

Reference:
Books Online Microsoft SQL Server 2005 CTP June 2005
See Topic: "Differences Between 32-bit and 64-bit Editions of SQL Server 2005"

(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/e0556daa-19cb-4c08-af02-f542641365a5.htm)

Please let me know if any of you have similar problem. Is there any solution to this other than using SQLNCLI.

I did have similar issue that could not register several Yukon servers from one big brother server. After a little research, solution to the issue was Windows 2003 SP1.

Now, I am facing another issue which is deal with MDAC in 64 bit environment. I've got Win 2003 SP1 64bit and Yukon April CTP i64. One of developer trying to deal with distribute query against to an excel file, it returns an error

"The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered. "

I looked around and realized that we don't have much ODBC driver available from that 64 bit box. Only available drivers are SQL Native Client and SQL server.

I ran Component checker and it found MDAC2.8 SP2. I also tried to install Jet40 SP8 64 bit, but it say no install needed because there is a newer verion found on system. When I try to create a new data source, I don't have much selections but only two.

As you stated that we don't have much control on MDAC nor Jet40 at this stage. And I've been look for a workaround but no luck yet last two days.

I am keep looking and will post here to imform you if I find some thing.

Thanks
Sunny

|||Hi, Deepak,

Thank you for reporting the problem. Can you tell us:

- is your SQL Server 2005 a default instance or a named instance?
- How do you specify the server in your connection string (the server name, ".", "(local)", etc.)?
- What protocols are enabled on your SQL Server 2005 (TCP/IP, Named Pipes, Shared Memory)?

Thank you,
Peter|||

iam facing this error message kindly assit

Thank you