Shamil Salakhetdinov
shamil-users at mns.ru
Sun Aug 17 06:40:05 CDT 2003
John, Yes, I gave up - I spent two days hanging around it and tryng to find a workaround and I learned a lot of things about hardware jumpers, installation and backup and restore and the registry... It (W2K) starts but it takes ages before it allow me to work with it - I'd better reinstall it... I'm now planning my fresh install... Shamil ----- Original Message ----- From: "John Colby" <jcolby at colbyconsulting.com> To: "Discussion of Hardware and Software issues" <dba-tech at databaseadvisors.com> Sent: Saturday, August 16, 2003 8:30 PM Subject: RE: [dba-Tech] OT: W2K gurus your advice is needed (moved here fromAccessD)... > Shamil, > > I would HIGHLY recommend a fresh install of Win2K / SQL Server and the rest. > I am thinking that you may never the registry straightened out and may > therefore have small crazy problems for the rest of the computer's life. > > John W. Colby > www.colbyconsulting.com > > -----Original Message----- > From: dba-tech-bounces at databaseadvisors.com > [mailto:dba-tech-bounces at databaseadvisors.com]On Behalf Of Shamil > Salakhetdinov > Sent: Saturday, August 16, 2003 7:30 AM > To: AccesD - dba-Tech > Subject: [dba-Tech] OT: W2K gurus your advice is needed (moved here from > AccessD)... > > > Gentlemen & gentlewomen, > > and especially the greatest AccessD advisor Mr. Drew Wutka! > > I wanted to report here that subject problem is on its way to be solved. > Having got Drew's advice/hints I did some dirty registry hacking (what MS > advises in KB wasn't enough - I needed to manually edit another dozen of > registry entries) and voila' the W2K Server loads now and seems to work 80 > percent correct... > > But there are still some annoyning problems, which I wanted to ask your > advise here how to solve. > > Here is the first one - SQL Server Service doesn't want to start now: > > <<< > And error 1069 - (The service did not start due to a logon failure) occured > while performing this service operation on the MSSQLServer service) > >>> > > and > > <<< > A connection could not be estableshed to PARIS\SQLSVRONPARIS > > Reason: SQL Server does not exists or access denied. > ConnectionOpen (Connect())... > > Please verify SQL Server is running and check your SQL Server registration > properties (by right-clicking on the PARIS\SQLSVRONPARIS node) and try > again. > > in the system event log I see for Service Control Manager: > > Logon attempt with current password failed with the following error: > Logon failure: the user has not been granted the requested logon type at > this computer. > > The MSSQL$SQLSVRONPARIS service failed to start due to the following error: > The service did not start due to a logon failure. > >>> > > I probably should better reinstall SQL Server but maybe there exists a > quickier solution? > > Another question - is it possible to make a kind of repair install for W2K > Server ? - if this is possible where I can read about it? > > Reason: there are other messages, which are very cryptic for me to expect I > find how to solve the problems behind them - these are the messages from > different system logs: > > <<< > NetLogon: > Dynamic registration or deregistration of one or more DNS records failed > with the following error: > No DNS servers configured for local system. > >>> > <<< > MRxSmb: > The redirector was unable to initialize security context or query context > attributes. > >>> > <<< > DHCPServer: > The DHCP/BINL service has determined that it is not authorized to service > clients on this network for the Windows domain: DAISY.local. > >>> > > <<< > NTDS: General, Global Catalog > > The attempt to communicate with global catalog \\paris.DAISY.local failed > with the following status: > Could not find the domain controller for this domain. > The operation in progress might be unable to continue. The directory > service will use the locator to try find an available global catalog server > for the next operation that requires one. > The record data is the status code. > >>> > > <<< > NTDS: General, Global Catalog > Unable to establish connection with global catalog. > >>> > > <<< > UserEnv: > Windows cannot determine the user or computer name. Return value (1908). > >>> > > Despite all that error messages above W2K seems to work rather well and it > has some rather stronmg self-repairing facilities... > > TIA for any help, > Shamil > > P.S. This accident with my system was AFAIU because I installed the second > harddrive with jumpers set incorrectly. Because of that during boot-up W2K > Server used I: drive as its system drive but there was also C: drive present > with W2K server operation system installed on it - so it (W2K) somehow > managed to load in this configuration but on shutdown (or even during its > working) it MODIFIED registry by writing absolute paths starting from I: for > some services, data (including Active Directory) etc. .... > And I thought I made full backup before I started my stupid games with > hardware but I DIDN'T do backup of system information :( So the only > solution was to continue my crazy games - now with registry)... > It seems that it worked in general but there are still some problems as > above... > > As in any accident there exists a positive experience - I've never had > enough time to look that close on all existing Windows services, registry > entries etc. - I think I'm now quite experienced in all that and in > back-uping/restoring... > > ----- Original Message ----- > Shamil Salakhetdinov shamil at smsconsulting.spb.ru > Fri Aug 15 23:30:25 CDT 2003 > > Thanks a lot, Drew, this is what I was looking for! > > I will read and play with it and will try to apply it! > > I should have asked my question here yesterday! > > Many thanks, > Shamil > > > ----- Original Message ----- > From: "Drew Wutka" <DWUTKA at marlow.com> > To: "'Access Developers discussion and problem solving'" > <accessd at databaseadvisors.com> > Sent: Friday, August 15, 2003 10:07 PM > Subject: RE: [AccessD] OT: W2K gurus your advice is needed... > > > > Here ya go Shamil: > > http://support.microsoft.com/default.aspx?scid=kb;en-us;249321 > > > > Tell your system engineers that it might help if they took a look at MS's > KB > > once in a while! <evilgrin> > > > > Drew > > > > -----Original Message----- > > From: Shamil Salakhetdinov [mailto:shamil at smsconsulting.spb.ru] > > Sent: Friday, August 15, 2003 11:54 AM > > To: AccessD > > Subject: [AccessD] OT: W2K gurus your advice is needed... > > > > > > Hi All, > > > > Here is a tough one - at least the system engineers I know here can't > answer > > this question/help me: > > > > - as the result of my hardware upgrade and different (stupid) > manipulations > > I've got my system disk (W2K) getting I: as drive letter instead of C: > > during booting (all the other five disks are OK - D:, E:, F:, G:, H:)... > > > > Funny? Yes - as the result when I try to logon after booting it accepts > > password but then after some time instead of showing desktop icons etc. it > > shows "Saving your settings" dialog and returns to Logon dialog... > > > > I've found that system disk gets I: drive letter instead of C: by > connecting > > to the problematic PC from another computer and by using Disk Management > > system utility. I've also used Event viewer to see that W2K can't start > > system programs and services because it expects C:\..... as system > drive... > > (It's interesting that it works at all... - this W2K is a good > software....) > > > > MS probably never tested such a use case as I managed to create here!... > > > > Well, the question is how/and where can I set system drive letter back to > > C:. I tried to find something in registry but failed. Is that written in a > > system file? Which one? > > > > Of course I've backup and I can try to restore from it but maybe it's > > quicker to replace just one(?) file where physical<->logical disk > > correspondence is stored? (I've spent quite some time on all that - first > > thought was that this is MSBLAST but I run MSBLAST fix and it didn't find > > anything... ) > > > > Does anybody know how is this drive mapping system file called and is it > > possible to solve my task by just overwriting this file? (of course I will > > boot from another drive and use problematic drive as slave and use backup > > copy to overwrite system file keeping drives mappings)... > > > > TIA for any info, tips and tricks, > > I hope there are real NT gurus here, > > Shamil > > > > -- > > e-mail: shamil at smsconsulting.spb.ru > > Web: http://www.smsconsulting.spb.ru/shamil_s > > > > > > _______________________________________________ > dba-Tech mailing list > dba-Tech at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-tech > Website: http://www.databaseadvisors.com > > > > _______________________________________________ > dba-Tech mailing list > dba-Tech at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-tech > Website: http://www.databaseadvisors.com