Could not execute read_settings query

Hi All,
I did localization of UI strings in Arabic and when I tried running Arabic InDesgin, it gave some error and InDesgin was closed.
First it gave an error message "The handle is invalid"
Again an error message "Could not execute read_settings query"
Then it opened the Visual Studio Just-In Time Debugger which displayed "An unhandled win32 exception occurred in InDesign.exe [2512]"
Do anybody have any idea about this error and how to resolve this error?
Thanks.

Here some suggestions:
If you don't have that yet, install the debug build and try there.
http://blogs.adobe.com/notesfrommnr/2005/08/heres_how_to_ge.html
Mention it is about the ME version, eventually procedures differ.
You should make a sense of all assert messages in the debug build, and eliminate them by fixing your bugs.
Get a Mac and retry there. The Microsoft debugger is notoriously too stupid to even recover stackframes. If the crash is within Windows, there is some server at Microsoft for symbol files, see MSDN for details how to add it to VS debug options.
Learn to read assembler, have at least a basic understanding of your debugger.
Narrow it down: Make a copy of your project. Step by step comment out features until the crash is gone.

Similar Messages

Org.hibernate.exception.GenericJDBCException: could not execute query

while executing sql statements with hibernate oracle this type of errors
org.hibernate.exception.GenericJDBCException: could not execute query
ava.sql.SQLException: ORA-01001: cursore non valido can any one suggest
a solution for this.
Thanks

This is likely due to a commit/rollback being executed after the statement has been executed but befofre the result set has been processed by the application. In TimesTen, unlike Oracle, commit/rollback closes all open cursors on the connection. This could be a case of using the wrong Hibernate dialect. Are you using a TimesTen dialect in Hibernate?
Chris

SQLGrammarException: could not execute query

