Common Database Problems

I. About Oracle If the deletion is not clean, try the following methods: 1. Choose "start"> "Settings"> "Control Panel"> "Administrative Tools"> "services" to stop all Oracle services. 2. Choose Start> program> Oracle> orahome81> Oracle Installation Products> universal installer to uninstall all Oracle products. 3. Run regedit and select HKEY_LOCAL_MACHINE/software/oracle, press del to delete the entry. 4. Run regedit, select HKEY_LOCAL_MACHINE/system/CurrentControlSet/services, and scroll through the list to delete all Oracle entries 5. From the desktop, startup (start) group, and program menu, delete all groups and icons related to Oracle 6. Restart 2. Solution iis5.1 by default, the website cannot be started, and the World Wide Web Hing service cannot start. Error 127 cannot find the specified program.Iis5.1 by default, the website cannot be started, and the World Wide Web Hing service cannot be started. Error 127 cannot find the specified program. After I reinstall IIS, the fault still exists. The result shows that the patch is installed. You can just delete the patch after January 1, July 10. This is the reason WindowsXP-KB939373-x86-CHS.exePatch. It seems to be a patch that prevents IIS from remotely executing code. It was just recently discovered that this problem occurred in a large area after July 10. I have encountered the same problem these two days. Solution: Go to control panel-Add/delete programs, click "display Update" at the top, find "Windows XP software update", and uninstall several patches after January 1, July 10, the World Wide Web Publishing Service can be started. (Premise: the folders starting with $ in the Windows directory of drive C are not deleted)
My problem has been solved now! III. This is forbidden when Alerter is started When IIS is started. The following three are started.
IIS Admin, World Wide Web Publishing, Remote Access Connection Manager 4. Stop the HTTP service of Oracle .
Click Start-> Program-> Oracle-orahome90-> Oracle HTTP Server-> stop the HTTP server supported by Apache 5, When you connect to SQL Server 2005, the default setting does not allow remote connection to SQL Server may cause this failure. (Provider: named pipeline provider, error: 40-unable to open the connection to SQL Server

The preceding error occurs in two cases: one is when SQL Server 2005 is enabled, and the other is when the application connects to SQL Server 2005. we have summarized the following reasons:

1. The database engine is not started.

There are two startup methods:

(1) Start-> Program-> Microsoft SQL Server 2005-> SQL Server 2005 peripheral application configurator. On the displayed page, click "peripheral application configurator for service connection ", on the displayed page, find the database engine and click "service". Check whether the service is started on the right side. If not, click "start" and make sure "Start type" is automatic, do not manually start the instance. Otherwise, the instance must be manually started the next time it is started;

(2) You can choose Start> program Microsoft SQL Server 2005> Configuration tool> SQL Server Configuration Manager, and select SQL Server (MSSQLServer) in SQL Server 2005 ), click "Start Service" in the toolbar to change the service status to start;

When using the above two methods, sometimes an error may occur during startup, and cannot be started, in this case, check whether the Via in SQL Server 2005 network configuration> MSSQLServer protocol is enabled in "SQL Server 2005 Configuration Manager". If yes, disable it. then, execute the preceding operation.

2. Whether remote connection is allowed during remote connection.

By default, SQL Server 2005 only supports local connections. you can manually enable remote connection. in the first method above, find the database engine, click "remote connection", and change "local connection only (l)" to "local connection and remote connection (r)" on the right )", select "use TCP/IP and named pipes (B) at the same time )".

3. For a remote connection, check whether the database connection statement is correct, the Logon account is correct, and the password is correct.

When I connect to a database in a LAN, it is necessary to have a problem because of the connection string. When one machine is connected to another machine in the LAN, set Server = IP address of another machine with database installed. I always encountered the above error when connecting to the database. After checking for a long time, I found that the IP address was not correctly transmitted to the connection string. In the past, I used a local connection, that is, 127.0.0.1, the input IP address is not passed to the connection string.

Note: When you select "server resource manager"> "Data Connection"> right-click and select "create SQL Server database", select "refresh" for the server name ", select the database with the same machine name (because many people may enable the SQL Server database in the LAN ). Right-click the machine name and choose my computer properties.