When you face this situation, we can resolve it in three steps
1) Open cmd and type in
sqlplus "/ as sysdba"
2)type there, alter user system account unlock;
3)alter user system identified by newpassword;
Thats it done.
Now you can open sqlpls and type system as username and password with your newpassword.
--------------------------------------------------------------------------------------------------
Sid already exists
Uninstall all Oracle components using the Oracle Universal Installer (OUI).
* Run regedit.exe and delete the HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE key. This contains registry entires for all Oracle products.
* Delete any references to Oracle services left behind in the following part of the registry: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Ora*
It should be pretty obvious which ones relate to Oracle. * Reboot your machine.
* Delete the "C:\Oracle" directory, or whatever directory is your ORACLE_BASE.
* Delete the "C:\Program Files\Oracle" directory.
* Empty the contents of your "c:\temp" directory.
* Empty your recycle bin.
--------------------------------------------------------------------------------------------------
IIS Authorization cannot verify access to path
1- Open IIS 7.0
2- Select Default Web Site and Right-Click on it
3- Select Add Application... or Add Virtual Directory...
4- Select Connect as..
5- Change Path credentials: from Application user (pass-through authentication) to Specific user:
6- Add the admin user of the system and password
----------------------------------------------------------------------------------------------------
Problem while setting up IIS on Cognos
HTTP Error 404.3 - Not Found
Description: The page you are requesting cannot be served because of
the Multipurpose Internet Mail Extensions (MIME) map policy that is
configured on the Web server. The page you requested has a file name
extension that is not recognized, and is not allowed.
Error Code: 0x80070032
Notification: ExecuteRequestHandler
Module: StaticFileModule
Requested URL: http://localhost:80/ets/bob.asp
Physical Path: C:\inetpub\wwwroot\ets\bob.asp
Logon User: Anonymous
Logon Method: Anonymous
Handler: StaticFile
Most likely causes:
It is possible that a handler mapping is missing. By default, the
static file handler processes all content.
The feature you are trying to use may not be installed.
The appropriate MIME map is not enabled for the Web site or
application. (Warning: Do not create a MIME map for content that users
should not download, such as .ASPX pages or .config files.)
What you can try:
In system.webServer/handlers:
Ensure that the expected handler for the current page is mapped.
Pay careful attention to preconditions (e.g. runtimeVersion,
pipelineMode, bitness) and compare them to the settings for your
application pool.
Pay careful attention to typographical errors in the expected handler
line.
Please verify that the feature you are trying to use is installed.
Verify that the MIME map is enabled or add the MIME map for the Web
site using the command-line tool appcmd.exe.
Open a command prompt and change directory to %windir%
\system32\inetsrv.
To set a MIME type, use the following syntax: appcmd set config /
section:staticContent /+[fileExtension='string',mimeType='string']
The variable fileExtension string is the file name extension and the
variable mimeType string is the file type description.
For example, to add a MIME map for a file which has the extension
".xyz", type the following at the command prompt, and then press
Enter:
appcmd set config /section:staticContent /+
[fileExtension='.xyz',mimeType='text/plain']
Warning: Ensure that this MIME mapping is needed for your Web server
before adding it to the list. Configuration files such as .CONFIG or
dynamic scripting pages such as .ASP or .ASPX, should not be
downloaded directly and should always be processed through a handler.
Other files such as database files or those used to store
configuration, like .XML or .MDF, are sometimes used to store
configuration information. Determine if clients can download these
file types before enabling them.
Create a tracing rule to track failed requests for this HTTP status
code. For more information about creating a tracing rule for failed
requests, click here.
More Information... This error occurs when the file extension of the
requested URL is for a MIME type that is not configured on the server.
You can add a MIME type for the file extension for files that are not
dynamic scripting pages, database, or configuration files. Process
those file types using a handler. You should not allows direct
downloads of dynamic scripting pages, database or configuration
files.
Resolution is to check whether CGI AND ISAPI extensions are enabled or not. Also check ASP and ASPX extension are checked.
To do that, go to control panel ->programs and features ->turn windows on or off and look for them.
