Bootcamp not releasing services

My wife's Mini (early 2009, 2GB RAM, 120GB HDD) has developed a new problem: when she tries to switch from Windows XP Pro SP3 to Snow Leopard using the diamond shaped icon in the systray the desktop freezes (you can move the cursor but nothing else responds) and she has to crash the Mini and restart. When the computer restarts in Windows and the file error check is running (due to the crash) I see that whatever service I was running just before the reboot reports errors.
If I use the conventional Windows restart path and use the Alt (Option) key her system doesn't hang and I can boot to either the Windows or the Mac side; this is the workaround she is using now.
This leads me to suspect that the bootcamp running in the systray (which is version 3.0) is broken because it isn't releasing/shutting down services prior to restarting, so my question is:
Is it possible to repair bootcamp using the OSX disk, or should I update it to version 3.1, and in either case will the XP partition be hosed? (I read in other posts that Win XP 32bit doesn't get along too well with bootcamp version 3.1). She backs up religiously but I'd rather not go through the hassle of a reinstall.
BTW, abandoning Windows just is not an option, we can't afford to replace Photoshop.

Dear Ghaleb
You have to use a development for this solution
User Exit : QEVA0010 UD: Usage decision check
QEVA0006 Entry to usage decision transactions
Regards
Gajesh

Similar Messages

Enterprise Service publish in SR with "Not Released State".

Hi guys,
i need someone who can help me with this problem, please.
I've model an Enterprise Service in the ESR, then i´ve implement it in an Ecc 6.0 ( Generating the Proxy and inserting the business logic ).
Note : When i´m trying to generate de proxy the state of the Service Interface is "Not released", but i can´t change this status, but when i save and activate it no errors appear.
Then in the Service Registry i search this Service published, The crazy thing is that i can see it published in the SR but i can´t consume it in the Visual Composer because it not appears in the Service Registry search menu. I can only see the WS that i published manually without modeling it directly from the Ecc 6.0.
Regards,
Diego Rodriguez.

Hi
You can change this in the Enterprise Services repository. Please go to the Service Interface > Mark it editable > From the menu options on top, choose Properties > and one of the properties there is Status, which will be not released.
Mark it as released.
regards
Rathish

Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]