Hello,
I created a table with the script belove in a Derby database and created Entity Class for that.
create table "BAHADIR"."User"
     "id" NUMERIC(5) not null primary key,
     "name" VARCHAR(25),
     "email" VARCHAR(100),
     "password" VARCHAR(25),
     "role" VARCHAR(25)
)In my controller class there's a method like that:
    public int getItemCount() {
        EntityManager em = getEntityManager();
        try{
            int count = ((Long) em.createQuery("select count(o) from User as o").getSingleResult()).intValue();
            return count;
        } finally {
            em.close();
    }When this method is called I get that exception stack:
HTTP Status 500 -
type Exception report
message
descriptionThe server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not execute query
root cause
javax.el.ELException: javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not execute query
root cause
javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not execute query
root cause
org.hibernate.exception.SQLGrammarException: could not execute query
root cause
java.sql.SQLSyntaxErrorException: Syntax error: Encountered "User" at line 1, column 42.
root cause
org.apache.derby.client.am.SqlException: Syntax error: Encountered "User" at line 1, column 42.
note The full stack traces of the exception and its root causes are available in the Sun Java System Application Server 9.1 logs.
Sun Java System Application Server 9.1
What does these mean? The IDE created the access method automatically, so it can not be wrong. So where's the error?
Thanks.

By fixing the HQL query that results in the query that is wrong. So step 1: trace down which HQL query is causing the misery. Step 2: turn on SQL logging to see which sql is generated for that HQL query. Step 3: figure out what is wrong. I can guess that there is something wrong with the annotations on an entity, like declaring something as nullable while it is in fact not according to the database schema. Another common culprit is using a name that is a reserved SQL keyword.
EDIT:
'from limit And the keyword name clash is the cause here. Limit is an SQL keyword in MySQL, so you can't use that as a table name.

A nested exception occurred. Could not execute the function

Hi Experts,
Post upgrade of SAP Portal from 7.0 to 7.31, and when we click any application related to visual composer it shows the below error.
and the default trace shows
#2.0 #2014 07 22 02:34:11:243#0-700#Error#visualComposer_NWBIKit_logger#
#EP-PIN-PRT#tc~epbc~prtc~core#C000A7EEAF63014200000002000019B9#11738650000000004#sap.com/com.sap.visualcomposer.BIKit#visualComposer_NWBIKit_logger#C921154#36##E220BC96117411E4C8F2000000B31E1A#519cf5b0118311e48b43000000b31e1a#519cf5b0118311e48b43000000b31e1a#0#Thread[HTTP Worker [@2079636611],5,Dedicated_Application_Thread]#Plain##
A nested exception occurredCould not execute the function
[EXCEPTION]
com.sapportals.connector.execution.ExecutionException: A nested exception occurred. Could not execute the function.
at com.sapportals.connectors.SAPCFConnector.SAPConnectorException.getNewExecutionLocalizedException(SAPConnectorException.java:193)
at com.sapportals.connectors.SAPCFConnector.execution.functions.SAPCFConnectorInteraction.execute(SAPCFConnectorInteraction.java:617)
at com.sap.portal.guimachine.bikit.query.bw.QueryViewFlatRfc.execute(QueryViewFlatRfc.java:209)
at com.sap.portal.guimachine.bikit.designtime.bw.BWResultsetProcessor$ExecuteHandler.execute(BWResultsetProcessor.java:399)
Please give us your valuable inputs to solve this.
Thanks in advace!!
Regards,
Preetha Balan

Hi Colin,
Sorry for the delay in response!!
Yes SAP gave patch VC70RUNTIME file to apply to get rid of this error.
Even asked us to follow the sap note
1532050 - Disabling error messages that pop up at runtime
Hope this helps you
Thanks,
Preetha Balan

SQL 2012 SP1 - How to determine a query that causes Error 8623 in SQL Log: The query processor ran out of internal resources and could not produce a query plan. This is a rare event...

We are getting multiple 8623 Errors in SQL Log while running Vendor's software.
How can you catch which Query causes the error?
I tried to catch it using SQL Profiler Trace but it doesn't show which Query/Sp is the one causing an error.
I also tried to use Extended Event session to catch it, but it doesn't create any output either.
Error:
The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that
reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error, contact Customer Support Services for more information.
Extended Event Session that I used;
CREATE EVENT SESSION
overly_complex_queries
ON SERVER
ADD EVENT sqlserver.error_reported
ACTION (sqlserver.sql_text, sqlserver.tsql_stack, sqlserver.database_id, sqlserver.username)
WHERE ([severity] = 16
AND [error_number] = 8623)
ADD TARGET package0.asynchronous_file_target
(SET filename = 'E:\SQLServer2012\MSSQL11.MSSQLSERVER\MSSQL\Log\XE\overly_complex_queries.xel' ,
metadatafile = 'E:\SQLServer2012\MSSQL11.MSSQLSERVER\MSSQL\Log\XE\overly_complex_queries.xem',
max_file_size = 10,
max_rollover_files = 5)
WITH (MAX_DISPATCH_LATENCY = 5SECONDS)
GO
-- Start the session
ALTER EVENT SESSION overly_complex_queries
ON SERVER STATE = START
GO
It creates only .xel file, but not .xem
Any help/advice is greatly appreciated

Hi VK_DBA,
According to your error message, about which query statement may fail with error message 8623, as other post, you can use trace flag 4102 & 4118 for overcoming this error. Another way is looking for queries with very long IN lists, a large number of
UNIONs, or a large number of nested sub-queries. These are the most common causes of this particular error message.
The error 8623 occurs when attempting to select records through a query with a large number of entries in the "IN" clause (> 10,000). For avoiding this error, I suggest that you could apply the latest Cumulative Updates media for SQL Server 2012 Service
Pack 1, then simplify the query. You may try divide and conquer approach to get part of the query working (as temp table) and then add extra joins / conditions. Or You could try to run the query using the hint option (force order), option (hash join), option
(merge join) with a plan guide.
For more information about error 8623, you can review the following article.
http://blogs.technet.com/b/mdegre/archive/2012/03/13/8623-the-query-processor-ran-out-of-internal-resources-and-could-not-produce-a-query-plan.aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

The process could not execute 'sp_repldone/sp_replcounters' error for Log Reader Agent and SQL Server Assertion 17066 & 3624 errors in SQL Logs

One of our SQL Server started creating SQLDUMP file and and on investigation I found the error longs are filled with Errors 3624 & 17066. There is transnational replication configured on one of the databases is the LogReader Agent is failing error "The
process could not execute 'sp_repldone/sp_replcounters' on XXXXX".
Not sure if both these Assertion & Logreader Agent errors are related. Before I remove and put the replication, I wanted to check if anyone has experienced the same issues or aware of what the cause.
***********Error messages from SQL Logs******
**Dump thread - spid = 0, EC = 0x0000000111534460
Message
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to
Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <logscan.cpp>, line=2123 Failed Assertion = 'UtilDbccIsInsideDbcc () || (m_ProxyLogMgr->GetPru ()->GetStartupState () < RecoveryUnit::Recovered)'. This error may be timing-related. If the error persists after rerunning
the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
Error: 17066, Severity: 16, State: 1.
External dump process return code 0x20000001.
External dump process returned no errors.
Thank you in advance.

You need to determine if this error is a transient one or a show stopper one.
It sounds like your log reader agent has crashed and can't continue.
If so your best bet is to call Microsoft CSS and open a support incident.
It also sounds like DBCC CHECKDB was running while the log reader agent crashed.
If you need to get up and running again run sp_replrestart, but then you might find that replicated commands are not picked up. You will need to run a validation to determine if you need to reinitialize the entire publication or a single article.
I have run into errors like this, but they tend to be transient, ie the log reader agent crashes, and on restart it works fine.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

Could not execute the job

Hi,
when i execute the job a a window appear with the massage" ERROR: could not execute the job .Error returned was 1
     MESSAGE is : Could not open command file...
And i can't find from where it comes any suggestion?

When today i execute the job i had this list of error
13860    15384    REP-100109        27/05/2014 08:22:10       |Session TF_SGFA
13860    15384    REP-100109        27/05/2014 08:22:10       Cannot save <History info> into the repository. Additional database information: <SQL submitted to ODBC data source
13860    15384    REP-100109        27/05/2014 08:22:10       <SIGSIRDDB01\SQLSIRDBD> resulted in error <[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for object
13860    15384    REP-100109        27/05/2014 08:22:10       'dbo.AL_HISTORY_INFO' in database 'DS_REP' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded
13860    15384    REP-100109        27/05/2014 08:22:10       files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files
13860    15384    REP-100109        27/05/2014 08:22:10       in the filegroup.>. The SQL submitted is <INSERT INTO "AL_HISTORY_INFO" ("OBJECT_KEY", "NAME", "VALUE", "NORM_NAME",
13860    15384    REP-100109        27/05/2014 08:22:10       "NORM_VALUE") VALUES (430, N'TRACE_LOG_INFO',
13860    15384    REP-100109        27/05/2014 08:22:10                N'F:\SAPDS/log/JobServDS/sigsirddb01_sqlsirdbd_ds_rep_dsuser/trace_05_27_2014_08_22_09_10__3a4327b0_92c8_4abe_ac24_96d49123242a.
13860    15384    REP-100109        27/05/2014 08:22:10       txt', N'TRACE_LOG_INFO',
13860    15384    REP-100109        27/05/2014 08:22:10                N'F:\SAPDS/LOG/JOBSERVDS/SIGSIRDDB01_SQLSIRDBD_DS_REP_DSUSER/TRACE_05_27_2014_08_22_09_10__3A4327B0_92C8_4ABE_AC24_96D49123242A.
13860    15384    REP-100109        27/05/2014 08:22:10       TXT') >.>.
13860    15384    REP-100112        27/05/2014 08:22:10       |Session TF_SGFA
13860    15384    REP-100112        27/05/2014 08:22:10       Cannot save <History info> for repository object <>. Additional database information: <Cannot save <History info> into the
13860    15384    REP-100112        27/05/2014 08:22:10       repository. Additional database information: <SQL submitted to ODBC data source <SIGSIRDDB01\SQLSIRDBD> resulted in error
13860    15384    REP-100112        27/05/2014 08:22:10       <[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for object 'dbo.AL_HISTORY_INFO' in database 'DS_REP'
13860    15384    REP-100112        27/05/2014 08:22:10       because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup,
13860    15384    REP-100112        27/05/2014 08:22:10       adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.>. The SQL submitted is
13860    15384    REP-100112        27/05/2014 08:22:10       <INSERT INTO "AL_HISTORY_INFO" ("OBJECT_KEY", "NAME", "VALUE", "NORM_NAME", "NORM_VALUE") VALUES (430, N'TRACE_LOG_INFO',
13860    15384    REP-100112        27/05/2014 08:22:10                N'F:\SAPDS/log/JobServDS/sigsirddb01_sqlsirdbd_ds_rep_dsuser/trace_05_27_2014_08_22_09_10__3a4327b0_92c8_4abe_ac24_96d49123242a.
13860    15384    REP-100112        27/05/2014 08:22:10       txt', N'TRACE_LOG_INFO',
13860    15384    REP-100112        27/05/2014 08:22:10                N'F:\SAPDS/LOG/JOBSERVDS/SIGSIRDDB01_SQLSIRDBD_DS_REP_DSUSER/TRACE_05_27_2014_08_22_09_10__3A4327B0_92C8_4ABE_AC24_96D49123242A.
13860    15384    REP-100112        27/05/2014 08:22:10       TXT') >.>.>.
13860    15384    REP-100112        27/05/2014 08:22:10       |Session TF_SGFA
13860    15384    REP-100112        27/05/2014 08:22:10       Cannot save <History info> for repository object <>. Additional database information: <Cannot save <History info> into the
13860    15384    REP-100112        27/05/2014 08:22:10       repository. Additional database information: <SQL submitted to ODBC data source <SIGSIRDDB01\SQLSIRDBD> resulted in error
13860    15384    REP-100112        27/05/2014 08:22:10       <[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for object 'dbo.AL_HISTORY_INFO' in database 'DS_REP'
13860    15384    REP-100112        27/05/2014 08:22:10       because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup,
13860    15384    REP-100112        27/05/2014 08:22:10       adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.>. The SQL submitted is
13860    15384    REP-100112        27/05/2014 08:22:10       <INSERT INTO "AL_HISTORY_INFO" ("OBJECT_KEY", "NAME", "VALUE", "NORM_NAME", "NORM_VALUE") VALUES (430, N'TRACE_LOG_INFO',
13860    15384    REP-100112        27/05/2014 08:22:10                N'F:\SAPDS/log/JobServDS/sigsirddb01_sqlsirdbd_ds_rep_dsuser/trace_05_27_2014_08_22_09_10__3a4327b0_92c8_4abe_ac24_96d49123242a.
13860    15384    REP-100112        27/05/2014 08:22:10       txt', N'TRACE_LOG_INFO',
13860    15384    REP-100112        27/05/2014 08:22:10                N'F:\SAPDS/LOG/JOBSERVDS/SIGSIRDDB01_SQLSIRDBD_DS_REP_DSUSER/TRACE_05_27_2014_08_22_09_10__3A4327B0_92C8_4ABE_AC24_96D49123242A.
13860    15384    REP-100112        27/05/2014 08:22:10       TXT') >.>.>.
and thank u.
Sincerly

SQL 2005 v9.0.2047 (SP1) - The query processor could not produce a query plan

Hi Everyone:
*Before* I actually call up Microsoft SQL Customer Support Services and ask them, I wanted to ping other people to see if you have ever ran into this exact error
"Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services."
I would have searched the forums myself, but at this moment in time, search is broken :(
If anyone has run into this error before, what conditions would exist that this could happen? That is, if I can sniff this out with suggestions from the community, I would be happy to do so.
It is an oddity because if I alter a couple subqueries in the where clause [ i.e., where tab.Col = (select val from tab2 where id='122') ]to not have subqueries [hand coded values], then the t-sql result is fine. It's not as if subqueries are oddities... I've used them when appropriate.
fwiw - Not a newbie t-sql guy. ISV working almost daily with t-sql since MS SQL 2000. I have never seen this message before...at least I don't recall ever seeing it.
Thanks in advance for other suggested examination paths.

This code also produces the error... the text is from an incident a while ago that I reported to microsoft.
--I just found a way to break the query engine. Looks like the SQL Server team missed something. I was generating phony data for test cases, by the way.
--Bad code:
DECLARE @t_Asset TABLE
(Asset_Id INT)
INSERT INTO @t_Asset (Asset_Id) VALUES (1)
INSERT INTO @t_Asset (Asset_Id) VALUES (2)
INSERT INTO @t_Asset (Asset_Id) VALUES (3)
DECLARE @Record_id INT
,@File_id NVARCHAR(MAX)
,@SKP_Cust_id NVARCHAR(MAX)
,@Unique_Barcode NVARCHAR(MAX)
SELECT @Record_Id = (SELECT TOP 1 Asset_Id FROM @t_Asset)
, @file_id = (SELECT LEFT(REPLACE(CAST(NEWID() AS NVARCHAR(50)), '-', ''), 10))
,@Unique_Barcode=(SELECT LEFT(REPLACE(CAST(NEWID() AS NVARCHAR(50)), '-', ''), 15))
go
--Msg 8624, Level 16, State 116, Line 12
--Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.
--Code that doesn’t fry the optimizing engine:
DECLARE @t_Asset TABLE
(Asset_Id INT)
INSERT INTO @t_Asset (Asset_Id) VALUES (1)
INSERT INTO @t_Asset (Asset_Id) VALUES (2)
INSERT INTO @t_Asset (Asset_Id) VALUES (3)
DECLARE @Record_id INT
,@File_id NVARCHAR(MAX)
,@SKP_Cust_id NVARCHAR(MAX)
,@Unique_Barcode NVARCHAR(MAX)
SELECT @Record_Id = (SELECT TOP 1 Asset_Id FROM @t_Asset)
SELECT @file_id = (SELECT LEFT(REPLACE(CAST(NEWID() AS NVARCHAR(50)), '-', ''), 10))
SELECT @Unique_Barcode=(SELECT LEFT(REPLACE(CAST(NEWID() AS NVARCHAR(50)), '-', ''), 15))

Log Reader Agent error "could not execute sp_replcmds' and causes stack dump

Publisher/Subscriber db: SQL 2008 R2, 2000 compatability mode
Distributor database is on separate server.
(note: There is another database on this instance that is running replication without error, it is not in compatibility mode)
After snapshot agent finishes, the log reader agent starts and fails immediately with this error in the Agent Job.
Then I get a SEV20 error and stack dump in the error logs.
Date  6/12/2014 3:12:26 PM
Log  Job History (SERVER\INSTANCE-DBNAME-43)
Step ID  2
Server  ######RT02
Job Name  SERVER\INSTANCE-DBNAME-43
Step Name  Run agent.
Duration  00:00:01
Sql Severity  0
Sql Message ID  0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted  0
Message
2014-06-12 20:12:26.302 Copyright (c) 2008 Microsoft Corporation
2014-06-12 20:12:26.302 Microsoft SQL Server Replication Agent: logread
2014-06-12 20:12:26.302
2014-06-12 20:12:26.302 The timestamps prepended to the output lines are expressed in terms of UTC time.
2014-06-12 20:12:26.302 User-specified agent parameter values:
   -Publisher SERVER\INSTANCE
   -PublisherDB DBNAME
   -Distributor ######RT02
   -DistributorSecurityMode 1
   -Continuous
   -XJOBID 0x8958DF32810C6849B28A037A8FF8DD92
   -XJOBNAME SERVER\INSTANCE-DBNAME-43
   -XSTEPID 2
   -XSUBSYSTEM LogReader
   -XSERVER SERVER\INSTANCE
   -XCMDLINE 0
   -XCancelEventHandle 0000000000000F98
   -XParentProcessHandle 0000000000000F34
2014-06-12 20:12:26.459 Parameter values obtained from agent profile:
   -pollinginterval 5000
   -historyverboselevel 1
   -logintimeout 15
   -querytimeout 1800
   -readbatchsize 500
   -readbatchsize 500000
2014-06-12 20:12:26.493 Status: 4096, code: 20024, text: 'Initializing'.
2014-06-12 20:12:26.493 The agent is running. Use Replication Monitor to view the details of this agent session.
2014-06-12 20:12:27.885 Status: 0, code: 20011, text: 'The process could not execute 'sp_replcmds' on 'SERVER\INSTANCE'.'.
2014-06-12 20:12:27.886 The process could not execute 'sp_replcmds' on 'SERVER\INSTANCE'.
2014-06-12 20:12:27.886 Status: 0, code: 21, text: 'Warning: Fatal error 3624 occurred at Jun 12 2014 3:12PM. Note the error and time, and contact your system administrator.'.
2014-06-12 20:12:27.886 Status: 0, code: 22037, text: 'The process could not execute 'sp_replcmds' on 'SERVER\INSTANCE'.'.
I've tried removing replication and setting it back up again, restarting SQL, and restarting the server itself.
Let me know if you need any more information to help troubleshoot. Thanks.
Please help, thanks.

Hi,
Enable Verbose logging and check the results.
Execute following commands: -Output C:\Temp\OUTPUTFILE.txt –Outputverboselevel 2.
Please refer following KB article for your reference -
http://support.microsoft.com/kb/q312292/
Thanks.
Tracy Cai
TechNet Community Support

Could not execute auto check for display colors using command /usr/

I am trying to Install Oracle 10g R2 on Solaris X86 32 bit
I am connecting to system from my windows vista laptop through putty... I get the following error...
$ ./runInstaller
Starting Oracle Universal Installer...
Checking installer requirements...
Checking operating system version: must be 5.10. Actual 5.10
Passed
Checking Temp space: must be greater than 250 MB. Actual 1214 MB Passed
Checking swap space: must be greater than 500 MB. Actual 1799 MB Passed
Checking monitor: must be configured to display at least 256 colors
>>> Could not execute auto check for display colors using command /usr/openw
Some requirement checks failed. You must fulfill these requirements before
continuing with the installation,at which time they will be rechecked.
Continue? (y/n) [n] n
User Selected: No
Exiting Oracle Universal Installer, log for this session can be found at /tmp/Or
I have done the following:-
# DISPLAY=192.168.1.133:0.0; export DISPLAY
# echo $DISPLAY
192.168.1.133:0.0
# xhost+
xhost+: not found
# xclock
xclock: not found
I know that I have to do the following:-
1. Install SUNWxwplt package ========> Is already Installed
2. Set DISPLAY variable
3. Execute xhost + on target (set in DISPLAY) computer
# pkginfo -i SUNWxwplt
system SUNWxwplt X Window System platform software
Some sites claim xming and some xwindows etc.... Plz give me a step by step instruction as how to overcome this..
bash-3.00# /usr/openwin/bin/xclock
Error: Can't open display:
bash-3.00# DISPLAY=192.168.1.133:0.0; export DISPLAY; echo DISPLAY
DISPLAY
bash-3.00# echo $DISPLAY
192.168.1.133:0.0
bash-3.00# /usr/openwin/bin/xclock
Error: Can't open display: 192.168.1.133:0.0
bash-3.00# pwd
bash-3.00# find . -name xhost
./usr/openwin/bin/xhost
^C
bash-3.00# /usr/openwin/bin/xhost +
/usr/openwin/bin/xhost: unable to open display "192.168.1.133:0.0"
bash-3.00#
# echo $PATH
/usr/sbin:/usr/bin
I have also gone through the below ... but was not of much help
Unable to execute runInstaller: Check if the DISPLAY variable is set
Plz help
Edited by: [email protected] on Feb 11, 2009 5:16 AM

bash-3.00# echo $SHELL
/sbin/sh
bash-3.00# echo $DISPLAY
bash-3.00# DISPLAY=192.168.1.133:0.0;export DISPLAY
bash-3.00# echo $DISPLAY
192.168.1.133:0.0
bash-3.00# /usr/openwin/bin/xclock
Error: Can't open display: 192.168.1.133:0.0
bash-3.00# man xclock
No manual entry for xclock.
bash-3.00# /usr/openwin/bin/xhost +
/usr/openwin/bin/xhost: unable to open display "192.168.1.133:0.0"
bash-3.00#

Could not execute view config service request. This usually happens when an invalid view config service request is made, or when a read only Oracle Endeca Server receives a view config service request. Error message: Error applying updates: Unsupported la

Hi,
I have some data loaded into the data-domain in Endeca 3.0. When I was creating views in studio I repeatedly get this message when I say save view:
Could not execute view config service request. This usually happens when an invalid view config service request is made, or when a read only Oracle Endeca Server receives a view config service request. Error message: Error applying updates: Unsupported language ${DEFAULT_LANGUAGE}
In the workspace.prm file I have set ${DEFAULT_LANGUAGE}=en
May I know why this happening and a remedy for it. Appreciate you help.

Hi,
I have some data loaded into the data-domain in Endeca 3.0. When I was creating views in studio I repeatedly get this message when I say save view:
Could not execute view config service request. This usually happens when an invalid view config service request is made, or when a read only Oracle Endeca Server receives a view config service request. Error message: Error applying updates: Unsupported language ${DEFAULT_LANGUAGE}
In the workspace.prm file I have set ${DEFAULT_LANGUAGE}=en
May I know why this happening and a remedy for it. Appreciate you help.

Could not execute command "getState" for server server01 using nodemanager

Hi,
I have built a weblogic 9.1 env with 2 managed servers running on different boxes from the admin server.
I am having problems in starting the managed servers using the nodemanager. I get the following error message in the Admin server log:
<Error> <NodeManager> <BEA-300034> <Could not execute command "getState" for server "******" using the node manager. Reason: I/O error while reading domain directory: java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic91/common/nodemanager' invalid (domain salt file not found).>
I get the following message on the admin console:
For server ******, the Node Manager associated with machine ******-machine is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager. No action will be performed.
I can start the managed server using the "startMangedWeblogic.sh" without any issues.
Any help on this would be greatly appreciated.
Thanks

one more thing to add:
I get the following error in the Managed server log:
<I/O error while reading domain directory: java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic91/common/nodemanager' invalid (domain salt file not found)>
java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic91/common/nodemanager' invalid (domain salt file not found)
at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:74)
at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:46)
at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:239)
at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:170)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:104)
at weblogic.nodemanager.server.Handler.run(Handler.java:64)
at java.lang.Thread.run(Thread.java:595)

SCE (Error: Could not execute com.sap.sec.kbmt.createtable : )

Hi,
we are working on Configurable Material in ECC 6.0( SP010 and wanted to transfer into CRM7.0.
Knowledge base object has been created and its consistent O.K.
When i am trying install SCE Database Scheme ,i am getting the Following error ( "Error: Could not execute com.sap.sec.kbmt.createtable : The system cannot find the file specified").
we have created Database in MS-ACCESS in local system ( in my PC)
i can able to see version in CRM product master In T.Code: COMMPR01 ->Material-->Product no. Configurable tab .
Hence i request you all could you please help me in resolving my issue
Thanks and regards
Namitha Verma

Thanks

Error "The application could not execute the required function"

Hi All,
When I try to activate the DTP the following error occurs."the application could not execute the required function".
I was able to activate the DTP for the same DataSource 2 days back but now I am unable to activate .
Kindly suggest what could be the possible reason for the same.
Regards,
Santosh Mani

If you have transformation, check it is active. Is the object 0plant is acitve or not?
Ravi Thotahdri

Could Not execute auto Check for DISPLAY

Aloha!
I'am about to install 11g R2 on OLE5 and i set the display variable using "DISPLAY=<machine-name>:0.0; export DISPLAY". Upon installation " ./runInstaller " im having this error "Could not execute auto check for display..."
Can i undo the command mention above?
Thanks for the help.
hades

Aloha!
"2. echo $DISPLAY << what it returns?"
value is 0.0
Having the same error..or i can still continue with the installation?
[oracle@ole5 database]$ ./runInstaller
Starting Oracle Universal Installer...
Checking Temp space: must be greater than 80 MB. Actual 34646 MB Passed
Checking swap space: must be greater than 150 MB. Actual 5087 MB Passed
Checking monitor: must be configured to display at least 256 colors
>>> Could not execute auto check for display colors using command /usr/bin/xdpyinfo. Check if the DISPLAY variable is set. Failed <<<<
Some requirement checks failed. You must fulfill these requirements before
continuing with the installation,
Continue? (y/n) [n]
Thanks,
Hades

Could not execute read_settings query

Similar Messages

Maybe you are looking for