Error "no connect to database " after moving group to second node.

hi experts,
I set up ERP2005 SR1 and MSSQL2005 with two nodes MSCS.
I am facing error "no connect to database session terminated mscs" from SAP GUI
after moving group to second node.
Now SPS level and kernel patch level has been not updated yet.
I counld'nt find any sap notes, so any help and suggestion could be appreciated.
Best Regards
MASAKI

solved myself . i was missing set SQL Service Account have Local Admnistrators.

Similar Messages

Error while connecting to Database after Database upgradation

Hi All,
I installed and worked with BAM and used Oracle Database 9i previously. After the Database
was upgraded to 10g (10.2.0.4.0 which is compatible for BAM), I am trying to ReInstall BAM
which is throwing me an error.
It accepts the Database Login Information but at the step of building Repository for
Enterprise Link it gives up the following error:
' A connection with the database cannot be made '
Can anyone please help me to figure out this one.
Thanks,
Vishal

Hi,
I also have the same problem.Could you plz tell us what configuration I need to add in tnsnames.ora file.
content of my tnsnames.ora file is below
# tnsnames.ora Network Configuration File: C:\DevSuiteHome_2\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = Rahul-PC)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = PLSExtProc)
)

Error while connecting MYSQL Database

Hi,
I use a 30 days trial of Crystal Reports 2008. When i try to connect with the database i always get the next error: [http://www.visiscan.nl/error.jpg]
The database is 4.1GB large and there is 10GB free space on the database.
Anybody can tell me what to do?

Hi Tom,
As I understand the error while connecting to database is
u201CFailed to retrieve data from databaseu201D
There could be some could be multiple reasons for this.
If you are using an ODBC connection then try to check the DSN. Recreate the same and then try.
If the database is oracle check if native client is installed and try to ping from the native client to check if it responds.
When connecting to Oracle, ensure that the Service name is identical to that used in the <ORA_HOME>/network/admin/tnsnames.ora file on the BusinessObjects XI Release 2 server.
For ODBC databases, ensure that the ODBC DSN is exactly the same in the ODBC Manager as on the BusinessObjects XI Release 2 server.
Please let us know if this helps
Regards,
Aditya Joshi

Error connecting to database after upgrade P6 R7.0 to P6 R8.2

Dear friends,
could you help me,
i have problem with primavera P6,
currently we using P6 R7.0 with server client. i have succesfully to installed it at sever and client and database connected too.
but after we purchased the new version R8.2, and i have upgraded. we got the big problem.
primavera could connect to PMDB, i tried create database (PMDB) but always failed. could you please to solve my problem?

Hi,
Use following credential if you are using Oracle database (XE)
1. Database Alias : PMDB
2. Driver Type : Oracle
click next , type XE as oracle connections string
Enter Public Login Information dialog, enter the following information.
The default public username is pubprm$pm.
The pubuser password will be the same password you entered during the original installation, e.g. admin01, i.e. the same password you have been using to login to P6
Professional.
Click next and finish

Unable to Connect to Database (after server has been re-started)

Hi, I use Essbase Admin Services 7.1.3 and the server was not responding, therefore our IT guys re-started it. Since then I am unable to connect to one of the applications. I have tried to start/Stop the application but it just says "Application did not start". There are 6 databases in this application altogether (3 data and 2 Currency). The application has been there for about 3 years (it holds historic sales data) and there has never been any problems with it. When I tried to Start the application, in the message panel at the bottom it says "Error: 1013015 Unable to Connect to Database (2003)". It's as if there is a problem with this 2003 database but the 2002 and 2004 database are OK. Has anyone ever had this problem and knows how to rectify it?? Thanks in advance. Sarah

It may be that the server restart corrupted the database. Go into database properties and uncheck the box start database with application and then try to restart the application. You can try database validation, or simply reload the database from backup. But you can get the application up and the rest of the databases up by decoupling the database restart from the application start. There will be a .xcp log file in your application directory (and possibly your database directory.) These might help Hyperion Support in identifying the cause of the problem. But the quickest solution would be to reload the database from backup. The serer and application logs can also provide help in identifying the problem. One of the keys is to determine why the server is not responding before restarting the server. It may be that a single application is the source of problem. Typical causes are unscheduled free space restructures, application loads of large databases, and an occasional rogue process. Rather than rebooting the entire box, or even restarting the Essbase server, the safest approach is to only kill the job that is soaking up the cpu cycles, causing the server to be unresponsive. This requires identifying the offending process (esssvr.exe) and killingit. Often that restores the rest of the system to operations, giving you time to focus onthe offending application. You learn thses things when you are pushing the server to its limits (or beyond). If it happens often, you need to do a serious performance audit of teh server and determine whether you need more power and/or memory. And in any case, you are less likely to encounter this sort of problem in the future if you try to limit applications to a single database. This will allow a better utilization of system resources. And also, it's a good idea to shut down applications that you are not going to be using for a while. Every loaded app takes system resources whether or not it is doing anything. So review your list of apps that start on startup and consider unloading apps after completing batch processing. Sorry about the long lecture, but I speak from somewhat painful experience. I hope that this will help you.

Why I cannot connect to database after deploying application to OAS?

Hello experts...i have a new problem and here are the facts:
I`m using on Windows Xp:
Oracle Database 10.2.0
Oracle Application Server 10.1.3
Oracle Jdeveloper 10.1.3.3
I`m creating a new application using jdeveloper and i`m using 2 connection classes:
a) First connection class using:
InitialContext ctx=new InitialContext();
DataSource ds=ctx.lookup("jdbc/connDS");
Connection conn=ds.getConnection();
b) Second connection class using:
Connection conn = DriverManager.getConnection("jdbc:and the entire link goes here");
So far so good, but when I create a ear file using the First connection class and after i deploy it to OAS my application will not connect anymore to database!
If I will use the Second connection class, and create an ear file then deploy it to OAS, my application works fine, it connects to database but i have a problem. In my application users can upload and download the files they uploaded. The files are saved in DB as blob. The problem appears when users are downloading the files because for example file "example.doc" is uploaded on the server database and when a user try to download it the name of the file is like "example_doc" and my pc open it like an html in which is a server 500 error. Someone told me that happens because of my connection class... and I want to find out you`re opinion.
Why i cann`t connect to DB after deploy the application on OAS using the FIRST connection class?
- on Jdeveloper i can connect to DB using both of the connect classes (one at a time)
- I`m creating a war file from jdeveloper and deploy the ear file on the OAS
- on OAS i`ve created the connection pool and the data source and "The connection was establish succesfully"
Why the uploaded files are downloaded in this way? it`s the connection the problem?
- I want to tell you that when i`m extracting data from the DB table i`m not using a temp file, the conversion is made in the java class and the program throws me the file to download.
- as i told you in Jdeveloper both of the connection classes work!!! and when i`m using the FIRST connection class and try to download, the files ARE DOWNLOADED PERFECTLY CORRECT!
- if i`m using the SECOND connection class in jdeveloper, running the application on the built in oc4j instance and trying to download the same files, the files are DOWNLOADED BAD like I told you: the name of the file is like "example_doc" and my pc open it like an html in which is a server 500 error. with the pdf format is the same problem but my pc cannot open it telling something with "bad conversion...." error.
There are someone who had the same problem?
Theoretically i had to make the application to connect to the database after deploy it to OAS with the FIRST connection class and this way my files will be downloaded corectly... what to do?

no one knows nothing about this issue? :(... i`m dissapointed...

SCCM coudn't connect to database after recovering SQL server

Hello.
Please help to solve a problem. After crashing data storage, i have lost my SCCM and SQL server. I have restored SCCM server as virtual machine and re-install SQL server. I restored old databases to the new SQL server. Same instances and names.
And now i have logs smsexec.log :
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
SMS_EXECUTIVE
27.03.2015 10:34:19
3268 (0x0CC4)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
SMS_EXECUTIVE
27.03.2015 10:34:19
3268 (0x0CC4)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
SMS_EXECUTIVE
27.03.2015 10:34:19
3268 (0x0CC4)
CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
SMS_EXECUTIVE
27.03.2015 10:34:19
3268 (0x0CC4)
I found that i lost my certificate
i found article Certificate drop down menu empty when trying to select SSL certificate to enable SQL Server 2008 client encryption
but i get an error when trying to execute certificate request.
ERROR TRANSLATE --- no information about certificate template
I don't know what to do. Plz help. This problem sticks me. :(

~===================== << Starting Configuration Manager 2012 Setup >> =====================
Configuration Manager Setup 01.04.2015 15:37:03
8980 (0x2314)
INFO: ConfigMgr2012 Setup was started by AV\dobrokhotov.vn.
Configuration Manager Setup 01.04.2015 15:37:03
8980 (0x2314)
INFO: Command line specified was: "C:\Program Files\Microsoft Configuration Manager\bin\X64\SetupWpf.exe"
Configuration Manager Setup 01.04.2015 15:37:03
8980 (0x2314)
FQDN for server SRV-SCCM is SRV-SCCM.ashipyards.com
Configuration Manager Setup 01.04.2015 15:37:03
8980 (0x2314)
INFO: Target computer is a 64 bit operating system.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Checking for existing setup information.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Setting setup type to 1. Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
INFO: Checking for existing SQL information.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: 'SRV-SQL.ashipyards.com' is a valid FQDN.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Verifying the registry entry for Asset Intelligence installation
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Found registry key for installation of Asset Intelligence full version
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Setup detected an existing Configuration Manager installation. Currently installed version is 7958
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Phase is 1C7 Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
WARNING: Failed to initialize COM to get SDK Providers. It might already be initialized. return code: 80010106.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: SDK Provider is on SRV-SCCM.ashipyards.com.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Setting the default CSV folder path Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
INFO: Language: Mobile Device (INTL), LangPack: 0.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Language: RUS, Server LangPack: 1. Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
INFO: Language: RUS, Client LangPack: 1. Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
INFO: Configuration Manager Build Number = 7958
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Configuration Manager Version = 5.0 Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
INFO: Configuration Manager Minimum Build Number = 800
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Verifying Configuration Manager Active Directory Schema Extensions.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Found DS Root:CN=Schema,CN=Configuration,DC=ashipyards,DC=com
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Verifying Configuration Manager Active Directory Schema Extensions.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Found DS Root:CN=Schema,CN=Configuration,DC=ashipyards,DC=com
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: SqlMasterDB = MSSC\master Configuration Manager Setup
01.04.2015 15:37:05 8980 (0x2314)
Removed SQL alias SRV-SQL.ashipyards.com\MSSC successfully.
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Registered type SRV-SQL.ASHIPYARDS.COM MSSC\MASTER for SRV-SQL.ashipyards.com MSSC\master
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Registered type SMS Master for SRV-SQL.ashipyards.com MSSC\master
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Registered type SRV-SQL.ASHIPYARDS.COM MSSC\SYSTEMCENTERCM_S01 for SRV-SQL.ashipyards.com MSSC\SystemCenterCM_S01
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Registered type SMS ACCESS for SRV-SQL.ashipyards.com MSSC\SystemCenterCM_S01
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: 'SRV-SCCM.ashipyards.com' is a valid FQDN.
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Run Site Maintenance on the primary site.
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Checking for existing setup information.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: Setting setup type to 1. Configuration Manager Setup
01.04.2015 15:37:06 8980 (0x2314)
INFO: Checking for existing SQL information.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: 'SRV-SQL.ashipyards.com' is a valid FQDN.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: Verifying the registry entry for Asset Intelligence installation
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: Found registry key for installation of Asset Intelligence full version
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: SDK Provider is on SRV-SCCM.ashipyards.com.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: Retrieving current site control image...
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
CSiteSettings::ReadActualSCFFromDatabase: Failed to get sql connection
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
ERROR: Failed to retrieve verifiable site control data
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: Evaluating for Site Maintenance process.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: g_SetupCmdLine.bMoveSql 0, g_SetupCmdLine.sNewSqlServer , g_SetupCmdLine.sNewSqlDatabaseName , pSetupInf->SqlMasterDB MSSC\master.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:09
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:09
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:09
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:09
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:12
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:12
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:12
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:12
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:15
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:15
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:15
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:15
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:18
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:18
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:18
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:18
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:21
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:21
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:21
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:21
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:24
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:24
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:24
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:24
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:27
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:27
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:27
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:27
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:30
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:30
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:30
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:30
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:33
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:33
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:33
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:33
8980 (0x2314)
ERROR: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:36
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:36
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:36
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:36
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:36
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:39
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:39
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:39
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:39
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:42
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:42
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:42
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:42
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:45
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:45
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:45
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:45
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:48
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:48
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:48
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:48
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:51
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.

Oracle Enterprise Manager can't connect to database after installation

Hello, I have a problem with Enterprise Manager. I installed Oracle 10g and the patch 10.2.0.2. After install, I could connect to database from SqlPlus without problems, but when I try to connect from AllPrograms - Oracle - DatabaseControl or since the Web browser with http://servername:1158/em nothing happen. I reviewed the status of dbconsole with emctl status dbconsole but the status is running. I recreated the repository with emca -deconfig.......-repos drop and emca -config ...... -repos create , but nothing happened. I reviewed some threads in this forum, but I didn't find the solution. Finally I could connect from the browser but with http://localhost:1158/em. Do you help me how can I connect from Database Control, because the operators in Computer Center should monitor the instance since there, and when I want to connect since my own PC how can do it?
Thanks for your help and excuse my English, I am from Bogotá Colombia.
Sincerely Rubén

Hi,
Check the network connectivity between db server and pc from where u want to access em.
Check the listener service.
Check firewall settings, it should be off.
Regards,
Xaheer

Show error when connect Company Database by DI API in 2004B

Hi
I use the DI API to connect company database in 2004B. I can get the company lists by SAPbobsCOM.CompanyClass.GetCompanyList().
I write a program to testing the connection that show two different result in client and server side.
- It show the error -2147221164 (Class not registered), when connect company database in client PC.
- The same program run in server, it connected.
I already checked my config as below
- SAP 2004B is installed 7.20.145 SP:00 PL:25
- SAPbobsCOM67.dll is 6.70.188.0 version, and "Special Build Description" is 21.
The client and server side are same config.
Any ideas how I should handle this?
Thanks
Winson

sorry! it is wrong posted in here!!

Cannot connect to database after apex 2.2 install

I have installed HTML DB from Companion CD Release 2 (10.2.0.1.0) and then i upgrade to apex 2.2. Apex is working, but when i try to connect my database form command line, i get:
sqlplus SYS/pass as sysdbaSQL*Plus: Release 10.1.0.3.0 - Production on N Sie 13 20:23:41 2006
Copyright (c) 1982, 2004, Oracle. All rights reserved.
ERROR:
ORA-12560: TNS:protocol adapter error
Enter user-name:
sqplus works when i set ORACLE_SID, but my oracle applications don't.
How repair that? My system is WinXP SP2.

You need to check your listener and its settings.
There are many ways to do this, so I recommend that you start by reading http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14196/network.htm#sthref173
Apex can work without this, because it is entirely inside the database, and (I think) sqlplus can bypass the listener, particularly when connecting as sysdba.
Without setting ORACLE_SID, you could have connected with
sqlplus sys/pass@service as sysdba

Can't connect to database after restarting, TNS Error

I'm a little new to Oracle 10g administration. I successfully installed it on Oracle Enterprise Linux. Immediately after installation, I was able to connect to the default ORCL database using sqlplus. However, when I restarted the computer, I was no longer able to do so, even after restarting the listener service.
Here is the error I get:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
The other strange thing is, whenver I create a new database using dbca, immediately after that I can connect via sqlplus. However, if I perform a shutdown/startup, I get the same error as above. Restarting the listener doesn't make any difference.
A tnsping to my new database is successful but I can't connect to it from sqlplus.
Running the 'lsnrctl services' command immediately after making the new database shows it running but after a shutdown/restart only the default EXTPROC service shows.
Can anyone tell me why this happens and how to resolve it? Is there some other service I have to restart? Also, why does the listener not know of the service when it is explicitly configured in the tnsnames.ora file?
Note that I change my ORACLE_SID to the service name before attempting to connect.
Everything in the listener and tnsnames files was coded by the software, not by me.
Thanks for any help.
Here is my listener file:
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /opt/oracle/product/10gR2)
(PROGRAM = extproc)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = linux)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
______________________________________________

I played around a little by deleting and creating databases. Here is my current tnsnames file:
TESTDATA =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = linux)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = TESTDATABASE)
ORCL =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = linux)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
I just made the database called TESTDATA. Here is the output of the command 'lsnrctl services', where the TESTDATABASE service refers to the database I just made:
[oracle@linux ~]$ lsnrctl services
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 11-JUL-2007 22:19:47
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=linux)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Service "TESTDATABASE" has 1 instance(s).
Instance "TESTDATABASE", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:13 refused:0 state:ready
LOCAL SERVER
Service "TESTDATABASEXDB" has 1 instance(s).
Instance "TESTDATABASE", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:972 state:ready
DISPATCHER <machine: linux, pid: 25175>
(ADDRESS=(PROTOCOL=tcp)(HOST=linux)(PORT=38662))
Service "TESTDATABASE_XPT" has 1 instance(s).
Instance "TESTDATABASE", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:13 refused:0 state:ready
LOCAL SERVER
Service "test2.class" has 1 instance(s).
Instance "test2", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
Service "test2_XPT.class" has 1 instance(s).
Instance "test2", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
The command completed successfully
[oracle@linux ~]$
Now I'm connecting and here is my result:
[oracle@linux ~]$ sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Jul 11 22:21:24 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> connect sys/pwd@testdata as sysdba
Connected.
SQL>
I am able to access the database from the OEM.
Now, here's what happens next. I shutdown the database from sqlplus and now when I restart, I get this message:
SQL> startup
ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
Now, if I exit sqlplus, enter again and try to connect, I get this error:
oracle@linux ~]$ sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Jul 11 22:28:01 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> connect sys/pwd@testdata
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
SQL>
Any solutions? I appreciate your help.

Cannot connect to Database after install Developer Suite

Help..
I installed Oracle Database and everything seems work properly. I can connect to the database. (system/oracle@orcl)
well, but after I install the developer suite, I can't connect to the database anymore.
I did check the services and both OracleOraDb10g_home1TNSListener and OracleServiceORCL are started.
I try to search help from google but I cannot solve the problem by myself. I also include two ora file below,
tnsnames.ora
=====
# tnsnames.ora Network Configuration File: C:\oracle\product\10.2.0\db_1\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.
ORCL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
====
listener.ora
===
# listener.ora Network Configuration File: C:\oracle\product\10.2.0\db_1\network\admin\listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = C:\oracle\product\10.2.0\db_1)
(PROGRAM = extproc)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
====
everything seems should working properly but I still have problem cannot connect to the database. SQLPlus says "ORA-12154" and "ORA-12514"
please help me.. I need to finish my project within next 2 weeks or I have to study one more year. T_T

Hi ...
The Oracle Doc points out as actions in this type of error:
- If you are using local naming (TNSNAMES.ORA file):
- Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA)
- Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible.
- Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file.
- Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable.
- If you are using directory naming:
- Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Verify that the LDAP directory server is up and that it is accessible.
- Verify that the net service name or database name used as the connect identifier is configured in the directory.
- Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier
- If you are using easy connect naming:
- Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Make sure the host, port and service name specified are correct.
- Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming.According to the above and my LISTENER settings in listener.ora file which is...
LISTENER =
(DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = myhost)(PORT = 1521))
)there is one ')' missing closing parenthesis....
So , modify your LISTENER settings ... according to the below....The difference is the ')' in bold....
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
Can you connect now.....????
Regards,
Simon

"Software Usage Metrics initialize failed" error when open Report Manager, after moving ReportServer from SSRS 2008 to SSRS 2012 (Native Mode)

I've asked this question in SQL Server Upgrade forume, I'm asking here as well:
Your help is highly appreciated!
After migrating ReportServer db from 2008 to 2012, when access Report Manager throughhttp://myserver:80/Reports, I got the error below:
ui!ReportManager_0-3!11d8!02/04/2013-15:19:12:: e ERROR: Software Usage Metrics initialize failed
The process is below:
•I successfully installed SQL Server 2012 (64-bit) Enterprise as a Native Mode on a server who runs Windows 7 Enterprise SP1 (64-bit).
•I restored "ReportServer2008To2012" and "ReportServer2008To2012TempDB" in SSRS 2012 from the db files backed up in SQL 2008. In SSRS 2008, I have SSRS Model, ad-hoc reports based on model, and I also have canned reports built through BIDS
report server project.
•I reconfigured both databases' Compatibility level to SQL Server 2012(110) from SQL Server 2008(100).
•I configured SSRS through Reporting Services Configuration Manager as below:
> I chosen "Use built-in account:" as Service Account
> In "Database" tab, I selected "Choose an existing report server database" and choose "ReportServer2008To2012" db, I used "Windows Authentication" (my login has the System Administrator priviledge). I got all 4 parts
success: Verifying database sku = Success; Generating rights scripts = Success; Applying connection rights = Success; Setting DSN = Success.
> I went to "Scale-out Deployment" to check if the initializing succeed, I found nothing there.
Here are what I did from different approaches:
A •I went to "Encryption Keys" and restored the key I backed up from SSRS 2008, after retoring, I got two initialized instances: One is on my current server (SSRS 2012), the other one is from the old server (SSRS 2008).
   I deleted the old one(SSRS 2008) through "Remove Server" action and kept the one on my current server(SSRS 2012).
   After I restart SSRS service, and tried to connect Report Manager, I got "An internal error occurred on the report server. See the error log for more details."
   I checked the log file, the error is actually "ERROR: Software Usage Metrics initialize failed"
B •I also tried to "Delete Encrypted Content" and did see the SSRS was initialized through checking it on "Scale-out Deployment", however when I tried to open Report Manager, I got the same error.
Anyone had the same issue? Any solution? Thanks in advance!

Your help is highly appreciated!
After migrating ReportServer db from 2008 to 2012, when access Report Manager through
http://myserver:80/Reports, I got the error below:
ui!ReportManager_0-3!11d8!02/04/2013-15:19:12:: e ERROR: Software Usage Metrics initialize failed
The process is below:
•I successfully installed SQL Server 2012 (64-bit) Enterprise as a Native Mode on a server who runs Windows 7 Enterprise SP1 (64-bit).
•I restored "ReportServer2008To2012" and "ReportServer2008To2012TempDB" in SSRS 2012 from the db files backed up in SQL 2008. In SSRS 2008, I have SSRS Model, ad-hoc reports based on model, and I also have canned reports built through BIDS
report server project.
•I reconfigured both databases' Compatibility level to SQL Server 2012(110) from SQL Server 2008(100).
•I configured SSRS through Reporting Services Configuration Manager as below:
> I chosen "Use built-in account:" as Service Account
> In "Database" tab, I selected "Choose an existing report server database" and choose "ReportServer2008To2012" db, I used "Windows Authentication" (my login has the System Administrator priviledge). I got all
4 parts success: Verifying database sku = Success; Generating rights scripts = Success; Applying connection rights = Success; Setting DSN = Success.
> I went to "Scale-out Deployment" to check if the initializing succeed, I found nothing there.
Here are what I did from different approaches:
A •I went to "Encryption Keys" and restored the key I backed up from SSRS 2008, after retoring, I got two initialized instances: One is on my current server (SSRS 2012), the other one is from the old server (SSRS 2008).
   I deleted the old one(SSRS 2008) through "Remove Server" action and kept the one on my current server(SSRS 2012).
   After I restart SSRS service, and tried to connect Report Manager, I got "An internal error occurred on the report server. See the error log for more details."
   I checked the log file, the error is actually "ERROR: Software Usage Metrics initialize failed"
B •I also tried to "Delete Encrypted Content" and did see the SSRS was initialized through checking it on "Scale-out Deployment", however when I tried to open Report Manager, I got the same error.
Anyone had the same issue? Any solution? Thanks in advance!

EAS 9.3.1 Error - Cannot connect to database

Hello. I am experiencing a connectivity issue with executing business rules in EAS. I can execute the business rule correctly, at first; however, if I attempt to execute the same rule a second time, the following error message is displayed:
*"You must be connected to a database to execute the rule"*
The inactivity limit is not the issue since I attempt to run the rule back-to-back and receive the error message. This occurs if I execute the same business rule or different business rules.
The issue has only surfaced recently...perhaps a few weeks. Prior to that, I was able to execute multiple rules, one after the next, with no problem.
Can anybody assist me?
Thanks so much!

You can have a look on these bug reports at digikam directly:
https://bugs.kde.org/show_bug.cgi?id=282047
https://bugs.kde.org/show_bug.cgi?id=281767#c13
https://bugs.kde.org/show_bug.cgi?id=281838
They have the same issue as you. I have discovered the same, but helped me to set the database directory manually by command line parameter to my Pictures directory which contains digikam.db

DPM 2012 R2 unable to connect to Database after failed Update Rollup 4 Installation

We have a DPM 2012 R2 Server with SQL Server 2012 installed locally.
We tried to install Rollup 4 for DPM 2012 R2 (KB3009516) using Windows Update
and it failed with error code 0x80070643. Now when we open the DPM Console
it is totally empty (no Protection Groups, Servers, Disks, just like a fresh install).
In the eventlog we get a lot of Errors and warnings:
Event 941 (MSDPM)
Unable to connect to the DPM database. Make sure that SQL Server is running and that it is configured correctly.
Cannot open database "DPMDB" requested by the login. The login failed.
Event 4209 (MSDPM)
The description for Event ID 4209 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
DPM Writer encountered an internal error. Please restart the DPM Writer service, and then try the backup operation again. For additional troubleshooting information, review the application event log and the DPM Troubleshooting Guide.
Event 107 (Report Server Windows Service (MSSQLSERVER)
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
Event 274 (SQLISService110)
Microsoft SSIS Service:
Registry setting specifying configuration file does not exist.
Attempting to load default config file.
Then there are some Errors/warnings from SQLSERVERAGENT about failed scheduled Jobs.
I think the failed Installation changed some database Settings, so that now the DPM Console
cant access the database anymore.
I would be happy if someone can help me getting this Server working again!

Our biggest problem is, that the DPM is not working any more. So there is no chance to backup the SQL Server via DPM.
I think the main problem is that DPM have no access to the database. Every time I start the DPM Application, I get an error "verify that the DPM service is running on this computer". In the eventlog are many errors that the msdpm service was unable
to connect to DPM Database. Another "information" is that the user 'nt authority\system' failed to open the database of dpm.
We've tried to reinstall the DPM but its still the same problem. I suppose that is a corrupt database.
Tomorrow I try to restore the database and hope it will be the solution of our problem.

Error "no connect to database " after moving group to second node.

Similar Messages

Maybe you are looking for