After running ccleaner application in my window server 2003 i dont know what happened and asked for log off. When i logged off and trying to log in,it returned back to log in screen. Then i restarted pc but it is showing 289 error dimm3/dimm4 multiple bit error detected. And after startup log in screen is not showing and screen remains blank. Please help me to resolve it.

are you using crack version for Windows 2003 SBS. if yes then restart ur server in safe mode, run the crack again. Be sure to have data backup before.

Your internet passwords are saved in the cookies. Install ccleaner. It is a free software and run this application to deleate cookies. Don't use the ccleaner as a registry cleaner. It is still under development. Use only for general disk cleanup. Ccleaner is an advanced disk cleanup software works better than the windows default disk cleanup application.

If you are running two versions of ASP.NET, you may get HTTP:/1.1 500 Internal Server Error when creating a new Web project or opening an existing Web project in Visual Studio.

This problem may occur when IIS is not sure what version of ASP.NET to use or where to locate ASP.NET files. One of the following solutions should fix the problem.

Solution 1.

1. Remove web.config file from inetpub/wwwroot directory
2. Go to IIS, Right click on Default web site / All tasks / Check server extensions and let it run
3. Reset IIS by right click on IIS or call iisreset from Run command

Solution 2.

1. Install ASP.NET again using the following command from your Run command: C:WINNTMicrosoft.NETFrameworkv1.1.4322aspnet_regiis.exe
   Make sure to change the windows folder and ASP.NET version folder with the version what you want to install
2. Reset IIS

Solution 3. Applies to Windows Server 2003
Note: This is a Microsoft KB article:

When you try to create a new Microsoft ASP.NET 1.1 application after you change the script mapping of the existing ASP.NET 1.1 Web application to ASP.NET 1.0 on a Microsoft Windows Server 2003-based computer, you may receive the following error message:
The Web server reported the following error when attempting to create or open the Web project located at the following URL: 'http://localhost/822319ev1'. 'HTTP/1.1 500 Internal Server Error'.
CAUSE
This issue occurs because Windows Server 2003 does not allow two versions of ASP.NET to run in the same application pool.
WORKAROUND
To work around the problem, do one of the following:
Restart the IIS before you create a new ASP.NET 1.1 application. At the command prompt type the following command: iisreset
OR -
Create an ASP.NET application in a separate application pool. Create the script-mapped application (ASP.NET 1.0) in a separate application pool -- for example, in the ScriptMapappPool application pool. Then, create a new ASP.NET 1.1 application in an application pool other than ScriptMapappPool. For more information about how to create an application pool, visit the following Microsoft Web site: Configuring Application Pools http://msdn.microsoft.com/en-us/library/1kdfe21k(VS.80).aspx

is the PC in question yours ?

this is more than likely a security related issue since the server you are attempting to log on to is Server 2003 and u still on 98... server 2003 and 98 dont like each other... see it as microsoft trying to bully you into upgrading your software...

and since you are not the network admin, ( i assume ) you wont be able to fix it, since you dont the rights, easiest solution :

remove the hard drive from the win98 PC and put it in another PC as a secondary or slave drive.. you will be able to access the data on the 98 hard drive via my computer..

if this sounds too daring or you have no idea what im talking about you need to urgently get hold of someone with some basic pc hardware knowledge and ask for help. While what ive suggested here is what i call "basic" ive also been working with PCs for 20+ years... so im not judging you :)

run ccleaner

www.ccleaner.com

install it and run it

and go to msconfig
startup

unselect the all programes

There are a number of issues might be affecting your PC's performance, some are dangerous while others not that serious. Learn why is it running slow and how to speed it up easily from: http://www.whyismypcsoslow.net/

Regards!

You need to go into administrative tools and look for group policy.

In the local computer policy
Computer Configuration
Windows Settings > security settings > Local policies > user rights assignment. In the right hand pane find the policy for "Allow log on locally" Set the user accounts for those users which are allowed to log on interactively on the server. Be careful you dont lock the administrator account out.
Use in conjunction with the "Deny logon locally policy" if you need to.
Hope this helps

clean out temp cleaner use ccleaner

A couple of questions for you...
1) What do you mean by 'crash'? How do you know its crashed?
2) Can you look in the Windows Event Viewer to see if there are any warning/error messages in the Application or System logs around the time of the starting or crashing of your web site on port 80? If so, anything that suggests the issue. If you don't understand the errors, try posting some of them here.
3) Is there any other web server running on port 80? If your running Internet Information Server, open the Internet Information Server Manager (mmc) console and click on "Web Sites" and it should list all the sites in the right pane. If you have anything 'running' on port 80, it will conflict.
4) Are you running Apache or any other web server on the system? If so, you're going to need to look at those configurations as well.
5) How about any other applications that might have a built in web server?

Let me know.

I?m assuming this is happening on a Windows machine. This is one of the really vague error messages that Microsoft give for an incredibly large number of problems. I typically see this on servers but have seen it occur on workstations. If you?re running XP, 2000 (server or Pro), or 2003: - Check and make sure your Remote Procedure Call Service is running. - There is an older vulnerability that tries to use a flaw in the RPC services. It is fixed if you copy of Windows is up to date so make sure it is. - Review your application log for any clues. If you need more assistance let us know your operating system, if it is fully patched and what is showing in your log file around the time you receive the error message.