SMC 4.0 setup database failed
Hi,
I'm trying to install SMC 4.0 on Sun V240 having Solaris 10 with release 10/09. The physical memory on the machine is 3 GB. Installation of SMC completes successfully but the setup fails with error message "Database setup failed : db-start failed".
copying template1 to postgres ... ok
WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the -A option the
next time you run initdb.
Success. You can now start the database server using:
postmaster -D /var/opt/SUNWsymon/db/data/SunMC
or
pg_ctl -D /var/opt/SUNWsymon/db/data/SunMC -l logfile start
createdb: could not connect to database postgres: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5433?
Started /var/opt/SUNWsymon/install/guibased-setup.1258931301102.sh at Mon Nov 23 12:11:38 NZDT 2009.
Running on SunOS wgls07.nz.thenational.com 5.10 Generic_141444-09 sun4u sparc SUNW,Sun-Fire-V240.
psql: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5433?
createlang: could not connect to database sunmc: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5433?
psql: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5433?After some digging I made an update in /var/opt/SUNWsymon/db/data/SunMC/postgresql.conf, chaging the line listen_address from *'{localhost, 127.0.0.1}'* to '(asterisk)' +[I had to use, in this post, the word asterisk insterad of teh character, which was activating the bold format]+ . This fixed the database manual startup. Running the setup script again removes the changes I made and the problem returns.
My network configuration is:
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
lo0:1: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
zone wglsdb2
inet 127.0.0.1 netmask ff000000
lo0:2: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
zone wglsdb1
inet 127.0.0.1 netmask ff000000
bge0: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 2
inet 10.64.86.27 netmask ffffff00 broadcast 10.64.86.255
groupname ipmp-test
ether 0:3:ba:e8:65:9
bge0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 10.64.86.36 netmask ffffff00 broadcast 10.64.86.255
bge0:2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
zone wglsdb2
inet 10.64.86.101 netmask ffffff00 broadcast 10.64.86.255
bge0:3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
zone wglsdb1
inet 10.64.86.100 netmask ffffff00 broadcast 10.64.86.255
bge1: flags=19040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,FAILED> mtu 1500 index 3
inet 10.64.86.28 netmask ffffff00 broadcast 10.64.86.255
groupname ipmp-test
ether 0:3:ba:e8:65:a
bge2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
inet 10.64.87.20 netmask ffffff00 broadcast 10.64.87.255
ether 0:3:ba:e8:65:bSystem is still using the */etc/pam.conf* file that comes with Sol10.
Request if someone can help on how to setup the SMC 4.0.
Cheers,
Andreas
Edited by: Bank_Of_New_Zealand on 23/11/2009 14:21
Hello Pegah
Even after that change, is still not working. Any more ideas?
# cat /etc/project
system:0::::
user.root:1::::
noproject:2::::
#default:3::::
default:3::::poject.max-shm-memory=(priv,1073741824,deny)
group.staff:10::::
# prtdiag|grep Memory\ size
Memory size: 3GB
# DISPLAY=10.68.66.16:0.0 /opt/SUNWsymon/sbin/es-guisetup &
[1] 16681
# Nov 25 08:24:04 wgls07.nz.thenational.com svc.startd[7]: application/management/sunmcdatabase:default failed repeatedly: transitioned to maintenance (see 'svcs -xv' for details)
# tail /var/opt/SUNWsymon/install/gui_setup_wgls07.nz.thenational.com.091125082050
Successfully disabled service sunmc-webserver
Stopping agent component
Successfully disabled service sunmc-agent
Stopping platform component
Successfully disabled service sunmc-platform
verifyDatabaseDown: instance is not executing
Successfully enabled service sunmc-database
Please wait, Sun Management Center database setup in progress. It may take 5 minutes...
Database setup failed : See the logfile /var/opt/SUNWsymon/install/core-db-setup_wgls07.nz.thenational.com.091125082357.17266
# cat /var/opt/SUNWsymon/install/core-db-setup_wgls07.nz.thenational.com.091125082357.17266
Started /var/opt/SUNWsymon/install/guibased-setup.1259090629094.sh at Wed Nov 25 08:23:57 NZDT 2009.
Running on SunOS wgls07.nz.thenational.com 5.10 Generic_141444-09 sun4u sparc SUNW,Sun-Fire-V240.
The files belonging to this database system will be owned by user "smcdbu".
This user must also own the server process.
The database cluster will be initialized with locale C.
creating directory /var/opt/SUNWsymon/db/data/SunMC ... ok
creating directory /var/opt/SUNWsymon/db/data/SunMC/global ... ok
creating directory /var/opt/SUNWsymon/db/data/SunMC/pg_xlog ... ok
creating directory /var/opt/SUNWsymon/db/data/SunMC/pg_xlog/archive_status ... ok
creating directory /var/opt/SUNWsymon/db/data/SunMC/pg_clog ... ok
creating directory /var/opt/SUNWsymon/db/data/SunMC/pg_subtrans ... ok
creating directory /var/opt/SUNWsymon/db/data/SunMC/pg_twophase ... ok
creating directory /var/opt/SUNWsymon/db/data/SunMC/pg_multixact/members ... ok
creating directory /var/opt/SUNWsymon/db/data/SunMC/pg_multixact/offsets ... ok
creating directory /var/opt/SUNWsymon/db/data/SunMC/base ... ok
creating directory /var/opt/SUNWsymon/db/data/SunMC/base/1 ... ok
creating directory /var/opt/SUNWsymon/db/data/SunMC/pg_tblspc ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 1000
creating configuration files ... ok
creating template1 database in /var/opt/SUNWsymon/db/data/SunMC/base/1 ... ok
initializing pg_authid ... ok
setting password ... ok
enabling unlimited row size for system tables ... ok
initializing dependencies ... ok
creating system views ... ok
loading pg_description ... ok
creating conversions ... ok
setting privileges on built-in objects ... ok
creating information schema ... ok
vacuuming database template1 ... ok
copying template1 to template0 ... ok
copying template1 to postgres ... ok
WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the -A option the
next time you run initdb.
Success. You can now start the database server using:
postmaster -D /var/opt/SUNWsymon/db/data/SunMC
or
pg_ctl -D /var/opt/SUNWsymon/db/data/SunMC -l logfile start
createdb: could not connect to database postgres: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5433?
Started /var/opt/SUNWsymon/install/guibased-setup.1259090629094.sh at Wed Nov 25 08:27:19 NZDT 2009.
Running on SunOS wgls07.nz.thenational.com 5.10 Generic_141444-09 sun4u sparc SUNW,Sun-Fire-V240.
psql: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5433?
createlang: could not connect to database sunmc: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5433?
psql: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5433?Cheers
Andreas
Edited by: Bank_Of_New_Zealand on 25/11/2009 09:34
Similar Messages
-
Dear All ,
I try install smc 4.0 on another sun box ,the reason for test CCR problem from on t2000 box ,I use same file which use for install smc on t2000 , but on step es-setup i got the problem (db-start failed).Here the log installation :
Initiating setup for Sun Management Center Agent Component.
This part of the setup process does the Sun Management Center Agent Component setup.
Started /opt/SUNWsymon/lib/sbin/sm_setup_agent.sh at Thu Nov 8 20:16:52 BNT 2007.
Running on SunOS sun240 5.10 Generic_120011-14 sun4u sparc SUNW,Sun-Fire-V240.
Copying snmpd.conf file into /var/opt/SUNWsymon/cfg
Server component also installed locally.
Using this machine as the Sun Management Center server.
---------------------------- WARNING ---------------------------
It appears that agent.snmpPort 161 is already in use.
Sun Management Center 4.0 agent may not be able to run due to this conflict.
There are two ways to correct this conflict:
1. Reconfigure the port that Sun Management Center 4.0 uses.
2. Stop the process that is using the port.
Press RETURN to force default port.
Enter port you would like to use [ 1100 to 65535 ]: 1161
Updating /var/opt/SUNWsymon/cfg/domain-config.x with new port number.
Generating agent security keys.
PKCS11 Utilities package(SUNWcsl) was found.
Encrypted SNMP Communication is supported.
Setup of Agent component is successful.
Starting Sun Management Center database setup...
verifyDatabaseDown: instance is not executing
Database consistency information missing.
Configuring database initialization parameter file
Stopping metadata component
Successfully disabled service sunmc-metadata
Stopping cfgserver component
Successfully disabled service sunmc-cfgserver
Stopping topology component
Successfully disabled service sunmc-topology
Stopping event component
Successfully disabled service sunmc-event
Stopping grouping service
Successfully disabled service sunmc-grouping
Stopping trap component
Successfully disabled service sunmc-trap
Stopping java server
Successfully disabled service sunmc-javaserver
Stopping webserver
Successfully disabled service sunmc-webserver
Stopping agent component
Successfully disabled service sunmc-agent
Stopping platform component
Successfully disabled service sunmc-platform
verifyDatabaseDown: instance is not executing
Failed to enable service sunmc-database
Database setup failed : db-start failed
Updating registry...
As database is not setup, Marking server setup as failed in Registry.
None of the base layers are setup.
No Addon is setup.
Following Addons are not yet setup: Advanced System Monitoring,ELP Config-Reader Monitoring,Desktop,Service Availability Manager,Sun Fire Entry-Level Midrange System,Performance Reporting Manager,Solaris Container Manager,System Reliability Manager,Workgroup Server
Could not finish requested task.
I am already uninstall(use uninstall script ) and reinstall back , but the result is same , Does any one know how to solve this problem ?
Regards
hadiGreetings,
I've not been able to resolve the topology issues, the recommended fixes have not resolved my issues. Upon un-installaing and re-installing multiple times I'm still not able to get the topology component to initialize correctly. The Management Center does display in the Applications listing in the Java Web Console (3.0.2) however clicking on it and displaying the main page for the Management Center 4.0 displays just a few items in the left nav, and none of the 'Discover Systems' requests make it in the queue or work at all. None of the other Management modules are displayed either. The web start console refuses to connect to the server as well, replying with a 'Server communication error, the server version may be incompatible' error.
I've noticed quite a bit of sql errors in the install, I've not seen anything in the release notes or forums regarding this issue either. Any help on this would be greatly appreciated! SMA and snmpdx are both disabled as well as dmi services.
The server is x86 Dell 2950, Entire install of Solaris 10 U3 11/06. Agent, Server, and Console components are installed and setup.
*/etc/project:*
system:0::::
user.root:1::::
noproject:2::::
default:3::::project.max-shm-memory=(priv,5368708912,deny)
group.staff:10::::
from */var/adm/messages:*
Dec 19 12:19:21 dvall topology[963]: [ID 840589 daemon.alert] syslog Dec 19 12:19:21 topology parsing error in file://localhost/topology-license-d.x;flags=ro(13):
Dec 19 12:19:21 dvall topology[963]: [ID 259113 daemon.alert] syslog Dec 19 12:19:21 topology *** aborting execution ***
install log:
Started ./es-inst at Wed Dec 19 11:50:19 PST 2007.
Running on SunOS dvall 5.10 Generic_125101-07 i86pc i386 i86pc.
This script installs Sun (TM) Sun Management Center 4.0
Installation files source directory: /root/src/SunMC/disk1/image/SunOS/i386
Copying required XML APIs from /root/src/SunMC/disk1/sbin/bin/i386-sun-solaris10 to /var/run/tmp/SunMCInstall/XML/APIs
Enter the directory in which you want to install: [ /opt ] /opt/SunMC/
Installation destination directory: /opt/SunMC
Select the Sun Management Center 4.0 components to install:
3 component(s) are available for your selection:
Do you want to install the Server component (y|n|q) y
Note: The Agent component will be installed automatically.
Do you want to install the Console component (y|n|q) y
Looking for valid JDK.
Found incomplete installation of : "1.6.0_03-b05"
SYMON_JAVAHOME is set to: /usr/java
JDK version is: "1.6.0_03-b05"
JDK check OK.
Looking for Tomcat Webserver.
Webserver check OK.
You must agree to the above license agreement to proceed with installation.
Do you agree (y|n|q) y
Sun Management Center 4.0 can be installed in the following languages:
Traditional Chinese
Simplified Chinese
French
Japanese
Korean
English is installed by default.
Are other languages required (y|n|q) n
Reading Add-On products from image. Please wait...
This can take approximately 3 minutes to complete.
Found: Sun Management Center Integration for Unicenter TNG
Found: Advanced System Monitoring
Found: System Reliability Manager
Found: Generic X86/X64 Config Reader
Found: Solaris Container Manager
Found: Service Availability Manager
Found: Performance Reporting Manager
Checking for applicable products. Please wait...
This can take approximately 2 minutes to complete.
Unable to find package directory for SUNWeshsm
Component script found: check-remote-install.sh
Running: /root/src/SunMC/disk1/image/SunOS/i386/Addons/TNG/Solaris_10/Basic//check-remote-install.sh
Return value: 1
Component script found: check-remote-install.sh
Running: /root/src/SunMC/disk1/image/SunOS/i386/Addons/TNG/Solaris_10/Basic//check-remote-install.sh
Return value: 1
Component script found: check_TNG_Server.sh
check if TNG Server is installed.
Cannot install the Unicenter TNG addon Server component. CA-TNG is not installed, you should install CA-TNG first.
Running: /root/src/SunMC/disk1/image/SunOS/i386/Addons/TNG/Solaris_10/Basic//check_TNG_Server.sh
Return value: 2
Script returned 2. Skipping this component.
Component script found: gca-check.sh
Running: /root/src/SunMC/disk1/image/SunOS/i386/Addons/X86ConfigReader/Solaris_10/Basic//gca-check.sh
Return value: 1
The Sun Management Center 4.0 Production environment will be installed.
The following Add-On Products are applicable for installation.
Advanced System Monitoring
Service Availability Manager
Performance Reporting Manager
Solaris Container Manager
System Reliability Manager
Sun Management Center Integration for Unicenter TNG
Generic X86/X64 Config Reader
Do you want to select all the products (y|n|q) n
Select the products you want to install:
Advanced System Monitoring (y|n|q) y
Service Availability Manager (y|n|q) y
Performance Reporting Manager (y|n|q) y
Solaris Container Manager (y|n|q) y
System Reliability Manager (y|n|q) y
Sun Management Center Integration for Unicenter TNG (y|n|q) n
Generic X86/X64 Config Reader (y|n|q) y
The following Add-On Products will be installed:
Advanced System Monitoring
Service Availability Manager
Performance Reporting Manager
Solaris Container Manager
System Reliability Manager
Generic X86/X64 Config Reader
Do you want to proceed (y|n|q) y
The following Add-On products are covered under license agreement:
You must agree to the above license agreement to proceed with installation.
Do you agree (y|n|q) y
Disk Space Checking....
Installing the components...
Installing... PRODUCT.PE COMPONENT.AGENT
Processing package instance <SUNWescom> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Common Components(i386) 4.0,REV=2.10.2007.10.23
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
Installing Sun Management Center Common Components as <SUNWescom>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
2426 blocks
## Executing postinstall script.
Installation of <SUNWescom> was successful.
Processing package instance <SUNWenesi> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center script localization messages(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
1 package pathname is already properly installed.
Installing Sun Management Center script localization messages as <SUNWenesi>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
683 blocks
Installation of <SUNWenesi> was successful.
Processing package instance <SUNWesagt> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Agent(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
3 package pathnames are already properly installed.
Installing Sun Management Center Agent as <SUNWesagt>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
24750 blocks
## Executing postinstall script.
Installation of <SUNWesagt> was successful.
Processing package instance <SUNWesmib> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Mib Instance Module(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
4 package pathnames are already properly installed.
Installing Sun Management Center Mib Instance Module as <SUNWesmib>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
281 blocks
Installation of <SUNWesmib> was successful.
Processing package instance <SUNWesken> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Kernel Reader Module(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
5 package pathnames are already properly installed.
Installing Sun Management Center Kernel Reader Module as <SUNWesken>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
399 blocks
Installation of <SUNWesken> was successful.
Processing package instance <SUNWesmod> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Agent Modules(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
9 package pathnames are already properly installed.
Installing Sun Management Center Agent Modules as <SUNWesmod>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
235 blocks
Installation of <SUNWesmod> was successful.
Processing package instance <SUNWesae> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Agent System Files(i386) 4.0,REV=2.10.2007.10.15
Using </> as the package base directory.
## Processing package information.
## Processing system information.
9 package pathnames are already properly installed.
Installing Sun Management Center Agent System Files as <SUNWesae>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
28 blocks
## Executing postinstall script.
Installation of <SUNWesae> was successful.
Processing package instance <SUNWesaem> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Event Module for Agent(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
9 package pathnames are already properly installed.
Installing Sun Management Center Event Module for Agent as <SUNWesaem>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
186 blocks
Installation of <SUNWesaem> was successful.
Processing package instance <SUNWesgui> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center GUI Installation(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
7 package pathnames are already properly installed.
Installing Sun Management Center GUI Installation as <SUNWesgui>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
6250 blocks
Installation of <SUNWesgui> was successful.
Processing package instance <SUNWsuagt> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Dynamic Agent Update Agent Components(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
6 package pathnames are already properly installed.
Installing Sun Management Center Dynamic Agent Update Agent Components as <SUNWsuagt>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
152 blocks
Installation of <SUNWsuagt> was successful.
Processing package instance <SUNWesval> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Validation Tool Components(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
4 package pathnames are already properly installed.
Installing Sun Management Center Validation Tool Components as <SUNWesval>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
220 blocks
Installation of <SUNWesval> was successful.
Processing package instance <SUNWesaxp> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Java API for XML Processing (JAXP) v1.1.3(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Java API for XML Processing (JAXP) v1.1.3 as <SUNWesaxp>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
2362 blocks
Installation of <SUNWesaxp> was successful.
Processing package instance <SUNWesmcp> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Module Configuration Propagation(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
8 package pathnames are already properly installed.
Installing Sun Management Center Module Configuration Propagation as <SUNWesmcp>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
249 blocks
Installation of <SUNWesmcp> was successful.
Processing package instance <SUNWeslac> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Local Access(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
3 package pathnames are already properly installed.
Installing Sun Management Center Local Access as <SUNWeslac>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
14 blocks
Installation of <SUNWeslac> was successful.
Processing package instance <SUNWesafm> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center FMA Service Module for Agent(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
5 package pathnames are already properly installed.
Installing Sun Management Center FMA Service Module for Agent as <SUNWesafm>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
92 blocks
Installation of <SUNWesafm> was successful.
Package SUNWservicetagr is already installed on this system.
Validating the Registry entry.
Package SUNWservicetagu is already installed on this system.
Validating the Registry entry.
Package SUNWstosreg is already installed on this system.
Validating the Registry entry.
Installing... PRODUCT.PE COMPONENT.CONSOLE
Package SUNWescom is already installed on this system.
Validating the Registry entry.
Package SUNWenesi is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWescon> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Console(i386) 4.0,REV=2.9.2007.10.16
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
4 package pathnames are already properly installed.
Installing Sun Management Center Console as <SUNWescon>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
6638 blocks
Installation of <SUNWescon> was successful.
Processing package instance <SUNWesjp> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Additional Components(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Additional Components as <SUNWesjp>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
5819 blocks
Installation of <SUNWesjp> was successful.
Package SUNWesaxp is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWesclt> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Client API(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Client API as <SUNWesclt>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
1609 blocks
Installation of <SUNWesclt> was successful.
Processing package instance <SUNWesjrm> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Client API support classes(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Client API support classes as <SUNWesjrm>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
663 blocks
Installation of <SUNWesjrm> was successful.
Processing package instance <SUNWenesf> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Console properties(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Console properties as <SUNWenesf>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
557 blocks
## Executing postinstall script.
Installation of <SUNWenesf> was successful.
Package SUNWesgui is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWesasc> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Advanced Services Console(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Advanced Services Console as <SUNWesasc>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
156 blocks
Installation of <SUNWesasc> was successful.
Processing package instance <SUNWescix> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Import/Export(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Import/Export as <SUNWescix>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
156 blocks
Installation of <SUNWescix> was successful.
Processing package instance <SUNWsucon> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Dynamic Agent Update Console Components(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Dynamic Agent Update Console Components as <SUNWsucon>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
27 blocks
Installation of <SUNWsucon> was successful.
Processing package instance <SUNWescli> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Command Line Interface(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
5 package pathnames are already properly installed.
Installing Sun Management Center Command Line Interface as <SUNWescli>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
862 blocks
Installation of <SUNWescli> was successful.
Processing package instance <SUNWesclb> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Command Line Interface For BatchMode(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
4 package pathnames are already properly installed.
Installing Sun Management Center Command Line Interface For BatchMode as <SUNWesclb>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
155 blocks
Installation of <SUNWesclb> was successful.
Package SUNWesval is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWesmc> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center MCP Console(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
3 package pathnames are already properly installed.
Installing Sun Management Center MCP Console as <SUNWesmc>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
200 blocks
Installation of <SUNWesmc> was successful.
Processing package instance <SUNWescdv> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Console Dataview(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
3 package pathnames are already properly installed.
Installing Sun Management Center Console Dataview as <SUNWescdv>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
354 blocks
Installation of <SUNWescdv> was successful.
Installing... PRODUCT.PE COMPONENT.SERVER
Package SUNWescom is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWesbui> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Web Console(sparc) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
3 package pathnames are already properly installed.
Installing Sun Management Center Web Console as <SUNWesbui>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
7789 blocks
Installation of <SUNWesbui> was successful.
Processing package instance <SUNWesbuh> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Help(sparc) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Help as <SUNWesbuh>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
498 blocks
Installation of <SUNWesbuh> was successful.
Package SUNWenesi is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWesdb> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Database(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Database as <SUNWesdb>
## Executing preinstall script.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Group smcdbg created
User smcdbu created
## Installing part 1 of 1.
/opt/SunMC/SUNWsymon/base <conflicting pathname not installed>
/opt/SunMC/SUNWsymon/base/bin <conflicting pathname not installed>
/opt/SunMC/SUNWsymon/base/bin/i386-sun-solaris2.10 <conflicting pathname not installed>
/opt/SunMC/SUNWsymon/base/lib <conflicting pathname not installed>
/opt/SunMC/SUNWsymon/base/lib/i386-sun-solaris2.10 <conflicting pathname not installed>
/opt/SunMC/SUNWsymon/lib/sbin <conflicting pathname not installed>
/opt/SunMC/SUNWsymon/sbin <conflicting pathname not installed>
928 blocks
Installation of <SUNWesdb> was successful.
Package SUNWesagt is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWessrv> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Server(i386) 4.0,REV=2.9.2007.10.16
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
12 package pathnames are already properly installed.
Installing Sun Management Center Server as <SUNWessrv>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
10640 blocks
[ verifying class <preserve> ]
Installation of <SUNWessrv> was successful.
Processing package instance <SUNWessa> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Server/Agent(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
10 package pathnames are already properly installed.
Installing Sun Management Center Server/Agent as <SUNWessa>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
2218 blocks
Installation of <SUNWessa> was successful.
Package SUNWesjp is already installed on this system.
Validating the Registry entry.
Package SUNWesaxp is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWesse> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Server System Files(i386) 4.0,REV=2.10.2007.10.15
Using </> as the package base directory.
## Processing package information.
## Processing system information.
5 package pathnames are already properly installed.
Installing Sun Management Center Server System Files as <SUNWesse>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
36 blocks
## Executing postinstall script.
Installation of <SUNWesse> was successful.
Package SUNWesclt is already installed on this system.
Validating the Registry entry.
Package SUNWesjrm is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWmeta> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Metadata Agent(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
3 package pathnames are already properly installed.
Installing Sun Management Center Metadata Agent as <SUNWmeta>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
38 blocks
Installation of <SUNWmeta> was successful.
Package SUNWenesf is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWesmdr> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center MDR for Basic Pack(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
4 package pathnames are already properly installed.
Installing Sun Management Center MDR for Basic Pack as <SUNWesmdr>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
246 blocks
Installation of <SUNWesmdr> was successful.
Package SUNWesgui is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWesweb> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Web Console(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management C -
Error message: "Querying or saving changes to the database failed."
Hi all,
I can sense I'm becoming a regular on this particular forum - the problem of spending 8 hours a day trying to get this software working!
_*The problem*_
When i try and setup a new device, or modify an existing one, I get an error message when i get to the Transcode Settings page. The error message is "Querying or saving changes to the database failed." After this I get a blank screen and can no longer see my settings.
No amount of restarting has fixed this. And I cannot see a way to create a device through the client software and add transcode settings.
Help?
Thanks in advance,
BenAh very good!
Ok - it seems then that this works absolutely fine as a work around. I can create a device and then assign the device to transcode settings through the client adminsitration panel (which is indeed what I meant).
So, there is a work around. Far less pressing now, but I would like to know why I'm getting the error message all the same - I'm now concerned about the integrity of the database...
Thanks Tony!
B -
Auto-Setup Emails Fail with kGotAuthenticationFailure
If I set up my people with a shortname of "first.last", the auto-setup email fails to work when they click the setup button with "kGotAuthenticationFailure."
I do the dot in the shortname to facilitate more organized email addresses. I could do this by adding an alias, but I've found this confuses users as some services (like the wiki) only accept the true shortname.
I would really like for the auto-setup emails to work. Any suggestions for a fix?Are the client Macs all created from a central image? If so, yes, it's a Kerberos key failure. The local KDCs need to be flushed from the image or from each Mac before you do your bind. Also good idea to discard the system keychain while you're at it.
Here's a simple sh script to do it.
#!/bin/sh
\# Delete System Keychain
rm -rf /Library/Keychains/System.keychain
\# Delete the local KDC database
rm -rf /var/db/krb5kdc
\# Regenerate the local KDC
/usr/libexec/configureLocalKDC
Message was edited by: thesunnyape
Message was edited by: thesunnyape -
If anyone is able to solve this they are a genius (or I am doing something very stupid!)
I am trying to reinstall CS5.5 Master Collection from DVD media on Windows 7 64 bit PC but setup.exe fails due to a msxml3.dll error.
Following a big bundle of recent Windows 7 updates, I started getting 'bad image' msxml3.dll error messages when opening any CS5.5 master collection program (Eg Premiere / Photoshop / Illustrator / Dreamweaver). Following advice on some threads here I tried uninstalling and then using the Adobe CC Cleaner Tool to clean up install, then reinstalling from my original DVD media.
Whenever I try using run setup.exe from installtion disc 1 the installing fails due to 'Missing files'. I have also tried dowloading trial versions and runing setup.exe fro mthe downloaded files but i still get the same message.
I have searched the forum and others have experienced this error but none of the solutions I have found seem to be working for me - as many seem to relate to download installations whereas I am installing from original DVD media (which worked fine before on the same PC)
These are the FATAL messages from the PDApp log
12/11/2014 15:29:27 [FATAL] PIM - Failed to Create XML instance : DOMDocument40 ADXML::initWithXMLPath Error:80040154
12/11/2014 15:29:27 [FATAL] Setup - Could not initialize ADXML object
12/11/2014 15:29:27 [FATAL] Setup - Unable to initialize. Error parsing setup.xml file
The PDApp troubleshooting seems to indicate that this is caused by error in downloads but I am getting it with both original media DVD and downloads.
I have also tried using my logon (which has admin privileges) and under our main admin account - and I get the same errors.
Is a clean install of Windows 7 + CS5.5 my only option?
Any help / info / advice / solutions very much appreciated! I have spent the last 2 days trying to sort this out and seem to be getting nowhere.
Thanks.Thanks for the reply kglad - much appreciated.
I have already tried that option (along with downloading files) as it was one of the solutions mentioned on other threads, but that also failed.
Any other ideas? -
Connect to database failed,rc=-10709 Connection failed (RTE:Database name)
Hi gurues, I'm facing this issue with an IDES on MaxDB with Windows.
System was up and running until someone tries to make an upgrade of the kernel. Since then we can not start our system. we tried to rollback kernel release to the previous one but it didn't work.
When we start our system from MMC console we can see all process in green but work processes are in RUN state and after a few minutes they goes down with the following error
trc file: "dev_w0", trc level: 1, release: "701"
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, MJ
B
B Mon May 16 23:57:31 2011
B create_con (con_name=R/3)
B Loading DB library '
sirillium1\sapmnt\SED\SYS\exe\uc\NTAMD64\dbsdbslib.dll' ...
B Library '
sirillium1\sapmnt\SED\SYS\exe\uc\NTAMD64\dbsdbslib.dll' loaded
B Version of '
sirillium1\sapmnt\SED\SYS\exe\uc\NTAMD64\dbsdbslib.dll' is "700.08", patchlevel (0.24)
B New connection 0 created
M sysno 00
M sid SED
M systemid 562 (PC with Windows NT)
M relno 7010
M patchlevel 0
M patchno 32
M intno 20020600
M make: multithreaded, Unicode, 64 bit, optimized
M pid 212
M
M kernel runs with dp version 241000(ext=110000) (@(#) DPLIB-INT-VERSION-241000-UC)
M length of sys_adm_ext is 576 bytes
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 212) [dpxxdisp.c 1348]
I MtxInit: 30000 0 0
M DpSysAdmExtCreate: ABAP is active
M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
M DpShMCreate: sizeof(wp_adm) 22784 (1752)
M DpShMCreate: sizeof(tm_adm) 5912704 (29416)
M DpShMCreate: sizeof(wp_ca_adm) 24064 (80)
M DpShMCreate: sizeof(appc_ca_adm) 8000 (80)
M DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080
M DpShMCreate: sizeof(comm_adm) 552080 (1088)
M DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
M DpShMCreate: sizeof(slock_adm) 0 (104)
M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
M DpShMCreate: sizeof(file_adm) 0 (72)
M DpShMCreate: sizeof(vmc_adm) 0 (1864)
M DpShMCreate: sizeof(wall_adm) (41664/36752/64/192)
M DpShMCreate: sizeof(gw_adm) 48
M DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000B2C0050, size: 6607136)
M DpShMCreate: allocated sys_adm at 000000000B2C0050
M DpShMCreate: allocated wp_adm at 000000000B2C2270
M DpShMCreate: allocated tm_adm_list at 000000000B2C7B70
M DpShMCreate: allocated tm_adm at 000000000B2C7BD0
M DpShMCreate: allocated wp_ca_adm at 000000000B86B450
M DpShMCreate: allocated appc_ca_adm at 000000000B871250
M DpShMCreate: allocated comm_adm at 000000000B873190
M DpShMCreate: system runs without slock table
M DpShMCreate: system runs without file table
M DpShMCreate: allocated vmc_adm_list at 000000000B8F9E20
M DpShMCreate: allocated gw_adm at 000000000B8F9EA0
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 000000000B8F9ED0
M DpShMCreate: allocated wall_adm at 000000000B8F9EE0
M
M Mon May 16 23:57:32 2011
M rdisp/queue_size_check_value : -> off
M ThTaskStatus: rdisp/reset_online_during_debug 0
X EmInit: MmSetImplementation( 2 ).
X MM global diagnostic options set: 0
X <ES> client 0 initializing ....
X Using implementation view
X <EsNT> Using memory model view.
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
M ThInit: running on host sirillium1
M
M Mon May 16 23:57:33 2011
M calling db_connect ...
C
C DBSDBSLIB : version 700.08, patch 0.024 (Make PL 0.32)
C MAXDB shared library (dbsdbslib) patchlevels (last 10)
C (0.024) Default value for max. input variables is 2000 (note 655018)
C (0.024) Profile parameter to define max. input variables (note 655018)
C (0.024) Switch SQLMODE after CREATE INDEX SERIAL (note 1267841)
C (0.024) Input parameters for SQL statements increased (note 655018)
C (0.018) Create index serial for MaxDB 7.6 (note 1267841)
C (0.018) More trace in case of packed to string conversion error (note 1262799)
C (0.016) R3trans export aborts with signal 6 (note 1262245)
C (0.009) IA64 alignment errors (note 1245982)
C (0.007) Support DB-Type 'SAP DB' by UPDSTAT (note 1225668)
C
C
C Loading SQLDBC client runtime ...
C SQLDBC SDK Version : SQLDBC.H 7.6.0 BUILD 007-123-091-175
C SQLDBC Library Version : libSQLDBC 7.6.5 BUILD 015-123-202-938
C SQLDBC client runtime is MaxDB 7.6.5.015 CL 202938
C SQLDBC supports new DECIMAL interface : 0
C SQLDBC supports VARIABLE INPUT data : 1
C SQLDBC supports keepAlive indicator : 0
C INFO : SQLOPT= -I 0 -t 0 -S SAPR3
C Try to connect (DEFAULT) on connection 0 ...
C *** ERROR => Connect to database failed, rc = -10709 (Connection failed (RTE:Database name is missing))
[dbsdbsql.cpp 137]
B ***LOG BV3=> severe db error -10709 ; work process is stopped [dbsh#2 @ 1203] [dbsh 1203 ]
B ***LOG BY2=> sql error -10709 performing CON [dblink#3 @ 431] [dblink 0431 ]
B ***LOG BY0=> Connection failed (RTE:Database name is missing) [dblink#3 @ 431] [dblink 0431 ]
M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c 1449]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 10563]
M
M Info for wp 0
M
M pid = 212
M severity = 0
M status = 0
M stat = WP_RUN
M waiting_for = NO_WAITING
M reqtype = DP_RQ_DIAWP
M act_reqtype = NO_REQTYPE
M rq_info = 0
M tid = -1
M mode = 255
M len = -1
M rq_id = 65535
M rq_source =
M last_tid = 0
M last_mode = 0
M semaphore = 0
M act_cs_count = 0
M csTrack = 0
M csTrackRwExcl = 0
M csTrackRwShrd = 0
M mode_cleaned_counter = 0
M control_flag = 0
M int_checked_resource(RFC) = 0
M ext_checked_resource(RFC) = 0
M int_checked_resource(HTTP) = 0
M ext_checked_resource(HTTP) = 0
M report = > <
M action = 0
M tab_name = > <
M attachedVm = no VM
M
M *****************************************************************************
M *
M * LOCATION SAP-Server sirillium1_SED_00 on host sirillium1 (wp 0)
M * ERROR ThInit: db_connect
M *
M * TIME Mon May 16 23:57:33 2011
M * RELEASE 701
M * COMPONENT Taskhandler
M * VERSION 1
M * RC 13
M * MODULE thxxhead.c
M * LINE 10783
M * COUNTER 1
M *
M *****************************************************************************
M
M PfStatDisconnect: disconnect statistics
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >BtcCallLgCl< for event BEFORE_DUMP
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 723]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 261]
M Entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 212) [dpnttool.c 334]
We check several entries on this SDN site, and look for a lot of notes on the marketplace, and they always are related to default user in xuser files, but our xuser list output is ok. We have a DEFAULT connection to SAPSID user, a DBM connection to CONTROL user and a USERDBA connection.
XUSER Entry 1
Key :DEFAULT
Username :SAPSID
UsernameUCS2:S.A.P.S.E.D. . . . . . . . . . . . . . . . . . . . . . . . . . .
Password :?????????
PasswordUCS2:?????????
Dbname :SID
Nodename :server1
Sqlmode :SAPR3
Cachelimit :-1
Timeout
Isolation
Charset :<unspecified>
XUSER Entry 2
Key :c
Username :CONTROL
UsernameUCS2:C.O.N.T.R.O.L. . . . . . . . . . . . . . . . . . . . . . . . . .
Password :?????????
PasswordUCS2:?????????
Dbname :SID
Nodename :server1
Sqlmode :INTERNAL
Cachelimit :-1
Timeout :-1
Isolation :-1
Charset :<unspecified>
XUSER Entry 3
Key :c_J2EE
Username :CONTROL
UsernameUCS2:C.O.N.T.R.O.L. . . . . . . . . . . . . . . . . . . . . . . . . .
Password :?????????
PasswordUCS2:?????????
Dbname :SID
Nodename :server1
Sqlmode :SAPR3
Cachelimit :-1
Timeout
Isolation
Charset :<unspecified>
XUSER Entry 4
Key :w
Username :SUPERDBA
UsernameUCS2:S.U.P.E.R.D.B.A. . . . . . . . . . . . . . . . . . . . . . . . .
Password :?????????
PasswordUCS2:?????????
Dbname :SID
Nodename :server1
Sqlmode :INTERNAL
Cachelimit :-1
Timeout :-1
Isolation :-1
Charset :<unspecified>
Any idea? we are out of ideas at this moment.
Regards
Edited by: Gustavo Goicochea on May 17, 2011 6:37 PMNatalia, this system was not resored nor copied, it was up and running before kernel update. We did some of the tests you said and someothers, here are some outputs.
We update kernel to release 142
R3trans -d and -x exit with (all with user SIDADM)
SVERS table does exist and belongs to SAPSID
dbmcli on SID>sql_execute select * from domain.tables where tablename='SVERS'
OK
END
'SAPSID';'SAPSID';'SVERS';'';'TABLE';'TABLE';'20100406';'00054637';'20100406';'00054637';'20100406';'00054638';'NO';(null);20000;(null);x'0000000000004842';'NO';'NO';'YES';'NO';(null)
Why it still says that SVERS table does not exist and SQL error 942?
C Now I'm connected to SAP DB
C 00: server1-SID, since=20110518015619, ABAP= <unknown> (0)
B Connection 0 opened (DBSL handle 0)
C *** ERROR => prepare() of C_0000, rc=1, rcSQL=-942 (POS(28) Unknown table name:SVERS) [
dbsdbsql.cpp 1604]
C *** ERROR => SQL PREPARE on connection 0, rc=-942 (POS(28) Unknown table name:SVERS) [dbslsdb.cpp 7253]
C sc_p=000000000CFAECC0,no=0,idc_p=0000000000000000,con=0,act=0,slen=34,smax=256,#vars=0,stmt=0000000002EA0AF0,table=SVERS
C SELECT VERSION INTO ? FROM SVERS ;
B ***LOG BZA=> table SVERS does not exist on database [dblink#4 @ 1301] [dblink 1301 ]
M ***LOG R19=> ThInit, db_connect ( DB-Connect 004096) [thxxhead.c 1515]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 10824]
M
Users seem to be ok
dbmcli on SID>sql_execute SELECT username, usermode FROM users
OK
END
'CONTROL';'ADMIN'
'SUPERDBA';'SYSDBA'
'SAPSID';'DBA'
'SAPR3';'DBA'
User SAPR3 does not have anything on database
dbmcli on SID>sql_execute select * from domain.tables where owner='SAPR3'
ERR
-24988,ERR_SQL: SQL error
100,Row not found
Any idea?
regards -
Error in /tmp/applianceagent/scripts/Database.sh: Start database failed with exit code 2
Hello
I have set up the Demo appliance landscape for the openSAP course "Introduction to SAP Fiori UX", on AWS.
The frontend machine is OK, but the configuration and startup of the server machine has failed for some reason. When logging in with ssh to the server, this message is presented:
The Appliance Agent detected an error and terminated.
When asked, please provide the file /tmp/applianceagent_20141002-145658.tar.bz2.
Note that a restrictive iptables based firewall is still active.
I have attached the file (had to add .txt to the name to circumvent file type restrictions).
I noticed that the appliancedeploy.log ended with these lines:
Start database Execute /usr/sap/hostctrl/exe/sapcontrol -nr 02 -function StartWait 3600 20
02.10.2014 13:56:58
Start
OK
02.10.2014 14:56:58
StartWait
FAIL: Timeout
error in /tmp/applianceagent/scripts/Database.sh: Start database failed with exit code 2
Notice the 1 hour jump in time, and then the timeout error message.
Do any of you have any idea what could be causing this, and how to fix it?
Please let me know if you need any further information.
Best regards,
BoHi Hannes.
Trying to create and activate a new instance (version 5 of the Fiori appliance), I first got this message in the CAL instance overview list:
Instance Operation Failed
Operation Start failed on step Start start VAs with message: Start failed for VM SAP Server due to Amazon Web Services issue : AMAZON : The snapshot 'snap-c779ff64' does not exist.
Then I terminated the instance and tried over again. And this time the deployment worked - I have a running server, which responds to the SAP GUI, and shows the Fiori web page.
Thanks a lot for your quick help.
Best regards,
Bo -
Constant failures in setting up scalable wordpress. Update ClearDB database failed.
I've been having Constant failures in setting up scalable wordpress with no luck on finding a fix.
Update ClearDB database failed is the most common issue, with Update deployment being the second issue. I though maybe it had to do with Azure changes over the last few months (beta portal), but have yet to successfully deploy a site.
Any suggestions / fixes would be greatly appreciated.
Also, i've tried utilizing the support link but it seems to hang perpetually (regardless of browser) when checking my subscription.Hi,
Two points need confirmed:
1.Have you already purse the ClearDB database?
2.What's error did you encounter when you scalable WP site?
Regards,
Will
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
Connection test to database failed: could not connect to server
I restarted one of my HPOV NNMi 9.23 servers this morning and NNMi is no longer loading. I am seeing the following errors in the logs indicated:
/var/opt/OV/log/nnm/public/nmsdbmgr.log
04/06/2015 09:28:05 AM Connection test to database failed: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?
/var/opt/OV/log/nnm/public/postgres.log
2015-04-06 09:25:55.312 EDT: :8580:0LOG: could not translate host name "localhost", service "5432" to address: Name or service not known
2015-04-06 09:25:55.312 EDT: :8580:0WARNING: could not create listen socket for "localhost"
2015-04-06 09:25:55.312 EDT: :8580:0FATAL: could not create any TCP/IP sockets
I checked /etc/hosts and found the following entry:
#; Local
127.0.0.1 localhost
From the command line I can ping localhost with no issue. Not sure why NNMi is not starting at this point.
This question was solved.
View Solution.I also attempted to do a reset using nnmresetebdb.ovpl. I recieved the following:
Attempting to reset the embedded database...
Starting nmsdbmgr process for database reset...
nmsdbmgr process did not restart successfully - please try reset again.
When I run ovstart -c I receive the following:
Name PID State Last Message(s)
OVsPMD 29831 RUNNING -
pmd 29832 RUNNING Initialization complete.
nmsdbmgr - NOT_RUNNING - Exit(1)
ovjboss - UNSTARTABLE -
nnmaction - UNSTARTABLE -
ovspmd: Attempt to start HP OpenView services is complete.
I definitely need some help with this please!
Thanks! -
Setup Database mail that connect with tcp/ip to the instance
I want to setup database mail that connect to the named instance via a fixed TCP/IP port.
This is a named instance that works with a fixed TCP/IP port
Database mail works fine if shared memory is enabled.
If it is disable I get the following log entry in the application log.
Log Name: Application
Source: DatabaseMail
Date: 18/11/2014 20:56:05
Event ID: 0
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Server.dom.be
Description:
1) Exception Information
===================
Exception Type: Microsoft.SqlServer.Management.SqlIMail.Server.Common.BaseException
Message: There was an error on the connection. Reason: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL
Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified), connection parameters: Server Name: server\instance, Database Name: msdb
Data: System.Collections.ListDictionaryInternal
TargetSite: Void OpenConnection(Microsoft.SqlServer.Management.Common.SqlConnectionInfo)
HelpLink: NULL
Source: DatabaseMailEngine
StackTrace Information
===================
at Microsoft.SqlServer.Management.SqlIMail.Server.DataAccess.ConnectionManager.OpenConnection(SqlConnectionInfo connectionInfo)
at Microsoft.SqlServer.Management.SqlIMail.Server.DataAccess.DataAccessAdapter.OpenConnection(String dbServerName, String dbName, String userName, String password, String appName, Int32 connectionTimeout)
at Microsoft.SqlServer.Management.SqlIMail.Server.DataAccess.DataAccessAdapter.OpenConnection(String dbServerName, String dbName, String userName, String password, Int32 connectionTimeout)
at Microsoft.SqlServer.Management.SqlIMail.IMailProcess.QueueItemProcesser.ProcessQueueItems(String dbName, String dbServerName, Int32 lifetimeMinimumSec, LogLevel loggingLevel, Byte[] encryptionKey, Int32 connectionTimeout)
Is there a way to change the connection parameters?
PS the Browser Service is not runningHello,
If the instance is a named instance, then SQL Server Browser service should be started to be able to connect to the instance
using TCP/IP.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Attached database failed for sever "blah". (Microsoft.SqlServer.Smo)
===================================
Attach database failed for Server 'DENR-HP'. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600.1+((KJ_RTM).100402-1539+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476
Program Location:
at Microsoft.SqlServer.Management.Smo.Server.AttachDatabase(String name, StringCollection files)
at Microsoft.SqlServer.Management.SqlManagerUI.AttachDatabaseData.PrimaryFile.Attach()
at Microsoft.SqlServer.Management.SqlManagerUI.AttachDatabase.SendDataToServer()
===================================
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Program Location:
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(StringCollection sqlCommands, ExecutionTypes executionType)
at Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQuery(StringCollection queries)
at Microsoft.SqlServer.Management.Smo.Server.AttachDatabaseWorker(String name, StringCollection files, String owner, AttachOptions attachOptions)
at Microsoft.SqlServer.Management.Smo.Server.AttachDatabase(String name, StringCollection files)
===================================
The database 'PlanningDB' cannot be opened because it is version 655. This server supports version 611 and earlier. A downgrade path is not supported.
Could not open new database 'PlanningDB'. CREATE DATABASE is aborted. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=948&LinkId=20476
Server Name: (local)
Error Number: 948
Severity: 20
State: 1
Line Number: 1
Program Location:
at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException)
at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException)
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)Hi,
As Olaf’s post, you cannot restore or attach a database which is created from a higher version of SQL Server to a lower version of SQL Server.
However, there are some ways which can help you to move a database to a lower version of SQL Server. I recommend you to use Generate Scripts Wizard of SQL Server Management Studio (SSMS), you can script all the database objects in SQL Server 2008, then run
the SQL scripts in SQL Server 2005, for more details, you can follow the steps in this blog:
How to migrate a SQL Server database to a lower version. Also you can try to use the Import and Export Wizard to move database from SQL Server 2008 to SQL Server 2005,for more details, please review this article:
How to: Run the SQL Server Import and Export Wizard.
Thanks
Lydia Zhang -
First-time install on a SBS 2011 server, name replaced as <SERVER> for this post. I had created a separate IIS site rather than using the Default Web Site and I am guessing this might be a permission issue on the folder...
Installation failed with Event ID 110 and a repeating error that states, "<Error>: Attempt to configure Active Directory Rights Management Server failed. The provisioning process failed to create the Configuration database due to the following
error from Sql Server: System.Data.SqlClient.SqlException: ALTER DATABASE failed because a lock could not be placed on database 'DRMS_Config_adrms_<SERVER>_local_443'. Try again later. ALTER DATABASE statement failed. ALTER DATABASE failed because a
lock could not be placed on database ." Configuration as follows:
<Informational>: This server might need to be restarted after the installation completes.
Active Directory Rights Management Services
Cluster Type
Root cluster
Trust Hierarchy
Production
Configuration Database Server
Windows Internal Database
Service Account
<SERVER>\adrms
Cluster Key Storage
AD RMS centrally managed key storage
Cluster Web Site
Active Directory RMS
Cluster Internal Address
https://adrms.<SERVER>.local:443/
SSL Certificate
Create a self-signed certificate
Licensor Certificate Name
<SERVER>
Register SCP
Register nowHi Ahmad, I have the same problem, I have a server windows server 2008 R2 standard. While
doing an Enterprise to Standard downgrade, I have removed enterprise edition of SQL Server 2008, rebooted and while installing standard edition, I get the below error saying "You SQL server 2008 installation completed with failures. Some or all identity
references could not be translated"
Bit of background. This server has another express instance of SQL Server 2008. I have
used local system account, network service as well as our general SQL service account, but I get the error towards the end of the installation and it fails saying “Some or all identity references could not be translated.”
I am installing a named instance with the same name as before but fails. I have tried
creating a new test instance that fails too. Any ideas? I have uninstalled SQL enterprise edition from
Add and Remore Programs/Programs and Features. I've also run the Windows Installer CleanUp Utility but no joy.
Cheers -
Crystal Reports 2008 Setup Has Failed
Post Author: MWheeler
CA Forum: Upgrading and Licensing
I get a setup error as soon as I hit "install" on the English upgrade to 2008 on my Windows Xp Sp2 machine. I am running XI developer edition on this machine. The Window title for the error message is "Crystal Reports 2008 Setup Error" and the text is "Crystal Reports 2008 Setup has failed. If this continues contact http:
support.businessobjects.com". I tried to open a Support case on this, but the Create a Case screen didn't have anyplace to enter any data at all and ended up just timing out.I have got the same error message.
I was unable to uninstall the program from the control panel.
Try to install Windows Installer CleanUp software, and uninstall with this program the previous version on Crystal Reports.
http://download.microsoft.com/download/e/9/d/e9d80355-7ab4-45b8-80e8-983a48d5e1bd/msicuu2.exe -
How to setup database trace on odata service
I have found two discussion which mention that we have to setup database trace but how is the question? if some one can please help me out step by step setting up the trace on odata service, links are as follows
Manage multi-table insert using OData Service
Where can I see logs of OData Service usage?
in aforesaid discussion they have said plz give path to xsa:<package path> but when i go to database trace config there is no option where i can give the path so please help...In the database trace / trace configuration dialog: first be sure to check Show All Components. Then in the input box at the top of the dialog type xsa:<your package>. You can type just a partial package name as well and the search will find all matches.
-
9.2 create Database fails in sql.bsq
I have installed Oracle 9.2.0.1.0. It appears to have installed correctly.
I am attempting to create a new database. The script sql.bsq in %ORACLE_HOME%\rdbms\admin appears to be trying to create a cluster around line 1329. I don't use clusters (per se).
I am rcving an the following error a trace file.
*** SESSION ID:(10.1) 2003-09-08 16:59:56.000
ORA-00604: error occurred at recursive SQL level 1
ORA-01569: data file too small for system dictionary tables
Offending statement at line 1332
create cluster c_cobj# (obj# number)
pctfree 0 pctused 50
/* space for: update cdef$ set condition = 'col IS NOT NULL' at // */
size 300
storage (initial 50K) /* avoid space management during IOR I */
ORA-01501: CREATE DATABASE failed
ORA-01519: error while processing file '%ORACLE_HOME%\RDBMS\ADMIN\SQL.BSQ' near line 1332
ORA-00604: error occurred at recursive SQL level 1
ORA-01569: data file too small for system dictionary tables
Can someone point me to an answer for this?
I have 2 95MB files being created in the system tablespace. and I can provide you either my create database script and/or my init.ora file, if they will assist.
Thnak youThank you.
I have changed the create database statement several times to try different possiblities.
I have put maxsize unlimited. That failed.
I have put maxsize 200M (with a second file of maxsize 200M) that failed.
I have added the temp storage syntax. That failed.
All of these failed in sql.bsq and all used the ORA 1569 error about a data file being too small.
WHAT DATA FILE? The system tablespace data file(s) have never been increased (by Oracle) from the original size value I provided (whether that size was 500K, or 95M). So what data file is Oracle complaining about?
In addition, I have seen the following message in the alert_project.log:
========================================
Assigning activation ID 2846189359 (0xa9a5672f)
Thread 1 opened at log sequence 1
Current log# 1 seq# 1 mem# 0: D:\DATA\ORACLE\ORADATA\BURKE\LOGS\LOGFILE1.LOG
Current log# 1 seq# 1 mem# 1: D:\ORACLE\ORADATA\BURKE\LOGS\LOGFILE1.LOG
Successful open of redo thread 1.
Tue Sep 09 11:42:39 2003
SMON: enabling cache recovery
Tue Sep 09 11:42:39 2003
create tablespace SYSTEM datafile 'd:\data\Oracle\oradata\burke\system01.dbf' size 500K REUSE
autoextend on next 500K maxsize 200M,
'd:\data\Oracle\oradata\burke\system02.dbf' size 500k REUSE
autoextend on next 500K maxsize 200M
default storage (initial 10K next 10K) EXTENT MANAGEMENT DICTIONARY online
Tue Sep 09 11:42:39 2003
Completed: create tablespace SYSTEM datafile 'd:\data\Oracle
Tue Sep 09 11:42:39 2003
create rollback segment SYSTEM tablespace SYSTEM
storage (initial 50K next 50K)
Completed: create rollback segment SYSTEM tablespace SYSTEM
Tue Sep 09 11:42:40 2003
Errors in file d:\data\oracle\admin\burke\udump\project_ora_1324.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-01569: data file too small for system dictionary tables
========================================
The line that says
default storage (initial 10K next 10K) EXTENT MANAGEMENT DICTIONARY online
is not in my create database statement. Can it be a portion of my problem?
I don't see it in the 9.2 SQL manual for create database.
I appreciate the assistance that has been provided, but I still need some more.
Thanks you all again.
Maybe you are looking for
-
Hello all. I have been search for a user exit in planned orders that allow me to define some code in it to triger some changes. this user exit should be at time of planned order is saved. I have already search in this forum and I found out how to fin
-
Mac 10.6.8's video calls not working! Please help!
Reposting the text below because there was no reply to the last message. Ack! Please help. Skype, is there a solution yet? Or even just an explanation and a time frame so we know when we can expect video calls to work again? Thanks! ---------------I
-
See my Why my calendar display different there is one day difference from different when I see main screen and open the calendar
-
How to open program developed using labview 8.2 in labview 7.1?
Dear friends, I need to open program developed by using labview 8.2 in labview 7.1.help me in this regard?
-
Hi, wht is the diff between alv list control and alv grid control with eg plz. in the different secondary lists i should get different different end of pages at bottom how should we do