I'm using Oracle Linux 6u6. While I'm installing openstack ( 2 node set up) using packstack, I'm getting this error:
Applying 10.245.33.37_cinder.pp
10.245.33.37_keystone.pp:                         [ ERROR ]
Applying Puppet manifests                         [ ERROR ]
ERROR : Error appeared during Puppet run: 10.245.33.37_keystone.pp
Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
You will find full trace in log /var/tmp/packstack/20150327-100335-ltC8Ic/manifests/10.245.33.37_keystone.pp.log
Please check log file /var/tmp/packstack/20150327-100335-ltC8Ic/openstack-setup.log for more information
Additional information:
* A new answerfile was created in: /root/packstack-answers-20150327-100336.txt
* Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components.
* Did not create a cinder volume group, one already existed
* File /root/keystonerc_admin has been created on OpenStack client host 10.245.33.37. To use the command line tools you need to source the file.
* To access the OpenStack Dashboard browse to http://10.245.33.37/dashboard .
Please, find your login credentials stored in the keystonerc_admin in your home directory.
Packages:
[root@slcai461 ~]# rpm -qa|grep keystone
python-keystoneclient-0.9.0-5.el6.noarch
python-keystone-2014.1.3-2.el6.noarch
openstack-keystone-2014.1.3-2.el6.noarch
[root@slcai461 ~]# rpm -qa|grep packstack
openstack-packstack-puppet-2014.1.1-0.12.dev1068.0.4.el6.noarch
openstack-packstack-2014.1.1-0.12.dev1068.0.4.el6.noarch
Log :
[root@slcai461 ~]# cat /var/tmp/packstack/20150327-100335-ltC8Ic/manifests/10.245.33.37_keystone.pp.log
Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Warning: Scope(Class[Keystone]): The sql_connection parameter is deprecated, use database_connection instead.
Warning: Scope(Class[Keystone]): token_format parameter is deprecated. Use token_provider instead.
Warning: Scope(Class[Keystone::Endpoint]): The public_address parameter is deprecated, use public_url instead.
Warning: Scope(Class[Keystone::Endpoint]): The internal_address parameter is deprecated, use internal_url instead.
Warning: Scope(Class[Keystone::Endpoint]): The admin_address parameter is deprecated, use admin_url instead.
Warning: Scope(Class[Nova::Keystone::Auth]): The cinder parameter is deprecated and has no effect.
Notice: Compiled catalog for slcai461.us.oracle.com in environment production in 1.60 seconds
Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false.
   (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in `set_default')
Notice: /Stage[main]/Keystone/Keystone_config[DEFAULT/admin_token]/value: value changed '[old secret redacted]' to '[new secret redacted]'
Notice: /Stage[main]/Keystone/Keystone_config[database/connection]/value: value changed '[old secret redacted]' to '[new secret redacted]'
Notice: /Stage[main]/Keystone::Db::Sync/Exec[keystone-manage db_sync]: Triggered 'refresh' from 3 events
Notice: /Stage[main]/Keystone/Exec[keystone-manage pki_setup]: Triggered 'refresh' from 2 events
Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
Wrapped exception:
Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
Error: /Stage[main]/Keystone::Service/Service[keystone]/ensure: change from stopped to running failed: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
Notice: /Stage[main]/Keystone::Service/Service[keystone]: Triggered 'refresh' from 5 events
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova_ec2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova_ec2]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinderv2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinderv2]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[novav3]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[novav3]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[services]: Skipping because of failed dependencies
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_user[neutron]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_user[neutron]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_user[nova]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_user[nova]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_user[glance]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_user[glance]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_role[admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_role[admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_user_role[glance@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_user_role[glance@services]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Endpoint/Keystone_service[keystone]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Endpoint/Keystone_service[keystone]: Skipping because of failed dependencies
Error: Could not prefetch keystone_endpoint provider 'keystone': Execution of '/usr/bin/keystone --os-endpoint http://127.0.0.1:35357/v2.0/ endpoint-list' returned 1: An unexpected error prevented the server from fulfilling your request. (HTTP 500)
Notice: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[RegionOne/keystone]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[RegionOne/keystone]: Skipping because of failed dependencies
Notice: /Stage[main]/Main/Keystone_service[cinder_v2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Main/Keystone_service[cinder_v2]: Skipping because of failed dependencies
Notice: /Stage[main]/Main/Keystone_endpoint[RegionOne/cinder_v2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Main/Keystone_endpoint[RegionOne/cinder_v2]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/novav3]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/novav3]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinder]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinder]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinder]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinder]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_service[glance]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_service[glance]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_endpoint[RegionOne/glance]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_endpoint[RegionOne/glance]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_user_role[admin@admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_user_role[admin@admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_user[cinder]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_user[cinder]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova_ec2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova_ec2]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinderv2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinderv2]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova]: Skipping because of failed dependencies
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_user_role[neutron@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_user_role[neutron@services]: Skipping because of failed dependencies
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_endpoint[RegionOne/neutron]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_endpoint[RegionOne/neutron]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder@services]: Skipping because of failed dependencies
Notice: Finished catalog run in 3.10 seconds
Please let me know how to fix this.

This problem connected with proxy-setings.
As the first steps you should try:
       1. export system env variable:
http_proxy=http://www-proxy.ru.oracle.com:80
https_proxy=https://www-proxy.ru.oracle.com:80
no_proxy=127.0.0.1,localhost
and you can also export
    export OS_TENANT_NAME=admin
    export OS_USERNAME=admin
    export OS_PASSWORD=root
    export OS_AUTH_URL=http://<conntroller_IP>:5000/v2.0/
2. and than restart mysqld, if it is running, stop iptables and repeat installation process from beginning with the currently generated answer file
if we are exporting variable OS_PASSWORD, its value should be the same as value for CONFIG_KEYSTONE_ADMIN_PW in the currently generated answer file.
This OS_PASSWORD will be written by packstack in the /root/keystonerc_admin file and will be used as admin's password for login to Openstack dashboard.

[svn] 2692: Bug: BLZ-227 - When using JMS Destination, MessageClient and FlexClient not released from memory when the session times out .

Revision: 2692
Author: [email protected]
Date: 2008-07-31 13:05:35 -0700 (Thu, 31 Jul 2008)
Log Message:
Bug: BLZ-227 - When using JMS Destination, MessageClient and FlexClient not released from memory when the session times out.
QA: Yes
Doc: No
Checkintests: Pass
Details: Fixed a memory leak with JMS adapter. Also a minor tweak to QA build file to not to start the server if the server is already running.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-227
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/messaging/adapters/J MSAdapter.java
blazeds/branches/3.0.x/qa/build.xml

Revision: 2692
Author: [email protected]
Date: 2008-07-31 13:05:35 -0700 (Thu, 31 Jul 2008)
Log Message:
Bug: BLZ-227 - When using JMS Destination, MessageClient and FlexClient not released from memory when the session times out.
QA: Yes
Doc: No
Checkintests: Pass
Details: Fixed a memory leak with JMS adapter. Also a minor tweak to QA build file to not to start the server if the server is already running.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-227
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/messaging/adapters/J MSAdapter.java
blazeds/branches/3.0.x/qa/build.xml

SQL Server Memory Usage Peaks to 95% and its not releasing SQL 2012

We are currently running SQL 2012 64 bit, Lock Pages Enabled, 128 GB. We allocated Max Memory 112000, Min Memory to 0. We have a SQL Maintenace Job which backs up (Full Backup) of our server around 11PM at that time the SQL Server memory peaks to almost
96% even during full business hours we are constantly in the range of 56 to 60% but after 11PM within 10 minutes of the job it peaks to 95 or 96 Percentage and even after the job completes it's not releasing the memory back. I have to manually shut the sql
service and then restart at that time it comes back to normal.
Any suggestions/any help really appreciated.

Here are the details Memory is at 96% I still didn't restart...Please any help appreciated...The memory detals is for 24 hours I restarted the service around 11AM before I posted my previous message..
Memory Used by SqLServer: 119329
Locked Pages Used SQLServer : 105969
Total VAS in MB : 8388607
Process Physical Memory Low : 0
Process Virtual Memory Low : 0
Max Memory set to :112000
Out of 128 Memory Last 24 hours the memory usage in %
Percent Memory Used - Total Memory is 128.0 GB
Last 24 Hours
DATE / TIME
Memory Used
19-Dec-14
11:46 PM
96.24659602
20-Dec-14
12:46 AM
96.24578349
20-Dec-14
1:46 AM
96.25146739
20-Dec-14
2:46 AM
96.24345652
20-Dec-14
3:46 AM
96.27311834
20-Dec-14
4:46 AM
96.28947067
20-Dec-14
5:46 AM
96.18931325
20-Dec-14
6:46 AM
96.09323502
20-Dec-14
7:46 AM
96.07915497
20-Dec-14
8:46 AM
96.07906977
20-Dec-14
9:46 AM
96.0784111
20-Dec-14
10:46 AM
96.07415009
20-Dec-14
11:46 AM
26.03422141
20-Dec-14
12:46 PM
33.57474359
20-Dec-14
1:46 PM
39.466561
20-Dec-14
2:46 PM
41.85940742
20-Dec-14
3:46 PM
43.89071274
20-Dec-14
4:46 PM
45.80877368
20-Dec-14
5:46 PM
46.49493281
20-Dec-14
6:46 PM
46.68486468
20-Dec-14
7:46 PM
46.69701958
20-Dec-14
8:46 PM
46.69994736
20-Dec-14
9:46 PM
57.5012455
20-Dec-14
10:46 PM
96.25695419
I verified its a sqL job and still my memory is 95%
It peaeked at 10:46PM and here are the details of the SQL job which started at 10:30
Progress: 2014-12-20 22:30:04.39
Source: Check Database Integrity Task Executing query "USE [DATASTORE] ".: 50% complete End Progress Progress: 2014-12-20 22:43:06.10
Source: Check Database Integrity Task Executing query "DBCC CHECKDB(N'DATASTORE') WITH NO_INFOMSGS ".: 100% complete End Progress
Progress: 2014-12-20 22:43:06.11 Source: Check Database Integrity Task Executing query "USE [ETL_Proc] ".: 50% complete
End Progress Progress: 2014-12-20 22:46:52.56 Source: Check Database Integrity Task Executing query "DBCC CHECKDB(N'ETL_Proc')
WITH NO_INFOMSGS ".: 100% complete End Progress Progress: 2014-12-20 22:46:52.64 Source: Back Up Database Task
Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".: 20% complete End Progress
Progress: 2014-12-20 22:46:52.64 Source: Back Up Database Task Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".
: 40% complete End Progress Progress: 2014-12-20 22:46:52.64
Source: Back Up Database Task Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".: 60% complete
End Progress Progress: 2014-12-20 22:46:52.64 Source: Back Up Database Task
Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".: 80% complete End Progress
Progress: 2014-12-20 22:46:52.64 Source: Back Up Database Task
Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".: 100% complete End Progress
Progress: 2014-12-20 22:46:55.63 Source: Back Up Database Task
Executing query "BACKUP DATABASE [ReportServer] TO DISK = N'P:\SQL...".: 100% complete
End Progress Progress: 2014-12-20 22:46:56.55 Source: Back Up Database Task
Executing query "BACKUP DATABASE [ReportServerTempDB] TO DISK = N'...".: 100% complete End Progress Progress: 2014-12-20 22:46:57.35
Source: Back Up Database Task Executing query "BACKUP DATABASE [dbamaint] TO DISK = N'P:\SQL_Bac...".: 100% complete End Progress
Progress: 2014-12-20 22:51:13.08 Source: Back Up Database Task
Executing query "BACKUP DATABASE [DATASTORE] TO DISK = N'P:\SQL_Ba...".: 100% complete End Progress
Progress: 2014-12-20 22:51:52.72 Source: Back Up Database Task
Executing query "BACKUP DATABASE [ETL_Proc] TO DISK = N'P:\SQL_Bac...".: 100% complete End Progress Progress: 2014-12-20 22:51:54.87
Source: Rebuild Index Task Executing query "USE [ReportServer] ".: 0% complete End Progress Progress:
2014-12-20 22:51:54.88 Source: Rebuild Index Task Executing query "ALT... The package executed successf... The step succeeded.

ORA-12154: TNS:could not resolve service name

Hi Guru's
i applied Maintainacepack 3480000 patch on my application for upgrading 11.5.7 to11.5.10.2, after completion of patch, I run the autoconfig it has given bellow error, please anybody can help me, i need to finish my task immediately, please provide me the solution.
autoConfig Profile Phase
Running Profile Process 1 of 1 for CLN_TOP
Executing script in InstantiateFile:
/sgmtemp/prodcomn/admin/install/MSBEP004_dcpsr006osm/clnadmprf.sh
script returned:
clnadmprf.sh started at Sun Feb 17 06:24:13 WST 2008
The environment settings are as follows ...
ORACLE_HOME : /sgmtemp/prodora/8.0.6
ORACLE_SID :
TWO_TASK : msbep004
PATH : /sgmtemp/prodora/iAS/Apache/perl/bin:/sgmtemp/prodora/8.0.6/bin:/sgmtemp/prodappl/fnd/11.5.0/bin:/sgmtemp/prodappl/ad/11.5.0/bin:/sgmtemp/prodcomn/util/jre/1.1.8/bin:/sgmtemp/prodcomn/util/unzip/unzip::/sgmtemp/prodora/8.0.6/bin:/usr/bin:/usr/ccs/bin:/usr/sbin:/sgmtemp/prodora/iAS/Apache/perl/bin:/sgmtemp/prodora/iAS/Apache/perl/bin:/sgmtemp/prodora/8.0.6/bin:/sgmtemp/prodcomn/util/jre/1.1.8/bin:/sgmtemp/prodcomn/util/unzip/unzip:/sgmtemp/prodora/8.0.6/bin:/usr/bin:/usr/ccs/bin:/usr/sbin:/usr/java14/jre/bin:/usr/java14/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/sgmtemp/prodappl/bin:/usr/bin/X11:/sbin:/usr/lpp/pd/bin:.
LD_LIBRARY_PATH : /sgmtemp/prodora/8.0.6/network/jre11/lib/aix/native_threads:/sgmtemp/prodappl/cz/11.5.0/bin:/sgmtemp/prodora/8.0.6/lib:/usr/dt/lib:/usr/openwin/lib
Executable : /sgmtemp/prodora/8.0.6/bin/sqlplus
SQL*Plus: Release 8.0.6.0.0 - Production on Sun Feb 17 06:24:13 2008
(c) Copyright 1999 Oracle Corporation. All rights reserved.
ERROR:
ORA-12154: TNS:could not resolve service name
clnadmprf.sh exiting with status 1
ERRORCODE = 1 ERRORCODE_END
.end std out.
thanks

Please Apply "Patch 5985992 - TXK AUTOCONFIG ROLLUP PATCH Q (JUL/AUG 2007)", run AutoConfig, and check then.

ORA-12154: TNS:Could not resolve service name. (WIS 10901).

HI Gurus, we have the following scenario...
Weu2019ve installed Busines Objects EDGE 3.1 SP3.
The server of this installation is MS Windows Server 2003 Enterprise Edition SP2, Intel ® Xeon Enterprise TM CPU 2.80 GHz 6.5 RAM.
In the Server we have SAP R/3 Installed over a DB Oracle 9i Enterprise Edition Release 9.2.8.0.
We installed all BO bundle with successful and we can use the Designer Tool for create universe. In the creation of the universe, we created a connection to the database of the SAP R/3 System and the test runs well, we save and export the universe to CMS. Then, we used that universe in the WebI tool of the suite installed in the server, and it runs well (we call the universe, selected fields of the table, and after run the query, it gives us registers of the DB).
After all this, we open the InfoView and used the WebI and execute the same universe and the same steps. And when we execute the query the following error occurs .
A database error occured. The database error text is: ORA-12154: TNS:Could not resolve service name. (WIS 10901)
The connection to DB is through Designer and we use ODBC Oracle to create the Universe with the Client type and we used super user system, validated previously OK.
Any suggestion for this error?.
Thanks.
Betto.
Edited by: Alberto Magaña Chávez on Jul 9, 2011 7:44 PM

Make sure there are no syntax errors in the TNSNAMES.ORA file, look for unmatched parentheses. Also check the SQLNET.ORA file.
Is the environment is clustered, if so then make sure you have the ODBC connection in all the servers.

Error in releasing service entry sheet

Dear All,
While releasing Service Entry Sheet,user is facing the below error.
BS 007 " Goods receipt for purch order " is not allowed (Internal Order Number)
If anyone of you people would have face this sort of issue or heard about it then do let me know.
Thanks in advance
nainesh
sap mm

Nano ,
Why the user want to Do MIGO ,
Service entry shhet are meant for service, In STD SAP you can not have do good recieved For the service
The process is like
1 Creation of service aster
2 Create a Service PO
3 Maintain service entry sheet
4approve service entry sheet
5 MIRO
After you release the serive PO try to do the MIRO

Not released note

Hi I am looking at the "Security Guide For Self-Serives" and it refers me to an SAP note 785345. However when I try to look at it, I get "Note 785345 is not released". Does anyone know how to get to the unreleased notes?
Thank you.

Brandon,
Yes, I'm glad to see that note 1587566 is now released .
ETA of 7.40 is planned for October 2014
Check notes:
http://service.sap.com/sap/support/notes/147519
http://service/sap/com/sap/support/notes/66971
(this is subject to last minute changes of course).
Jude

Configuration details for releasing service entry sheet

Dear all
Kindly let me know the step by step procedure in configuration for releasing service entry sheet,
regards
M.Chandra mohan

Identify the characteristics that you will use for determination of release strategy. Create characteristics for each of these - ensure that the reference table name is CESSR and reference field name is the appropriate field name. If the field name is not found in CESSR you will need to use an user exit - better not to get into that for now.
Create a class (of class type 032) and assign these characteristics to the class.
Then create one Release Group and link the class to the release group.
Create Release Codes for the release group
Create release indicator
Create release strategies.
You will configure this in the golden master client. However you will need to maintain the classification in all clients using CL20N or CL24N.
Lakshman

[Not solved][Sudo/X] Enter key not released after typing password

After upgrade to xserver 1.16 I noticed strange thing - any command I try to run with sudo "hangs" keyboard and mouse. It looks like after typing password and pressing <Enter>, this key is not released.
System is still responsive, for example I can watch youtube, listen to music, there is no high cpu usage, but inputs are blocked.
For example:
sudoedit /etc/whateverrc
opens editor and cursor goes down.
This is not a problem with my keyboard
In tty sudo works fine.
Last edited by n0rv (2014-08-09 19:45:28)

jasonwryan wrote:How do you start X?
startx
What DE/WM?
AwesomeWM, quite old setup.
What is in your journal/logs?
After "hang" X still works, so I need to kill it (alt+sysrq+re) or reboot.
Xorg.log.0.old
[ 5770.071] (II) RADEON(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[ 5770.071] (II) RADEON(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[ 5770.110] (II) systemd-logind: got resume for 13:68
[ 5770.110] (II) systemd-logind: got resume for 13:67
[ 5770.126] (II) systemd-logind: got resume for 13:64
[ 5770.156] (II) systemd-logind: got resume for 13:65
[ 5770.209] (II) systemd-logind: got resume for 13:66
[ 5885.135] (II) systemd-logind: got pause for 226:0
[ 5885.135] (II) systemd-logind: got pause for 13:68
[ 5885.135] (II) systemd-logind: got pause for 13:67
[ 5885.135] (II) systemd-logind: got pause for 13:64
[ 5885.135] (II) systemd-logind: got pause for 13:65
[ 5885.135] (II) systemd-logind: got pause for 13:66
[ 5893.481] (II) evdev: USB Keyboard: Close
[ 5893.481] (II) UnloadModule: "evdev"
[ 5893.481] (II) systemd-logind: releasing fd for 13:66
[ 5893.481] (EE) systemd-logind: failed to release device: Connection is closed
[ 5893.481] (II) evdev: USB Keyboard: Close
[ 5893.481] (II) UnloadModule: "evdev"
[ 5893.481] (II) systemd-logind: releasing fd for 13:65
[ 5893.481] (EE) systemd-logind: failed to release device: Connection is closed
[ 5893.481] (II) evdev: A4Tech PS/2+USB Mouse: Close
[ 5893.481] (II) UnloadModule: "evdev"
[ 5893.481] (II) systemd-logind: releasing fd for 13:64
[ 5893.481] (EE) systemd-logind: failed to release device: Connection is closed
[ 5893.481] (II) evdev: Power Button: Close
[ 5893.481] (II) UnloadModule: "evdev"
[ 5893.481] (II) systemd-logind: releasing fd for 13:67
[ 5893.481] (EE) systemd-logind: failed to release device: Connection is closed
[ 5893.481] (II) evdev: Power Button: Close
[ 5893.481] (II) UnloadModule: "evdev"
[ 5893.481] (II) systemd-logind: releasing fd for 13:68
[ 5893.481] (EE) systemd-logind: failed to release device: Connection is closed
[ 5893.560] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[ 5893.560] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[ 5893.560] (EE)
Fatal server error:
[ 5893.560] (EE) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[ 5893.560] (EE)
[ 5893.560] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 5893.560] (EE) Please also check the log file at "/home/n0rv/.local/share/xorg/Xorg.0.log" for additional information.
[ 5893.560] (EE)
[ 5893.560] (EE)
[ 5893.560] (EE) Backtrace:
[ 5893.613] (EE) 0: /usr/bin/Xorg.bin (xorg_backtrace+0x56) [0x593966]
[ 5893.614] (EE) 1: /usr/bin/Xorg.bin (0x400000+0x197b69) [0x597b69]
[ 5893.614] (EE) 2: /usr/lib/libc.so.6 (0x7f5912809000+0x33df0) [0x7f591283cdf0]
[ 5893.614] (EE)
[ 5893.614] (EE) Segmentation fault at address 0x0
[ 5893.614] (EE)
FatalError re-entered, aborting
[ 5893.614] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 5893.614] (EE)
journalctl:
sie 07 23:15:12 Arch sudo[3368]: n0rv : TTY=pts/1 ; PWD=/home/n0rv ; USER=root ; COMMAND=sudoedit /etc/yaourtrc
sie 07 23:15:12 Arch sudoedit[3368]: pam_unix(sudo:session): session opened for user root by (uid=0)
sie 07 23:15:12 Arch systemd[1]: Starting user-0.slice.
sie 07 23:15:12 Arch systemd[1]: Created slice user-0.slice.
sie 07 23:15:12 Arch systemd[1]: Starting User Manager for UID 0...
sie 07 23:15:12 Arch systemd[3372]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
sie 07 23:15:12 Arch systemd-logind[1230]: New session c2 of user root.
sie 07 23:15:12 Arch systemd[1]: Starting Session c2 of user root.
sie 07 23:15:12 Arch systemd[1]: Started Session c2 of user root.
sie 07 23:15:12 Arch systemd[3372]: Starting -.slice.
sie 07 23:15:12 Arch systemd[3372]: Created slice -.slice.
sie 07 23:15:12 Arch systemd[3372]: Starting D-Bus Message Bus Socket.
sie 07 23:15:12 Arch systemd[3372]: Listening on D-Bus Message Bus Socket.
sie 07 23:15:12 Arch systemd[3372]: Starting Paths.
sie 07 23:15:12 Arch systemd[3372]: Reached target Paths.
sie 07 23:15:12 Arch systemd[3372]: Starting Timers.
sie 07 23:15:12 Arch systemd[3372]: Reached target Timers.
sie 07 23:15:12 Arch systemd[3372]: Starting Sockets.
sie 07 23:15:12 Arch systemd[3372]: Reached target Sockets.
sie 07 23:15:12 Arch systemd[3372]: Starting Basic System.
sie 07 23:15:12 Arch systemd[3372]: Reached target Basic System.
sie 07 23:15:12 Arch systemd[3372]: Starting Default.
sie 07 23:15:12 Arch systemd[3372]: Reached target Default.
sie 07 23:15:12 Arch systemd[3372]: Startup finished in 7ms.
sie 07 23:15:12 Arch systemd[1]: Started User Manager for UID 0.
sie 07 23:15:20 Arch kernel: SysRq : Keyboard mode set to system default
sie 07 23:15:20 Arch systemd-journal[1227]: Journal stopped
sie 07 23:15:21 Arch systemd-journal[3399]: Permanent journal is using 131.6M (max allowed 100.0M, trying to leave 2.9G free of 6.0G available → current limit 131.6M).
sie 07 23:15:21 Arch kernel: SysRq : Terminate All Tasks
sie 07 23:15:21 Arch systemd-journald[1227]: Received SIGTERM.
sie 07 23:15:21 Arch systemd[1]: [email protected] has no holdoff time, scheduling restart.

OSS notes and service packs

Hi,
Can anyone elaborate me the difference between OSS1 transaction and SNOTE transaction in relation with application of OSS notes ?
Also, what is the difference between SAP service pack and OSS notes ?
Are SAP service pack similar to windows service packs ?
Whose job is it to apply OSS notes and service packs ?
Regards,
Tushar.

A service pack is generally a collection of the (release dependent) OSS notes that have been created since the last pack.
If you have done custom development on an SAP object, that development will likely be lost if an OSS note modifies it. You will have an opportunity to review the changes using transaction SPAM when service packs are applied.
Rob
Message was edited by: Rob Burbank

ServiceLayer - Could not start service

Hello,
I've just bought Nokia N95 8GB and wanted to install Nokia PC Suite. When installing PC Connectivity Solution there was a window message with title ServiceLayer and text "Could not start service". Afterwards, installation continued and finished "succesfully". Unfortunately I have problem that was posted a few times. I can't connect phone to PC Suite. I tried to Repair PC Connectivity solution, uninstall this and Cable driver and repair Nokia PC Suite, uninstall everything and use later Nokia cleaner etc. Nothing worked. When I go to PC Connectivity Solution and run manually ServiceLayer.exe I get the same message, that "Could not start service". What should I do? Please help me. I do not want to format my HDD and install Windows from the beginning. I use WinXP SP2.

Hi,
I've found the cause of the problem. It was firewall - Agnitum Outpost Personal Firewall Pro. I had old version and after installing new version the message dissapeared. As You can see below - one of issues solved was the problem "Outpost Firewall could block installation of services".
"Outpost Firewall Pro 2008 (build 6.0.2172.214.422.270)
Release date: November 14, 2007
The following issues are resolved (only significant ones are listed):
* Outpost monitor and Outpost Feedback were not registered in startup entries
* Outpost Firewall could block installation of services
* Information about crashes could not be sent to Agnitum
* Rules autocreation did not work on 64-bit systems for applications from ProgramFiles (x86) and SysWOW64 folders
* Most commonly reported crashes (including crash on content filtering)
* Error 14001 during installation
* Rules were applied incorrectly in some cases
* Address macros could be incorrectly resolved in rules
* Leaktests SPT 15 and SPT 16 were failed on Vista64
* Error while importing LAN settings from Outpost Firewall 4.0
* Web pages content could be blocked/corrupted (GZIP decoding issue)
* Outpost Firewall now cannot be installed over Outpost Security Suite"
But now I have different problem - I can't download update of PC Suite. The download starts and it stops when the progress bar is in its way. Sometimes it goes to the end but the installation doesn't start. What could be the problem?

Could not resolve service name

Hi friends.
I have this problem where want conect to database 9i: ERROR: "12154" could not resolve service name".
I was see LISTANER.ORA, TNSNAMES.ORA, SLQ.ORA files and not seem anything wrong.
I have install Oracle 9i database enterprise release 2 (9.2.0.1) server and client, also developer site 10g(9.0.4), all these in my personal Pc.
Thanks to all.

Thanx for the reply...Justin
Yes, I am sure I only have one Oracle Home...
Anyways, here is the tnsnames file content:
# TNSNAMES.ORA Network Configuration File: C:\ShafHome\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.
SHAF =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = home-3770fh0hi3)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = shaf.world)
INST1_HTTP =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = home-3770fh0hi3)(PORT = 1521))
(CONNECT_DATA =
(SERVER = SHARED)
(SERVICE_NAME = MODOSE)
(PRESENTATION = http://HRService)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC2))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
Thanx,
Shaf

12154: "Could not resolve service name"

[oracle@proton dbs]$ sqlplus system/manager@bcqa
SQL*Plus: Release 8.1.7.0.0 - Production on Fri May 4 16:00:00 2001
(c) Copyright 2000 Oracle Corporation. All rights reserved.
ERROR:
ORA-12154: TNS:could not resolve service name
I have read many documentations and I have no clue on what I'm doing wrong.. Here are the contents of a few .ora files:
listener.ora
LISTENER =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = proton.cityxpress.com)(PORT = 1521))
(PROTOCOL_STACK =
(PRESENTATION = TTC)
(SESSION = NS)
tnsnames.ora
PROTON.CITYXPRESS.COM =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.11.19)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = bcqa.cityxpress.com)
sqlnet.ora
NAMES.PREFERRED_SERVERS =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = dbhost)(PORT = 1575))
NAMES.DEFAULT_DOMAIN = cityxpress.com
SQLNET.EXPIRE_TIME = 0
NAMES.DIRECTORY_PATH=(HOSTNAME)
lsnrctl started with no problem and here's the output from lsnrctl status:
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>
[oracle@proton admin]$ lsnrctl status
LSNRCTL for Linux: Version 8.1.7.0.0 - Production on 04-MAY-2001 16:10:13
(c) Copyright 1998 Oracle Corporation. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=proton.cityxpress.com)(PORT=1521))(PROTOCOL_STACK=(PRESENTATION=TTC)(SESSION=NS)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 8.1.7.0.0 - Production
Start Date 04-MAY-2001 16:10:06
Uptime 0 days 0 hr. 0 min. 7 sec
Trace Level off
Security OFF
SNMP OFF
Listener Parameter File /usr/oracle/network/admin/listener.ora
Listener Log File /usr/oracle/network/log/listener.log
The listener supports no services
The command completed successfully
[oracle@proton admin]$
<HR></BLOCKQUOTE>
Here's the output from using tnsping:
[oracle@proton admin]$ tnsping proton.cityxpress.com
TNS Ping Utility for Linux: Version 8.1.7.0.0 - Production on 04-MAY-2001 16:11:22
(c) Copyright 1997 Oracle Corporation. All rights reserved.
Attempting to contact (ADDRESS=(PROTOCOL=TCP)(HOST=proton.cityxpress.com)(PORT=1521))
OK (0 msec)
That's good, but look at this one:
[oracle@proton admin]$ tnsping proton
TNS Ping Utility for Linux: Version 8.1.7.0.0 - Production on 04-MAY-2001 16:12:11
(c) Copyright 1997 Oracle Corporation. All rights reserved.
TNS-03506: Failed to create address binding
Any help would be greatly appreciated, thanks.

you have a listener problem at least.
The status request to lsnrctl reports "no service". If the listener does not support any service, no connection.
configure a service using "netasst".
Regards
null

Bootcamp not releasing services

Similar Messages

Maybe you are looking for