TechNet Top Questions - August 9, 1999

Greetings, and welcome! For those of you checking in for the first time, my name is Devon and I'm here to provide detailed answers to popular questions submitted to TechNet via the answer forums and feedback alias. I choose questions that I believe are relevant to many of us working in the trenches to plan, deploy, maintain and support Microsoft® products.

This Week:

On This Page

What are the differences between SQL 7.0 Server and SQL Server 7.0 Enterprise Edition?

Preparing Servers for SQL Server Failover Support

Forgotten passwords – What to Do?

Why Can't I Share?

What are the differences between SQL 7.0 Server and SQL Server 7.0 Enterprise Edition?

Enterprise Edition is for customers who require the highest level of scalability and reliability. SQL Server 7.0 Enterprise Edition delivers Failover Clustering, the ability to partition OLAP Services (a.k.a. Data Warehousing) and the capability to utilize up to 32 processors and 64 GB of memory. SQL Server Enterprise Edition must run on Windows NT® Server 4.0 Enterprise Edition with Service Pack 4 or later.

As usual, the SQL Server 7.0 Books Online ("BOL") has some good information on this topic. As mentioned above, one of the benefits of SQL Server 7.0 Enterprise Edition is Failover Clustering. Query SQL Server 7.0 BOL by using the query "Using SQL Server Failover Support."

Here's a little tease:

Preparing Servers for SQL Server Failover Support

Building your server configuration to use SQL Server Failover Support can be done in two stages. The first stage is to prepare both servers for Microsoft SQL Server version 7.0 installation. This stage requires selecting servers from the HCL and installing identical versions of Windows NT 4.0 Enterprise Edition, Microsoft Internet Explorer version 4.01 Service Pack 1 or greater, and Windows NT SP 4 (or greater) on each server. After this is completed, you can install Clustering Service.

The SQL Server 7.0 Technical Product Overview is recommended reading for these long summer evenings.

Forgotten passwords – What to Do?

With so many passwords, PINs, keys, IDs, codes, and secret handshakes to remember these days, it's a wonder that we're able to get gas in the car. It's the same with our computers. All of this security is there to protect us from those that would do us harm, whether it's stealing your debit card PIN or your company's trade secrets.

Passwords and problems associated with them – such as forgetting what they are - have been around for ages. Microsoft is serious about maintaining the confidence of users' expectations about passwords - whether they protect a Word document, network logon, or access to a computer – as with screen savers. The problem is that people forget passwords. Sometimes they can be recovered or removed - other times they can't (like Word or Excel passwords.)

The logic is that if Microsoft made information for removing a password easily available (like in the Knowledge Base or the WWW) then what use would passwords be? So, the best advice is don't forget the password. In reality, sometime it may happen, and if it does, your best course of action is to contact Microsoft Technical Support.

Why Can't I Share?

Say you've got a brand new shiny laser printer dropped at your cubicle "door" and you would like to enable others in your group to print to it. Most of the time it would be pretty easy to do – you would connect the printer to your computer, "Add" the computer to your server or workstation, install the needed device drivers and share it. The process is basically the same on Windows 9x or Windows NT – with a couple of exceptions. With Windows NT you would grant access permissions to specific users or groups, as opposed to sharing a printer from a Windows 9x machine where you control access with the optional use of a password. With Windows 9x, you also need to make sure that File and Print sharing is activated in the Control Panel, Networks icon.

Sometimes, however, things don't work out as planned. One situation is that you could receive an error message that might not seem like it has anything to do with why you can't share your printer. Such is the case with an error when sharing a printer on Windows NT. One indication that all is not well is that the Server Service did not start and you see a System Error 1130. Sometimes you can get this error when you execute a NET USE command. Either way, the associated text to this error is

System Error 1130 has occurred.

Not enough server storage is available to process this command.

"Not enough server storage" is the term that can be confusing – is it disk space?

No, inadequate disk space is not the problem. Chances are that the cause is the size of the registry has exceeded the maximum size set in the virtual memory settings. The solution is addressed in Knowledge Base article #166840, "Err Msg: Not Enough Storage to Complete Operation".

Another possible culprit for getting the 1130 error typically occurs with computers that come from the original equipment manufacturer (OEM) with Windows NT and Service Pack 3 preinstalled. This problem can occur if Windows NT is installed and the latest service pack is installed before any network services are installed. Read the following article for more information.

15427: Server Service May Fail After Installing Network Card.

It is possible to receive an error message "Printer settings could not be saved" along with the 1130 error. The following Knowledge Base article addresses this.

234530: Unable to Change the Specified Driver for a Network Printer

Phew! That is it for now. Check out the new TechNet Top Questions on August 23.

Illustration by Elizabeth Anderson, MSN Staff