January 28, 2013

Error:Foreign Key constraints using Visual Studio with SQL Server Database

when you try to save dbo.Table2 after entry in Table2 it will show ERROR given below:

{
'Table1' table saved successfully
'Table2' table
- Unable to create relationship 'FK_Table2_Table1'.  
The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "FK_Table2_Table1". The conflict occurred in database "~\FOREIGNKEY\APP_DATA\DATABASE.MDF", table "dbo.Table1", column 'Id'.
}

Solution:
press ctrl+s and save dbo.Table2 first then do the data Entry in Table 2.
If you do entry in Table2 without saving it. then it will not follow Foreign Key constraints.

Error: Starting Tomcat v6.0 server at localhost has encountered a problem in eclipse

Problem:
Port 8080 required by Tomcat v6.0 Server at localhost is already in use. The server may already be running in another process, or a system process may be using the port. To start this server you will need to stop the other process or change the port number(s).

Solution:
If Port 8080 is already in use then use another port in place of port 8080.
Double click on Tomcat Server at localhost
 
Next Screen is following and port in red circle is the port that is already in use.

We only need to change this port 8080 to any other valid port which is not in use by other process.

Screen after changing port 8080 to port 8081
Press Ctrl+s to Save the changes made by you and then right click over Tomcat Server and click start.

Error Project facet Java version 1.6 or 1.7 is not supported in eclipse

It can be that java 1.7 is not installed in your system then you can use java version that is already installed in your system.Following Steps could resolve this error by setting up current version in project facet

1: Right Click over your Project on Project Explorer and click on Properties.

2: Goto java build path->Libraries
 Check JRE System Library Jars and also check it is JDK 1.6 or 1.7

3: Goto Project Facet and select your current java version available.



click apply then ok

Please Comment Thanks to us if this topic is helpful :)

Error,account is locked,Warning you no longer connected to Oracle,Problem when connecting to HR account in Oracle database

Following are the Steps that how we can unlock any Database User Account(eg. HR).
Before Unlocking any user account that user must be in the Database and must be Locked and to unlock that user you need DBA(Database Administrator) Privileges that's why I firstly connected as SYSDBA.


Press win+R( For Run) and type cmd then ok.then you need to write SQLPLUS/NOLOG as shown below to reach SQL Command Line.
OR
you can directly go to SQL Command Line
Start-> All programs-> Oracle 10g Express Edition -> Run SQL Command Line
Why we need to Unlock HR User:
When you try to work(eg. create table) with HR User First Time then you wouldn't be able to connect HR User because by default it remains Locked that's why we need to unlock it.

you can also see this error while connecting to HR Locked Account.
"Error,account is locked,Warning, you no longer connected to Oracle"
 C:\>SQLPLUS/NOLOG  
 SQL>CONN/AS SYSDBA  
 connected  
 SQL>CONN HR/HR  
 Error,account is locked  
 warning,you no longer connected to oracle  
 SQL>CONN/AS SYSDBA  
 connected  
 SQL>ALTER USER HR IDENTIFIED BY HR;  
 user altered  
 SQL>ALTER USER HR ACCOUNT UNLOCK;  
 user altered  
 SQL>ALTER USER HR IDENIFIED BY HR ACCOUNT UNLOCK;  
 user altered  
 SQL>CONN HR/HR  
 connected    

Microsoft JScript runtime error: Out of stack space



when you see this error then please check again your java script code because this is a javascript error, and it's usually happens when an recursive method called. 
That caused JavaScript to perform the unwanted Recursion. 

The stack is a working area of memory that grows and shrinks dynamically with the demands of your executing program. Its limits have been exceeded.


To correct this error(for Visual Basic)

  1. Check that procedures are not nested too deeply.
  2. Make sure recursive procedures terminate properly.
  3. If local variables require more local variable space than is available, try declaring some variables at the module level. You can also declare all variables in the procedure static by preceding the Property, Sub, or Function keyword with Static. Or you can use the Static statement to declare individual static variables within procedures.
  4. Redefine some of your fixed-length strings as variable-length strings, as fixed-length strings use more stack space than variable-length strings. You can also define the string at module level where it requires no stack space.
  5. Check the number of nested DoEvents function calls, by using the Calls dialog box to view which procedures are active on the stack.
  6. Make sure you did not cause an "event cascade" by triggering an event that calls an event procedure already on the stack. An event cascade is similar to an unterminated recursive procedure call, but it is less obvious, since the call is made by Visual Basic rather than an explicit call in the code. Use the Calls dialog box to view which procedures are active on the stack.

Disclaimer

We shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its response or damage to your system. We do not guarantee that the integrity or security of this communication has been maintained or that this communication is free of viruses, interceptions or interferences. Anyone communicating with us by email accepts the risks involved and their consequences. We accept no liability for any damage caused by any virus transmitted by this site.