Adding new WhoIs server

HI there,
Im wondering if there is a way for me to edit the available WHOIS servers in the Network Utilities application?
I know that I can type a new server in though the application doesn't let me keep that value in the dropdown, which would be ideal so I could just type the domain select server and lookup the info..
Cheers,
Phil

The solution (as posted: http://hints.macworld.com/article.php?story=20011205055200598) for anyone else who is interested is:
Go to /Users/user_name/Library/Preferences.
Quit Network Utility if it's running.
Open com.apple.NetworkUtility.plist file in propertylisteditor (or TextEdit if you don't have the Dev Tools installed).
Open the NUWhoisServers key (in TextEdit, look for <key>NUWhoisServers</key>). Add/delete additional strings with the whois servers you would like to keep/remove permanently from the Network Utilities server list (in TextEdit, insert additional <string>whois.server.name</string> values into the list, or delete the ones you don't wish to see).
Save your changes and quit the editor.
Re-launch Network Utility and see the new list of servers
Worked perfectly for me...

Similar Messages

Full server pool crashes when adding new iSCSI server

Hi,
we have a Pool Group with 2 machines (1 Server Pool Master + Server Virtual Machine + Utility Server and another 1 Server Virtual Machine). Both have a iSCSI Shared Disk which builds /OVS partition.
This is working, we can use High Availability, Migrate guests etc.
But when adding new Server Virtual Machines to the pool (with guests running), current machines in the Pools get restarted.
My question is, can server virtual machines be "hot added" to the pool group while guests are running?
Thanks and regards,
Marc

Hi,
hosts file seems to be correct.
Messages logs during the crash time are the following:
Node vmserver15 = Server Pool Master, Utility Master and Server Virtual Machine
Dec 10 12:40:02 vmserver15 kernel: vlan500: port 3(vif6.0) entering disabled state
Dec 10 12:40:02 vmserver15 kernel: device vif6.0 left promiscuous mode
Dec 10 12:40:02 vmserver15 kernel: type=1700 audit(1260445202.434:16): dev=vif6.0 prom=0 old_prom=256 auid=4294967295 ses=4294967295
Dec 10 12:40:02 vmserver15 kernel: vlan500: port 3(vif6.0) entering disabled state
Dec 10 12:40:02 vmserver15 kernel: loop10: dropped 10114 extents
Dec 10 12:40:03 vmserver15 udhcpc: udhcp client (v0.9.8) started
Dec 10 12:40:03 vmserver15 udhcpc: Lease of 193.109.175.25 obtained, lease time 172800
Dec 10 12:40:04 vmserver15 kernel: device vif7.0 entered promiscuous mode
Dec 10 12:40:04 vmserver15 kernel: type=1700 audit(1260445204.774:17): dev=vif7.0 prom=256 old_prom=0 auid=4294967295 ses=4294967295
Dec 10 12:40:04 vmserver15 kernel: vlan500: topology change detected, propagating
Dec 10 12:40:04 vmserver15 kernel: vlan500: port 3(vif7.0) entering forwarding state
Dec 10 12:40:05 vmserver15 kernel: loop10: fast redirect
Dec 10 12:40:06 vmserver15 kernel: blkback: ring-ref 770, event-channel 9, protocol 1 (x86_32-abi)
Dec 10 12:53:35 vmserver15 kernel: o2net: no longer connected to node vmserver10.pic.es (num 1) at 193.109.174.110:7777
Dec 10 12:53:36 vmserver15 kernel: (4989,0):o2hb_do_disk_heartbeat:776 ERROR: Device "sdb1": another node is heartbeating in our slot!
Dec 10 12:53:37 vmserver15 kernel: o2net: accepted connection from node vmserver10.pic.es (num 1) at 193.109.174.110:7777
Dec 10 12:53:38 vmserver15 kernel: (4989,0):o2hb_do_disk_heartbeat:776 ERROR: Device "sdb1": another node is heartbeating in our slot!
Dec 10 12:53:50 vmserver15 last message repeated 6 times
Dec 10 12:53:51 vmserver15 kernel: o2net: no longer connected to node vmserver10.pic.es (num 1) at 193.109.174.110:7777
Dec 10 12:53:52 vmserver15 kernel: (4989,0):o2hb_do_disk_heartbeat:776 ERROR: Device "sdb1": another node is heartbeating in our slot!
Dec 10 12:53:53 vmserver15 kernel: o2net: accepted connection from node vmserver10.pic.es (num 1) at 193.109.174.110:7777
Dec 10 12:53:53 vmserver15 kernel: (5638,0):dlm_send_remote_convert_request:393 ERROR: dlm status = DLM_IVLOCKID+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):dlmconvert_remote:327 ERROR: dlm status = DLM_IVLOCKID+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):ocfs2_cluster_lock:1206 ERROR: DLM error DLM_IVLOCKID while calling dlmlock on resource M000000000000000001050c00000000: bad lockid+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):ocfs2_inode_lock_full:2064 ERROR: status = -22+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):ocfs2_inode_lock_atime:2193 ERROR: status = -22+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):__ocfs2_file_aio_read:2434 ERROR: status = -22+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):dlm_send_remote_convert_request:393 ERROR: dlm status = DLM_IVLOCKID+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):dlmconvert_remote:327 ERROR: dlm status = DLM_IVLOCKID+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):ocfs2_cluster_lock:1206 ERROR: DLM error DLM_IVLOCKID while calling dlmlock on resource M000000000000000001050c00000000: bad lockid+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):ocfs2_inode_lock_full:2064 ERROR: status = -22+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):ocfs2_write_begin:1845 ERROR: status = -22+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):ocfs2_file_buffered_write:2016 ERROR: status = -22+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):__ocfs2_file_aio_write:2173 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):dlm_send_remote_convert_request:393 ERROR: dlm status = DLM_IVLOCKID+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):dlmconvert_remote:327 ERROR: dlm status = DLM_IVLOCKID+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_cluster_lock:1206 ERROR: DLM error DLM_IVLOCKID while calling dlmlock on resource M000000000000000000020744c1370e: bad lockid+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_inode_lock_full:2064 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_reserve_suballoc_bits:449 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_reserve_cluster_bitmap_bits:682 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_local_alloc_reserve_for_window:930 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_local_alloc_slide_window:1063 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_reserve_local_alloc_bits:537 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):__ocfs2_reserve_clusters:725 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_lock_allocators:677 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_write_begin_nolock:1751 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_write_begin:1861 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_file_buffered_write:2016 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):__ocfs2_file_aio_write:2173 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: loop: Write error at byte offset 37644512256, length 4096.+
. <the above bold and cursive text is repetead few times>
Dec 10 12:58:29 vmserver15 kernel: (5638,3):dlmconvert_remote:327 ERROR: dlm status = DLM_IVLOCKID
Dec 10 12:58:29 vmserver15 kernel: (5638,3):ocfs2_cluster_lock:1206 ERROR: DLM error DLM_IVLOCKID while calling dlmlock on resource M000000000000000001050c00000000: bad lockid
Dec 10 12:58:29 vmserver15 kernel: (5638,3):ocfs2_inode_lock_full:2064 ERROR: status = -22
Dec 10 12:58:29 vmserver15 kernel: (5638,3):ocfs2_write_begin:1845 ERROR: status = -22
Dec 10 12:58:29 vmserver15 kernel: (5638,3):ocfs2_file_buffered_write:2016 ERROR: status = -22
Dec 10 12:58:29 vmserver15 kernel: (5638,3):__ocfs2_file_aio_write:2173 ERROR: status = -22
Dec 10 13:01:16 vmserver15 syslogd 1.4.1: restart.
Node vmserver10: Virtual Server Machine
Dec 10 12:53:35 vmserver10 kernel: o2net: no longer connected to node vmserver15.pic.es (num 0) at 193.109.174.115:7777
Dec 10 12:53:35 vmserver10 kernel: (5029,0):ocfs2_dlm_eviction_cb:98 device (8,17): dlm has evicted node 0
Dec 10 12:53:35 vmserver10 kernel: (20996,0):dlm_get_lock_resource:844 E3FE9E5767CA457FA697980EB637E93B:M000000000000000000022044c1370e: at least one node (0) to recover before lock mastery can begin
Dec 10 12:53:36 vmserver10 kernel: (5344,4):dlm_get_lock_resource:844 E3FE9E5767CA457FA697980EB637E93B:$RECOVERY: at least one node (0) to recover before lock mastery can begin
Dec 10 12:53:36 vmserver10 kernel: (5344,4):dlm_get_lock_resource:878 E3FE9E5767CA457FA697980EB637E93B: recovery map is not empty, but must master $RECOVERY lock now
Dec 10 12:53:36 vmserver10 kernel: (5344,4):dlm_do_recovery:524 (5344) Node 1 is the Recovery Master for the Dead Node 0 for Domain E3FE9E5767CA457FA697980EB637E93B
Dec 10 12:53:36 vmserver10 kernel: (20996,0):ocfs2_replay_journal:1183 Recovering node 0 from slot 0 on device (8,17)
Dec 10 12:53:37 vmserver10 kernel: o2net: connected to node vmserver15.pic.es (num 0) at 193.109.174.115:7777
Dec 10 12:53:38 vmserver10 kernel: (8672,1):dlm_get_lock_resource:844 ovm:$RECOVERY: at least one node (0) to recover before lock mastery can begin
Dec 10 12:53:38 vmserver10 kernel: (8672,1):dlm_get_lock_resource:878 ovm: recovery map is not empty, but must master $RECOVERY lock now
Dec 10 12:53:38 vmserver10 kernel: (8672,1):dlm_do_recovery:524 (8672) Node 1 is the Recovery Master for the Dead Node 0 for Domain ovm
Dec 10 12:53:40 vmserver10 kernel: kjournald starting. Commit interval 5 seconds
Dec 10 12:53:51 vmserver10 kernel: o2net: no longer connected to node vmserver15.pic.es (num 0) at 193.109.174.115:7777
Dec 10 12:53:53 vmserver10 kernel: o2net: connected to node vmserver15.pic.es (num 0) at 193.109.174.115:7777
Dec 10 12:53:53 vmserver10 kernel: (3761,0):dlm_convert_lock_handler:489 ERROR: did not find lock to convert on grant queue! cookie=0:92+
Dec 10 12:53:53 vmserver10 kernel: lockres: M000000000000000001050c0000000, owner=1, state=0+
Dec 10 12:53:53 vmserver10 kernel:   last used: 0, refcnt: 3, on purge list: no+
Dec 10 12:53:53 vmserver10 kernel:   on dirty list: no, on reco list: no, migrating pending: no+
Dec 10 12:53:53 vmserver10 kernel:   inflight locks: 0, asts reserved: 0+
*Dec 10 12:53:53 vmserver10 kernel:   refmap nodes: [ ], inflight=0*+
Dec 10 12:53:53 vmserver10 kernel:   granted queue:+
Dec 10 12:53:53 vmserver10 kernel:     type=5, conv=-1, node=1, cookie=1:243, ref=2, ast=(empty=y,pend=n), bast=(empty=y,pend=n), pending=(conv=n,lock=n,cancel=n,unlock=n)+
Dec 10 12:53:53 vmserver10 kernel:   converting queue:+
Dec 10 12:53:53 vmserver10 kernel:   blocked queue:+
. <the above bold and cursive text is repetead few times>
Dec 10 12:57:18 vmserver10 modprobe: FATAL: Module ocfs2_stackglue not found.
Dec 10 12:57:18 vmserver10 kernel: (3761,0):dlm_convert_lock_handler:489 ERROR: did not find lock to convert on grant queue! cookie=0:92+
Dec 10 12:57:18 vmserver10 kernel: lockres: M000000000000000001050c0000000, owner=1, state=0+
Dec 10 12:57:18 vmserver10 kernel:   last used: 0, refcnt: 3, on purge list: no+
Dec 10 12:57:18 vmserver10 kernel:   on dirty list: no, on reco list: no, migrating pending: no+
Dec 10 12:57:18 vmserver10 kernel:   inflight locks: 0, asts reserved: 0+
*Dec 10 12:57:18 vmserver10 kernel:   refmap nodes: [ ], inflight=0*+
Dec 10 12:57:18 vmserver10 kernel:   granted queue:+
Dec 10 12:57:18 vmserver10 kernel:     type=5, conv=-1, node=1, cookie=1:243, ref=2, ast=(empty=y,pend=n), bast=(empty=y,pend=n), pending=(conv=n,lock=n,cancel=n,unlock=n)+
Dec 10 12:57:18 vmserver10 kernel:   converting queue:+
Dec 10 12:57:18 vmserver10 kernel:   blocked queue:+
. <the above bold and cursive text is repetead few times>
Dec 10 12:58:32 vmserver10 kernel: (3761,0):dlm_unlock_lock_handler:511 ERROR: failed to find lock to unlock! cookie=0:1849
Dec 10 12:58:33 vmserver10 modprobe: FATAL: Module ocfs2_stackglue not found.
Dec 10 12:59:02 vmserver10 kernel: o2net: connection to node vmserver15.pic.es (num 0) at 193.109.174.115:7777 has been idle for 30.0 seconds, shutting it down.
Dec 10 12:59:02 vmserver10 kernel: (0,0):o2net_idle_timer:1503 here are some times that might help debug the situation: (tmr 1260446312.830107 now 1260446342.828243 dr 1260446312.830066 adv 1260446312.830319:1260446312.830320 func (b9f5fd13:506) 1260446312.830109:1260446312.830303)
Dec 10 12:59:02 vmserver10 kernel: o2net: no longer connected to node vmserver15.pic.es (num 0) at 193.109.174.115:7777
Dec 10 12:59:32 vmserver10 kernel: (3761,0):o2net_connect_expired:1664 ERROR: no connection established with node 0 after 30.0 seconds, giving up and returning errors.
Dec 10 13:01:42 vmserver10 kernel: o2net: connected to node vmserver15.pic.es (num 0) at 193.109.174.115:7777
Dec 10 13:01:45 vmserver10 kernel: ocfs2_dlm: Node 0 joins domain E3FE9E5767CA457FA697980EB637E93B
Dec 10 13:01:45 vmserver10 kernel: ocfs2_dlm: Nodes in domain ("E3FE9E5767CA457FA697980EB637E93B"): 0 1
Dec 10 13:01:51 vmserver10 kernel: o2net: accepted connection from node vmserver16.pic.es (num 2) at 193.109.174.116:7777
Dec 10 13:01:56 vmserver10 kernel: ocfs2_dlm: Node 2 joins domain E3FE9E5767CA457FA697980EB637E93B
Dec 10 13:01:56 vmserver10 kernel: ocfs2_dlm: Nodes in domain ("E3FE9E5767CA457FA697980EB637E93B"): 0 1 2
Dec 10 13:09:05 vmserver10 modprobe: FATAL: Module ocfs2_stackglue not found.
Dec 10 13:16:45 vmserver10 kernel: o2net: connection to node vmserver16.pic.es (num 2) at 193.109.174.116:7777 has been idle for 30.0 seconds, shutting it down.
Dec 10 13:16:45 vmserver10 kernel: (0,0):o2net_idle_timer:1503 here are some times that might help debug the situation: (tmr 1260447375.655426 now 1260447405.655712 dr 1260447375.655413 adv 1260447375.655427:1260447375.655427 func (b9f5fd13:503) 1260446516.75600:1260446516.75608)
Dec 10 13:16:45 vmserver10 kernel: o2net: no longer connected to node vmserver16.pic.es (num 2) at 193.109.174.116:7777
Dec 10 13:17:15 vmserver10 kernel: (3761,0):o2net_connect_expired:1664 ERROR: no connection established with node 2 after 30.0 seconds, giving up and returning errors.
Dec 10 13:17:19 vmserver10 kernel: (5029,0):ocfs2_dlm_eviction_cb:98 device (8,17): dlm has evicted node 2
Dec 10 13:17:20 vmserver10 kernel: (3761,0):ocfs2_dlm_eviction_cb:98 device (8,17): dlm has evicted node 2
Dec 10 13:29:05 vmserver10 kernel: o2net: no longer connected to node vmserver15.pic.es (num 0) at 193.109.174.115:7777
Dec 10 13:29:05 vmserver10 kernel: (5029,0):ocfs2_dlm_eviction_cb:98 device (8,17): dlm has evicted node 0
Dec 10 13:29:06 vmserver10 kernel: (5344,4):dlm_get_lock_resource:844 E3FE9E5767CA457FA697980EB637E93B:$RECOVERY: at least one node (0) to recover before lock mastery can begin
Dec 10 13:29:06 vmserver10 kernel: (5344,4):dlm_get_lock_resource:878 E3FE9E5767CA457FA697980EB637E93B: recovery map is not empty, but must master $RECOVERY lock now
Dec 10 13:29:06 vmserver10 kernel: (5344,4):dlm_do_recovery:524 (5344) Node 1 is the Recovery Master for the Dead Node 0 for Domain E3FE9E5767CA457FA697980EB637E93B
Dec 10 13:29:06 vmserver10 kernel: (28412,0):ocfs2_replay_journal:1183 Recovering node 0 from slot 0 on device (8,17)
Dec 10 13:29:09 vmserver10 kernel: kjournald starting. Commit interval 5 seconds
Dec 10 13:29:16 vmserver10 kernel: o2net: accepted connection from node vmserver16.pic.es (num 2) at 193.109.174.116:7777
Dec 10 13:29:20 vmserver10 kernel: ocfs2_dlm: Node 2 joins domain E3FE9E5767CA457FA697980EB637E93B
Dec 10 13:29:20 vmserver10 kernel: ocfs2_dlm: Nodes in domain ("E3FE9E5767CA457FA697980EB637E93B"): 1 2
Dec 10 13:32:08 vmserver10 kernel: o2net: connected to node vmserver15.pic.es (num 0) at 193.109.174.115:7777
Dec 10 13:32:11 vmserver10 kernel: ocfs2_dlm: Node 0 joins domain E3FE9E5767CA457FA697980EB637E93B
Dec 10 13:32:11 vmserver10 kernel: ocfs2_dlm: Nodes in domain ("E3FE9E5767CA457FA697980EB637E93B"): 0 1 2
Dec 10 13:36:10 vmserver10 shutdown[28681]: shutting down for system reboot+
I will investigate what seems to be going on and post it here.
Thanks for your help.
Edited by: Marc Caubet on 11-Dec-2009 02:05
Edited by: Marc Caubet on 11-Dec-2009 02:07

Adding new domain server to network

Thanks Carl! I'll give it a shot tomorrow.

Hello Guys and Gals,
I have a Windows 2008 R2 domain server and I am wanting to add another one. I have purchased a server with Windows 2012 R2.
I have joined the domain on the new system but I haven't added any roles yet. Anything I should keep in mind before I add the Role?
This topic first appeared in the Spiceworks Community

Not able to set Weblogic Runtime on eclipse while adding new weblogic srvr

Hi Everyone,
I downloaded Oracle Integration pack for eclipse by clicking at "Download additional server adapters". I am not able to set Weblogic Runtime on eclipse while adding new weblogic server.
I am trying to give following values:
Name :Oracle WebLogic Server 10gR3 (2)
Weblogic home :C:\bea\wlserver_10.3
Java home: C:\bea\jrockit_160_05
Below it I am getting "No applicable extension found" and finish button is greyed out.
Please help in telling what is wrong. Never faced such an issue.
Thanks
SM

I found this problem too.
OS:windows7、eclipse:helios、oepe:Part of Oracle Enterprise Pack for Eclipse 11.1.1.7.3
<workspace>\.metadata\.log:
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: enter_new_hit_count in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: exception_occurred_setting_bp_properties in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: hit_count_must_be_positive in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: no_description_provided in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: scripts in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: select_javascript_file in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: set_bp_hit_count in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: suspend_target in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: suspend_thread in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: the_argument_0_is_not_valid in: org.eclipse.wst.jsdt.debug.internal.ui.messages
I tried the weblogic 10.3.1、10.3.3、10.3.4、10.3.5 still show the info that "No applicable extension found" and finish button is greyed out.
What is the reason?
thanks!

Adding another application server.

Hi Experts,
My company is having 2 system landscape.
DEV & QAS in one and PRD in one server.
in recent years, my company is growing faster.
i.e increasing number of End users and database growth.
and now the task is to add 2 or more application servers.
my doubts about application server are as follows:-
1 *Deploying application server means is tht installation of sap central instance in
new server or installing an Dailog instance ?
2 *How to add new installed application server to the existing land scape ?
3 *how to group up the added application servers in to a group , so that the
user will get connected to sap by tht group of application server?
requesting you to give some inputs on adding new application server and
solution for database growth ?

Hi graham,
You mean to say, if i install Dailog instance in new server and connected to lan with same ip class as PRD server. that will appear in SMLG.
so, there is no concept of selecting new server from PRD. i.e by STMS router or RFC .
and after adding the new application server i can create new group in SMLG
(by combining all the application servers, so tht user logons will be distributed.)
is that right.
if any RFC connection has to maintained from PRD to new application server.
please let me know that.
thanking you
by
raghav

Adding unique report server

My Oracle AS is running on Linux box.
I am adding new report server as below.
Connected remoetly via SSH.(putty) from my winows xp.
oracle@appserver:~/biforms/opmn/conf> rwserver -install repserver007
batch=no autostart=no
rwserver: error while loading shared libraries: libjvm.so: cannot open shared
object file: No such file or directory
DN

As in another thread, did you set the proper environment before starting? biforms.sh?
And also remove -install, it's for Windows when you want it to be installed as a Windows Services. You should anyhow try to start it as mentioned before with opmnctl.
Martin

Error while adding new OVM in server pool

Hi,
I have to add a new OVM server to the existing server pool.
while doing test connecting at the time of adding server in server pool, it is contacting. however, it is showing error with " check the agent connectivity" while clicking OK.
ovs agent server is running.
can any one assit me on this

Hi,
Did the subscriber database used for replication before?
Check the MSDistribution_history table in the distribution database. It contains history rows for the Distribution Agents.
In case you encounter the “One or more subscriptions have been marked inactive. Drop and re-create all subscriptions for this node that are failing with this error.” in the Replication Monitor after restarting the Distribution
Agent.
This means that the Distribution Agent is unable to delivery data due to some errors or the job was stopped and the Agent will go into an infinite retry logic.
The Agent will stay in retry mode until the Distribution Cleanup job removes the “cached” transactions from the Distribution Database. At this point the Distribution Agent will no longer have the data needed to “catch
up” the subscriber. As result, the Subscriber will be marked “inactive” and post the following error in the MSrepl_errors table in the Distribution database.
Subscription Expiration and Deactivation
http://technet.microsoft.com/en-us/library/ms151188.aspx
Thanks.
Tracy Cai
TechNet Community Support

Error adding new users from local server

Hello, BPC Gurus,
We use BPC 7.0 MS SP4, MS SQL 2008 (Server name - BPCP01)
In Administration Console we're trying to add user from local server (server with SQL Database), and warning window is appeared with message "The Server Is Not Operational [BPBCP01]"
I checked Logging folder and found message:
==============[System Error Tracing]==============
[System Name] : OSoftAdminSecurity
[Job Name]     : frmManageUser::GetAllObjectsFromDomainServer
[DateTime]     : 2010-12-06 16:58:43
[Exception]
    DetailMsg : {System.Exception: The server is not operational [BPCP01]
   at Microsoft.VisualBasic.CompilerServices.LateBinding.LateGet(Object o, Type objType, String name, Object[] args, String[] paramnames, Boolean[] CopyBack)
   at OSoft.Consumers.Admin.Security50.ManageDataSet.GetAllObjectsFromDomainServer(String pDomainName, String pLDAPFullPath, Int32 pDomainObjectType, String pObjectValue, String pDomainType)
   at OSoft.Consumers.Admin.Security50.frmManageUser.GetAllObjectsFromDomainServer(String pDomainName, FILTER_TYPE pOptionType, String pOptionValue, String pDomainType)}
===========[System Error Tracing End ]===========
Any ideas?

The installation was done with a local user or with a domain user?
You know that BPC server can not be in the same time also domain controler.
Are you using Windows authentication or CMS authentication.
If you are using CMS authentication then again you can not add local users.
If you are using Windows authentication then you have to go into server Manager
Options - Define System User Groups
Domain Type - Local Windows
System User Group Name - Local Users.
If you are using Windows 2008 make sure you addrole to have compatibility with IIS 6.because using this module bpc is adding new users.
Regards
Sorin Radulescu

Adding new Hub Transport server in existing environment

Hi everyone,
Currently we have 5 exchange servers 2010 :
2 CAS Servers (Virtual)
2 MB and Hub Transport servers (Physical)
1 Edge server in DMZ. (Virtual)
Now I have added 2 more servers
with MB and Hub Tranport Roles (VIRTUAL) and want to configure the mail flow from these new transport servers.
Can anyone help with the steps I should follow. Please note we have 1 existing Edge server in 2010 and email flow should be from Hub Transport to Edge server then from Edge to internet.
Existing environment is working fine without any issues. Main reason to do this is to virtualize the physical servers. Mailbox DB already migrated to new servers.
Thanks.
Manish Kumar MCSA, MCITP Enterprise Admin. MCTS Exchange server 2007, MCITP Virtualization Admin.

Dear Manish
Please find your answers below
For mail flow to happen through new hub transport I will make the new edge subscription from new HUB server
to Edge server. Is there any other changes I have to do ?
No other changes is required
Create a new edge subscription and then import it and run start endge sync
So when I will do create the new edge subscription then it will delete the old send connectors and will
create the new one?
IT will create old edge sync and create a new edge sync which will not make any impact on your config
Will there be any downtime while doing this activity ?
Better to do this on after production hours since definitely there will be mail delay and may delay more if you try this on production hours
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish (MVP)

Error in Adding new vritual machine server to HaA cluster ???

Hi
when i adding new Server to my cluster i see this error
Check prerequisites to add server (192.168.20.253) to server pool (karkas) succeed
2009-11-29 12:16:33     Check prerequisites to add server (192.168.20.253) to server pool (karkas) succeed
2009-11-29 12:16:46     During adding servers ([192.168.20.253]) to server pool (karkas), Cluster setup failed: (OVM-1011 OVM Manager communication with 192.168.20.254 for operation HA Setup for Oracle VM Agent 2.2.0 failed: errcode=50006, errmsg=Do 'clusterm_init_root_sr' on servers ('192.168.20.253') failed. )
but when edited again see solved problem but not HA feature work correctly(when shutdown server pool virtual machine is goes down )
i test is with nfs server but not work i user iscsci target on RHEL5 for create iscsi server
i see ha work correctly same az this
2009-11-29 12:25:44     Check prerequisites to add server (192.168.20.253) to server pool (karkas) succeed
2009-11-29 12:25:50     Check prerequisites to add server (192.168.20.253) to server pool (karkas) succeed
Select     Server Pool Name     Status     High Availability Status     Servers     Users     Logs
Select     karkas     Active     Enabled     Total: 2     Total: 1     View Logs
and no error in /var/log/ovs/*.log
but when add new server i see in status "error in adding server "" and when edited again see server add and active state
1-i have no ocfs2 partition on my machine use iscsi initiator
2-all server use root cluster id /var/ovs/mount/disk_id
3-all permission set for everybody and 777
any idea for solve this problem
thanks

hi
and very thanks for your reply
every this work good
[root@OVS2-253-32 ~]# service o2cb online
Starting O2CB cluster ocfs2: OK
[root@OVS2-253-32 ~]# service o2cb start
Starting O2CB cluster ocfs2: OK
[root@OVS2-253-32 ~]#
but see :
     During adding servers ([192.168.20.253]) to server pool (jojo), Cluster setup failed: (OVM-1011 OVM Manager communication with 192.168.20.254 for operation HA Setup for Oracle VM Agent 2.2.0 failed: errcode=50006, errmsg=Do 'clusterm_init_root_sr' on servers ('192.168.20.253') failed. )
Select     Server Host/IP     Server Name     Server Type     Status     Server Location     Server Pool Name     Logs
Select     192.168.20.254     254     Server Pool Master,Utility Server,Virtual Machine Server     Active          jojo     View Logs
Select     192.168.20.253     253     Virtual Machine Server     Error          jojo     View Logs
but edit this server work fine. i use doc in step by step configure and no error occur in configuration but still see this error on adding new server and HA can't works correctly (only when i power off virtual quest machine after 15 second this server goes up and live migration not work correctly )when i shutting down one virtual machine server guest still wait for powering up this server
ocfs2 kernel module load correctly
cat /var/log/ovs-agent/ovs_root.log
StackTrace:
File "/opt/ovs-agent-2.3/OVSXCluster.py", line 115, in clusterm_init_root_sr
sr.initialize()
File "/opt/ovs-agent-2.3/_storage/OVSFileSR.py", line 127, in initialize
self.sp.mount(mp)
File "/opt/ovs-agent-2.3/_storage/plugins/OVSFileSP.py", line 209, in mount
fs_spec = self.get_fs_spec()
File "/opt/ovs-agent-2.3/_storage/plugins/OVSFileSP.py", line 184, in get_fs_spec
tgt_dev = get_dev_spec(self.fs_uuid, self.fs_spec)
File "/opt/ovs-agent-2.3/_storage/plugins/OVSFileSP.py", line 82, in get_dev_spec
raise Exception("No device found: dev_uuid=%s" % dev_uuid)
are you have any idea for solve this problem ???
very thanks

Adding an additional new app server - to BI

We're going to add a new app server, dialogue instance to our BI 7.1 system so that we'll have 2. Do we need to apply the enhancement pack 1 to the new dialogue instance?
Thanks,
Daniel

Hi Daniel,
For updating the dialog instances please see note 1245473
Add. Info. - SAP Enhancement Package Installer 7.00
Updating Dialog Instances
After the enhancement package installation on the central instance, you
need to update the dialog instances accordingly. To do this, you install
the new dialog instances on top of the old dialog instances using the
tool SAPinst.
You can now also install more dialog instances, if necessary.
3. Save your dialog instance profiles, if you want to reuse them.
4. In case of a dual-stack system or a Java system, uninstall the old
    dialog instances as described in the installation guide for your
    source release.
5. To install a new dialog instance, proceed as described in the
    document Installation Guide - <SAP NetWeaver / SAP application>
    (<Technology>) on <Operating System>: <Database>.
6. If you use other instance numbers than on the source release and
    reuse the old dialog instance profiles, adapt the instance numbers
    in the profiles.
So installing the new dialog instance will be updated.
Regards,
Paul

Warning while adding new ECC

Hi ,
I am getting error while adding new ECC variable in ICM. PFB the error message.
" The Maximum size of all Expanded Call Variable in the Computer Telephony Integeration Server is 2500 bytes. Saving these schanges would require 2795 bytes.
will this hamper the performance of the system..?

Hi, no, it will not work at all, so no worries about system performance.
Why are you adding a new ECC variable when the system tells you it wont fit?
G.
Sent from Cisco Technical Support Android App

Error when creating a new Reports Server instance

Hi,
I have tried to create and start a new reports server instance using the following method:
1- Creating the report server instance:
rwserver server=%newrepserver% start
2- Stopping the OPMN:
*%ORACLEHOME%\opmn\bin\opmnctl stopall*
3- Adding a new server target to OPMN.XML
*%ORACLEHOME%\bin\addNewServerTarget.bat %newrepserver%*
4- Updating the configuration with new OPMN settings:
*%ORACLEHOME%\dcm\bin\dcmctl.bat updateconfig -ct opmn -v -d*
*%ORACLEHOME%\dcm\bin\dcmctl.bat resyncinstance -v -d*
5- Starting the OPMN again:
*%ORACLEHOME%\opmn\bin\opmnctl startall*
However, when I try to start the OPMN again, I receive the following error:
opmn id="##########:6200 5 of 6 processes started
ias-instance id=red.########.########.lan
++++++++++++++++++++++++++++++++++
ias-component/process-type-process-set:
*%newrepserver%/ReportsServer/%newrepserver%*
Error --> Process (pid=6888) failed to start a managed process after the maximum retry limit.
Log: %ORACLEHOME%\opmn\logs\%newrepserver%~ReportsServer~%newrepserver%
Any ideas as to why the reports server instance cannot be started?
I have tried rebooting the server many times and have recreated other reports server instances but with no luck.
Many thanks in advance,
Chris

On Windows this is caused most often by the temporary directory setting.
Change the temporary directory to some fixed directory writable by anybody, e.g. "C:\temp".
Change this in:
Registry entry: hkey_local_machine\software\oracle\key_<oashome>\REPORTS_TMP
<oashome>\opmn\conf\opmn.xml: search for environment variable TEMP (under ias-instance)
Good luck!

Install Failing when attempted to Add a new Management Server into SCSM Management Group

Hello Experts
I am adding a additional MS into my current SCSM 2012 sp1 MANAGEMENT Group. But its failing with the below error message .One thing is little wiered here is ...that the wizard fails with the message that the UPGARDE FAILED , but I am not rying to upgrade
, I am adding a MS on a new 2012 vm. It goes all the way and install the services with the account , but then it rollbacks everything I am installing the bits with the same account which is the admin on the workflow server . I have created a registry
key ServicesPipeTimeout to 600000ms , but still no luck . The new VM is all up to date with patches , the sdk/config account is the admin on the new ms vm . The service manager db is a cluster , not sure if that's wats causing it .
SCSM2012 SP1
Primary Workflow MS : WIN2008R2
SQL CLUSTER : 2008R2SP1
New MS :- WIN2012
Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.WaitForSDKServiceStart
WaitForSDKServiceStart:Entering
WaitForSDKServiceStart: Error: The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection.,
Stack:    at Microsoft.EnterpriseManagement.Common.Internal.ExceptionHandlers.HandleChannelExceptions(Exception ex)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint(EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.ConstructEnterpriseManagementGroupInternal(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore clientCallback)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.RetrieveEnterpriseManagementGroupInternal(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Connect(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
   at Microsoft.EnterpriseManagement.EnterpriseManagementGroup.InternalInitialize(EnterpriseManagementConnectionSettings connectionSettings, EnterpriseManagementGroupInternal internalsProxy)
   at Microsoft.EnterpriseManagement.EnterpriseManagementGroup.Connect(EnterpriseManagementConnectionSettings connectionSettings)
   at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.WaitForSDKServiceStart(Session session)
MSI (s) (B8:98) [16:36:03:050]: NOTE: custom action _WaitForSDKServiceStart unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
CustomAction _WaitForSDKServiceStart returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (B8:78) [16:36:05:044]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1156350899,LangId=0,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (B8:78) [16:36:05:044]: Executing op: DialogInfo(Type=0,Argument=0)
MSI (s) (B8:78) [16:36:05:046]: Executing op: DialogInfo(Type=1,Argument=Microsoft System Center 2012 - Service Manager)

D5DB645B01E7},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.Core,fileVersion="7.5.2905.0",version="7.0.5000.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:669]: Executing op: AssemblyPublish(Feature=SMCommon,Component={4D0CB3BB-D941-408A-AA30-F8B7996AB220},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.Packaging,fileVersion="7.5.2905.0",version="7.0.5000.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:675]: Executing op: AssemblyPublish(Feature=SMCommon,Component={B6133F85-0B89-4120-ADFD-9A426FB7D5A3},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.OperationsManager.Common,fileVersion="6.0.6278.0",version="6.0.4900.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:681]: Executing op: AssemblyPublish(Feature=SMCommon,Component={58A6B313-BD98-46E0-B344-0D6861535208},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.ServiceManager,fileVersion="7.5.2905.0",version="7.0.5000.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:688]: Executing op: AssemblyPublish(Feature=SMCommon,Component={41071460-6573-41C8-AED8-06CEC0D0AFB9},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.DataWarehouse,fileVersion="7.5.2905.0",version="7.0.5000.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:693]: Executing op: AssemblyPublish(Feature=SMCommon,Component={E51AEF3C-9B2D-4B0E-AB7E-AD0423899C39},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.OperationsManager,fileVersion="6.0.6278.0",version="6.0.4900.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:713]: Executing op: AssemblyPublish(Feature=SMCommon,Component={9718BF1D-6A9F-3406-A992-630F7EF2F164},AssemblyType=2,,AssemblyName=Microsoft.VC90.CRT,version="9.0.30729.1",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32",)
MSI (s) (80:88) [11:29:02:720]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitUninstall.62894CB9_4320_40DB_B4E4_C0347FAB97B6,,)
MSI (s) (80:88) [11:29:02:721]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitUninstall.62894CB9_4320_40DB_B4E4_C0347FAB97B6,ActionType=3649,Source=BinaryData,Target=ExecNetFx,)
MSI (s) (80:88) [11:29:02:722]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitInstall.62894CB9_4320_40DB_B4E4_C0347FAB97B6,,)
MSI (s) (80:88) [11:29:02:724]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitInstall.62894CB9_4320_40DB_B4E4_C0347FAB97B6,ActionType=3649,Source=BinaryData,Target=ExecNetFx,)
MSI (s) (80:88) [11:29:02:725]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitUninstall,,)
MSI (s) (80:88) [11:29:02:726]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitUninstall,ActionType=3649,Source=BinaryData,Target=ExecNetFx,)
MSI (s) (80:88) [11:29:02:726]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitInstall,,)
MSI (s) (80:88) [11:29:02:728]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitInstall,ActionType=3649,Source=BinaryData,Target=ExecNetFx,CustomActionData=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft
System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.ConsoleFramework.dll" /queue:1?500?C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.Foundation.dll"
/queue:1?500?C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.Controls.dll" /queue:1?500?C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe
install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.ViewFramework.dll" /queue:1?500?C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service
Manager\Microsoft.EnterpriseM
MSI (s) (80:88) [11:29:02:729]: Executing op: ActionStart(Name=_ConfigureConfigService.D2179E31_E456_401A_A820_CEBB135E3429,Description=Configure Config Service,)
MSI (s) (80:88) [11:29:02:734]: Executing op: CustomActionSchedule(Action=_ConfigureConfigService.D2179E31_E456_401A_A820_CEBB135E3429,ActionType=3585,Source=BinaryData,Target=ConfigureSDKConfigService,CustomActionData=1 OMCFG)
MSI (s) (80:88) [11:29:02:736]: Executing op: ActionStart(Name=_ConfigureSDKConfigService,,)
MSI (s) (80:88) [11:29:02:737]: Executing op: CustomActionSchedule(Action=_ConfigureSDKConfigService,ActionType=3585,Source=BinaryData,Target=ConfigureSDKConfigService,CustomActionData=1 OMSDK)
MSI (s) (80:88) [11:29:02:738]: Executing op: ActionStart(Name=_WaitForSDKServiceStart,,)
MSI (s) (80:88) [11:29:02:840]: Executing op: CustomActionSchedule(Action=_WaitForSDKServiceStart,ActionType=1537,Source=BinaryData,Target=WaitForSDKServiceStart,)
MSI (s) (80:88) [11:29:02:924]: Executing op: ActionStart(Name=_RegisterSdkSCP,,)
MSI (s) (80:88) [11:29:02:944]: Executing op: CustomActionSchedule(Action=_RegisterSdkSCP,ActionType=1089,Source=BinaryData,Target=RegisterSdkSCP,CustomActionData=SCSMPROD|DOMAIN\_SVCACCT|SMSDKSCP)
MSI (s) (80:6C) [11:29:03:103]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI16CE.tmp, Entrypoint: RegisterSdkSCP
CAPACK: Extracting custom action to temporary directory: C:\Windows\Installer\MSI16CE.tmp-\
CAPACK: CLR version v2.0.50727 is installed.
CAPACK: CLR version v2.0.50727 is detected.
CAPACK: CLR version v4.0.30319 is installed.
CAPACK: CLR version v4.0.30319 is detected.
CAPACK: Binding to CLR version v2.0.50727
Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.RegisterSdkSCP
RegisterSdkSCP: There is no previous serviceConnectionPoint
RegisterSdkSCP: Creating New serviceConnectionPoint
RegisterSdkSCP: Adding ACL for current user: DOMAIN\_SVCACCT
RegisterSdkSCP: Adding ACL for SM Admini: DOMAIN\_SVCACCT
RegisterSdkSCP: Error: Access is denied.
StackTrace:    at System.DirectoryServices.Interop.UnsafeNativeMethods.IAds.SetInfo()
   at System.DirectoryServices.DirectoryEntry.CommitChanges()
   at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.RegisterSdkSCP(Session session)
MSI (s) (80:6C) [11:29:10:243]: NOTE: custom action _RegisterSdkSCP unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
MSI (s) (80:88) [11:29:10:246]: Executing op: ActionStart(Name=_SetupSdkDefaultConnector,Description=Setting SDK default connector,)
CustomAction _RegisterSdkSCP returned actual error code 1603 but will be translated to success due to continue marking
MSI (s) (80:88) [11:29:10:265]: Executing op: CustomActionSchedule(Action=_SetupSdkDefaultConnector,ActionType=17921,Source=BinaryData,Target=SetupSdkDefaultConnector,CustomActionData=EDVXSCSMWEBPP02)
MSI (s) (80:88) [11:29:10:366]: Executing op: ActionStart(Name=_CreateSetupUser,,)
MSI (s) (80:88) [11:29:10:381]: Executing op: CustomActionSchedule(Action=_CreateSetupUser,ActionType=1537,Source=BinaryData,Target=CreateSetupUser,CustomActionData=DOMAIN\_SVCACCT)
MSI (s) (80:88) [11:29:10:461]: Executing op: ActionStart(Name=_CreateInstanceQualityRelationship,Description=Creating Default Instances, Qualities And There Relationships,)
MSI (s) (80:88) [11:29:10:481]: Executing op: CustomActionSchedule(Action=_CreateInstanceQualityRelationship,ActionType=17921,Source=BinaryData,Target=CreateInstanceQualityRelationship,CustomActionData=Cmdb^Microsoft.SystemCenter.ResourceAccessLayer.CmdbResourceStore^Ral.CmdbResourceStore.Cmdb^SCSMSMDBDOMAIN,DOMAIN^ServiceManager^Microsoft.SystemCenter.ResourceAccessLayer.Stores|Ods^Microsoft.SystemCenter.ResourceAccessLayer.SqlResourceStore^Ral.SqlResourceStore.Ods^SCSMSMDBDOMAIN,DOMAIN^ServiceManager^Microsoft.SystemCenter.ResourceAccessLayer.Stores|Workflows^Microsoft.SystemCenter.ResourceAccessLayer.SqlResourceStore^Ral.SqlResourceStore.Workflows^SCSMSMDBDOMAIN,DOMAIN^ServiceManager^Microsoft.SystemCenter.ResourceAccessLayer.Stores|Orchestration^Microsoft.SystemCenter.ResourceAccessLayer.DagResourceStore^Ral.DagResourceStore.Orchestration^EDVXSCSMWEBPP02^Dag^Microsoft.SystemCenter.ResourceAccessLayer.Stores|Sdk^Microsoft.SystemCenter.ResourceAccessLayer.SdkResourceStore^Ral.SdkResourceStore.Sdk^EDVXSCSMWEBPP02^Sdk^Microsoft.SystemCenter.ResourceAccessLayer.Stores$Cmdb^Cmdb|Ods^Ods|Workflows^Wo
MSI (s) (80:88) [11:29:10:551]: Executing op: ActionStart(Name=_CreateSLAOOBMetric,,)
MSI (s) (80:88) [11:29:10:593]: Executing op: CustomActionSchedule(Action=_CreateSLAOOBMetric,ActionType=1537,Source=BinaryData,Target=CreateSLAOOBMetric,)
MSI (s) (80:88) [11:29:10:669]: Executing op: ActionStart(Name=_AddAuthenticatedUserToSmEndusersRole,,)
MSI (s) (80:88) [11:29:10:687]: Executing op: CustomActionSchedule(Action=_AddAuthenticatedUserToSmEndusersRole,ActionType=17921,Source=BinaryData,Target=AddUserGroupToSmRole,CustomActionData=SERVERNAMEDOMAIN,DOMAIN|0CDDEB2B-5AC7-4E9b-8918-F73A5A5DC5FA|S-1-5-11)
MSI (s) (80:88) [11:29:10:764]: Executing op: ActionStart(Name=PublishFeatures,Description=Publishing product features,Template=[1])
MSI (s) (80:88) [11:29:10:769]: Executing op: FeaturePublish(Feature=SMCommon,,Absent=2,Component=(q3HBAv]i@qJ'%Q!&u`-E'vFHJKp&?B*BP3I&v8CI)GV$dS}K9o{`+oQzOH`6rk8o}k)$9h9ht?25ep*M5[kQmAiu8ksDfcfd?7Y`cA}%6azL=&%e(j@mj@Fz,ecq(qrp8](TKe3L$PCRH97spltW=ku%.hsb*,Om8nB9k-6cA0[3pMQTZ)ilXhqI.}^o8,EuQO7^U_3+@[M`@}[t9u8Wo6!tFc%bh)^7q6wW=apEHCHH1,?v,UEvGBSJArZu~HLod%Kb5o96e+p$903LI])2$p$F%OJdG^%+A=LH+73@4VPU6Grpj92,@+LF6KK25&]=f`,Pw3-%=3zM^iId4@ZCcxSHi&g39aNS8{R&72hWL`[email protected]`]AQmIfehM.h8y$eKidM0ZZCIg^udzEY?vKfT%PHraR*_a5.zP5_@[KW{oCEn$OB[,Y5D*`m9ByA])z,POCbb@sj&oXSAAcoGYM11_t!LQ[A2'u.90@8@Eats}$VHsbIFnRS=HM!!AA67_?kk^q?LXxN=r$8P(zZWMJJ{9@Z'[&R=ibW(AelUb.T7J9-G*B~='`,6hc~mWukk*QjX6`=?+MOCxGuQnGmy*71a$.d=q2UJvQ$^-E1ev?yK?40?AC856b78PAvp@-+AM.W?c~waDTv0,B3zl1iw%vO9)BKj!jy7~r^wE3]d*T-@NwxfGl[ns7%KANUrxZ_9)ODbn-q(ifd)oMIA18&?By'*2%,lY+,!UmZHa]_8+TSP[td}bT-CL%NNDP3?Z*yqPzZpJL.g@_oYZZZ@f!r?*1+']Zj]ZqjdIrE93ZaoSS_`udf%hNKO=9j?aFhCl*?,uleMNZ1Z~ZE9FqKxu+Isz3ow_9L8eB^=3X9%1XjT_huv(S=Kofh9JKrEq.?bB!L`vCwRLC3@2y4WO-0'Ic%eNDY,x-y@1n30[^'z+cLCX]e[=7a8'W6k*?}q&'br-YB(.!`@fw0~&p`8-=Mnx6qys!X9TQW^09zZ@pU
MSI (s) (80:88) [11:29:10:821]: Executing op: FeaturePublish(Feature=SMServer,,Absent=2,Component=Ik{Op{5Kr=GT6Le$}XC3c6,M6L((V9pkVNH,10cG1+tmy*`TG?4+OQ_V,p$dVCsu8xeQf9Brt8)ud$Sf^SsJTSpso8TFvFZg+*V!vIFSk4eIY98NOU2f+BvOK_yzaR8Je9TA*L3kFh1Q^c{'C@}z5=0HxnJ+Ye5m?Bt&'[email protected][Q%j-V=`9aWmoOnwf@bG~tm6{U72@o$9HI1rY8sqD'n71MVZ?sjtIJ^RR~x(I9V?3bEV9=E%_oQj-dfO26gb,)~X?v_5H&}8OBC,Zd3FO*6x?^&vV^oAnT8W]VCJ5{1D?cF2hz^y{{p&uDdwpd}h8`NZJv_a3H!)feXUfw]v?_@*Otsy%B'YK$aq~=M9AbjW10uEDJQXE)3'L82.?,2W6FLDxVGn^9T&=1y~9]TMt7^XvHXTYuO[z=6}@L_^wh,(g}ZqJ^O1bEhS?r)iI.5E.A7i&@zDQdtV='FS(W8wl!b1yF'DVKLY={M5MYbn*wOxsSgjVY3D@oGP5W(_$7[fx&!R(pHF=T%$LsMp7?spYDG3w!zC?5B2{8,F)[H!uUfS0'_m?$WG=P,jT7WOo2W_*dsE@=5jq^lyW?1(8?&32w,NAkc8wJs8GCEu1_2Xc^g[?VhL-,XO~{,H,a]zRr,2=]XThvu.EBR0v?pCd&1@?-Rud!Nf*yt-S'NdXk~P99PFN(w0J9RAmQC40IY9AQKBcb!S?=CnT=EuzE1q=w)`V(40a'jdyXR+pN}`A.UP3IQjE(9xOtNZV!)e9YJ=NzOE[$(Itp!&{M^09-FPfKKbD1uIz}V_z3K^9t3U4Tvo(Gq8eyV`z3K^9b)@zEvo(Gq}1+M!-vLb9Y{kU8s)9cs`p`b,X*][=!CtK^UfdUy]u[kDa&5C?dr&Nb_m6L%E'Tes__*W=Cf)0-^yp**S{$*8j'~D=bv,m!@w5F5^Yvr?u^T??[Dr^?X5&DC{BJ]9S.IY?X_+EYCq`~aII17]HE$Y=G,N.-Z]Nu9F
MSI (s) (80:88) [11:29:10:862]: Executing op: FeaturePublish(Feature=SMConsole,,Absent=2,Component=-t's,QtH^Aw+6FO*=Se(iQRgqk%_g=dT63!k9!rD@dhrK&d7h=K@C5tXh+0WxiGiG5${}83t&igNy{fY&JO-tv~W3Ah1fGYB1.`B!^o%uu!H)9R}66fvSA0Wv%z,9-1jG9y?v}nwk!s?K=B`'Nk^.93`591RA^Ebzru^Hg?vMA6WScC*[V.DUtMfGl+Os98*Wc&+YY[2abg{3@n-]@5Gxvon=g76CVQ~Ijn^X9P2H12*)v(!KYwG+v*QS={[,{TMbA'(jZhl`KmU$?Vez&@)YK[mVm~2X&18E@])Ry4^X^KQ`vnk@+v{B?dAn}YD*9*5S_~w'M?2c?s8Sf^yA)9@nE@ABBSrt8T++.V{d4gb6,p$83`m4?OV9^r0F`IO[`o_-lb2}91AcKjfKCE2=q?*Gk,g'?2O7pkHrC*](^yu[K}-S9elzyj=2zt[iF(M2nb-z9sgF?29J6($ZQAS%izDO9oq$k`dG4]?OicWT^[Y=AlFJBP05%gId7HBQ9jDv?bh(2W~-B+J%ZHxQK2k4?Umi{dWK[GK_mG&(el!^AR,YT-X9P-m(9%C-l..z==Oh(RE,xmDS6=!lKz,O=&,deE`++iQ5VCXL[Y^Z?LB7r)u}k4n7=LtnTJwZA)eY8vfB@7vvdYD(a8ZU=qVm47sBI?iaZk6p!S]8?6D_x4Z7cJjqfl~xo!zh@7X%ORA?XADrzW?JWEfO9?9@$3t_Qr`{kPS!rsu19(OfCf'~0~Po4[nv@Xp]=P^LkdkaG14a99ww^FX2@Amv.^j+f3M*e)H?o6qr@fx9b'rGbrKH@FR8}kA.9^kv{98D@Qy?cq4uLo2o=_8G4&1&IqY(CeD&$F@G@MdV7cI5ewzftyD$`o_k=~X5yoL3!&A`NSB.WH!LA3(1Rmkk9?ethX(x,HWR9_OUZ=H!k3Xko]}oWUVJ@QG{ztU'eAplc=@70chp9&@F34p~'T)CfM[I(VWm9.a`6U-hvjpUZDg96]v?@_S7.CdN=Uj
MSI (s) (80:88) [11:29:10:908]: Executing op: ActionStart(Name=_StartNamedServices_CoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,,)
MSI (s) (80:88) [11:29:10:910]: Executing op: CustomActionSchedule(Action=_StartNamedServices_CoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,ActionType=3649,Source=BinaryData,Target=StartNamedServices,CustomActionData=HealthService System Center Management
APM)
MSI (s) (80:88) [11:29:10:913]: Executing op: ActionStart(Name=PublishProduct,Description=Publishing product information,)
MSI (s) (80:88) [11:29:10:918]: Executing op: CleanupConfigData()
MSI (s) (80:88) [11:29:10:918]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\5BA67A970AE3F4C4989BC10A4083CEE2\Patches 3: 2
MSI (s) (80:88) [11:29:10:918]: Executing op: RegisterPatchOrder(Continue=0,SequenceType=1,Remove=0)
MSI (s) (80:88) [11:29:10:918]: Note: 1: 1402 2: UNKNOWN\Products\5BA67A970AE3F4C4989BC10A4083CEE2\Patches 3: 2
MSI (s) (80:88) [11:29:10:923]: Executing op: ProductPublish(PackageKey={1B3B79AF-1391-4E6E-9BE2-2BD0832DADE7})
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:942]: Executing op: UpgradeCodePublish(UpgradeCode={4F70C213-6F45-4AA0-8994-1A09CBF27D77})
MSI (s) (80:88) [11:29:10:947]: Executing op: SourceListPublish(,,DiskPromptTemplate=Please Insert Disk 1,,NumberOfDisks=1)
MSI (s) (80:88) [11:29:10:947]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList 3: 2
MSI (s) (80:88) [11:29:10:948]: Executing op: ProductPublishClient(,,)
MSI (s) (80:88) [11:29:10:949]: Executing op: SourceListRegisterLastUsed(SourceProduct={79A76AB5-3EA0-4C4F-89B9-1CA00438EC2E},LastUsedSource=E:\SCSM2012sp1\amd64\Setup\Server\)
MSI (s) (80:88) [11:29:10:949]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (80:88) [11:29:10:963]: Specifed source is already in a list.
MSI (s) (80:88) [11:29:10:963]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (80:88) [11:29:10:963]: Adding new sources is allowed.
MSI (s) (80:88) [11:29:10:963]: Set LastUsedSource to: E:\SCSM2012sp1\amd64\Setup\Server\.
MSI (s) (80:88) [11:29:10:963]: Set LastUsedType to: n.
MSI (s) (80:88) [11:29:10:963]: Set LastUsedIndex to: 1.
MSI (s) (80:88) [11:29:10:964]: Executing op: ActionStart(Name=_EnabledDiscoveryDataAuthorization,,)
MSI (s) (80:88) [11:29:10:979]: Executing op: CustomActionSchedule(Action=_EnabledDiscoveryDataAuthorization,ActionType=1537,Source=BinaryData,Target=EnabledDiscoveryDataAuthorization,)
MSI (s) (80:88) [11:29:11:086]: Executing op: ActionStart(Name=_RegisterVssExpressWriterSM,,)
MSI (s) (80:88) [11:29:11:104]: Executing op: CustomActionSchedule(Action=_RegisterVssExpressWriterSM,ActionType=1089,Source=BinaryData,Target=RegisterVssExpressWriterSM,CustomActionData=SCSMSMDBDOMAIN,DOMAIN|ServiceManager)
MSI (s) (80:EC) [11:29:11:173]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI36AB.tmp, Entrypoint: RegisterVssExpressWriterSM
CAPACK: Extracting custom action to temporary directory: C:\Windows\Installer\MSI36AB.tmp-\
CAPACK: CLR version v2.0.50727 is installed.
CAPACK: CLR version v2.0.50727 is detected.
CAPACK: CLR version v4.0.30319 is installed.
CAPACK: CLR version v4.0.30319 is detected.
CAPACK: Binding to CLR version v2.0.50727
Calling custom action CAManaged!Microsoft.MOMv3.Setup.VssWriterCAs.RegisterVssExpressWriterSM
RegisterVssExpressWriter: Registering VSS express writer.
MSI (s) (80:EC) [11:29:15:881]: NOTE: custom action _RegisterVssExpressWriterSM unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
MSI (s) (80:88) [11:29:15:884]: Executing op: ActionStart(Name=_Rollback_RegisterVssExpressWriterSM,,)
RegisterVssExpressWriter: Registered VSS express writer.
MSI (s) (80:88) [11:29:15:896]: Executing op: CustomActionSchedule(Action=_Rollback_RegisterVssExpressWriterSM,ActionType=1345,Source=BinaryData,Target=RemoveVssExpressWriterSM,)
MSI (s) (80:88) [11:29:15:975]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=639325328)
MSI (s) (80:88) [11:29:42:385]: An error occured while refreshing environment variables updated during the installation of ''. Some users logged on to the machine may not see these changes until they log off and then log back on.
MSI (s) (80:88) [11:29:42:445]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (80:88) [11:29:42:446]: User policy value 'DisableRollback' is 0
MSI (s) (80:88) [11:29:42:446]: Machine policy value 'DisableRollback' is 0
MSI (s) (80:88) [11:29:42:452]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (80:54) [11:29:42:890]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIB293.tmp, Entrypoint: StopNamedServices
MSI (s) (80:BC) [11:29:43:709]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIB40B.tmp, Entrypoint: ExecNetFx
MSI (s) (80:BC) [11:29:43:731]: Generating random cookie.
MSI (s) (80:BC) [11:29:44:395]: Created Custom Action Server with PID 4800 (0x12C0).
MSI (s) (80:F0) [11:29:45:368]: Running as a service.
MSI (s) (80:F8) [11:29:45:393]: Hello, I'm your 32bit Elevated custom action server.
MSI (s) (80:F0) [11:29:45:460]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIBCA7.tmp, Entrypoint: ExecNetFx
MSI (s) (80:F4) [11:29:45:593]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIBCF6.tmp, Entrypoint: ExecNetFx
MSI (s) (80:EC) [11:29:45:662]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIBD83.tmp, Entrypoint: ExecNetFx
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.ConsoleFramework.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.Foundation.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.Controls.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.ViewFramework.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.WpfViews.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.ExtendedControls.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\CommunicatorAPIInterop.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\CommunicatorPrivateInterop.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "Microsoft.EnterpriseManagement.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /queue:2
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe update /queue
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
MSI (s) (80:9C) [11:29:50:885]: Invoking remote custom action. DLL: C:\Windows\Installer\MSID199.tmp, Entrypoint: ConfigureSDKConfigService
ConfigureSDKConfigService: Custom action data property value. 1 OMCFG
ConfigureSDKConfigService: RHS so start services. 1
CAStartServices: CAStartServices was passed . OMCFG
CAStartServices: Checking if service already started. OMCFG
CAStartServices: Attempting to start service. OMCFG
ConfigureSDKConfigService: CAStartServices succeeded!. OMCFG
MSI (s) (80:F4) [11:30:01:168]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIF733.tmp, Entrypoint: ConfigureSDKConfigService
ConfigureSDKConfigService: Custom action data property value. 1 OMSDK
ConfigureSDKConfigService: RHS so start services. 1
CAStartServices: CAStartServices was passed . OMSDK
CAStartServices: Attempting to start service. OMSDK
MSI (s) (80:A0) [11:30:04:965]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI82C.tmp, Entrypoint: WaitForSDKServiceStart
CAPACK: Extracting custom action to temporary directory: C:\Windows\Installer\MSI82C.tmp-\
CAPACK: CLR version v2.0.50727 is installed.
CAPACK: CLR version v2.0.50727 is detected.
CAPACK: CLR version v4.0.30319 is installed.
CAPACK: CLR version v4.0.30319 is detected.
CAPACK: Binding to CLR version v2.0.50727
Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.WaitForSDKServiceStart
WaitForSDKServiceStart:Entering
WaitForSDKServiceStart: Error: The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection.,
Stack:    at Microsoft.EnterpriseManagement.Common.Internal.ExceptionHandlers.HandleChannelExceptions(Exception ex)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint(EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.ConstructEnterpriseManagementGroupInternal(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore clientCallback)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.RetrieveEnterpriseManagementGroupInternal(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Connect(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
   at Microsoft.EnterpriseManagement.EnterpriseManagementGroup.InternalInitialize(EnterpriseManagementConnectionSettings connectionSettings, EnterpriseManagementGroupInternal internalsProxy)
   at Microsoft.EnterpriseManagement.EnterpriseManagementGroup.Connect(EnterpriseManagementConnectionSettings connectionSettings)
   at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.WaitForSDKServiceStart(Session session)
MSI (s) (80:A0) [11:30:36:809]: NOTE: custom action _WaitForSDKServiceStart unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
CustomAction _WaitForSDKServiceStart returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (80:88) [11:30:37:805]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1156471542,LangId=0,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (80:88) [11:30:37:805]: Executing op: DialogInfo(Type=0,Argument=0)
MSI (s) (80:88) [11:30:37:806]: Executing op: DialogInfo(Type=1,Argument=Microsoft System Center 2012 - Service Manager)
MSI (s) (80:88) [11:30:37:807]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ea.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835eb.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ec.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ed.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ee.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ef.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f0.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f1.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f2.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f3.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f4.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f5.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f6.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f7.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f8.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f9.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835fa.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835fb.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835fc.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835fd.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835fe.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ff.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\8883600.rbf)
MSI (s) (80:88) [11:30:40:009]: Executing op: ActionStart(Name=_Rollback_RegisterVssExpressWriterSM,,)
MSI (s) (80:88) [11:30:40:013]: Executing op: ProductInfo(ProductKey={79A76AB5-3EA0-4C4F-89B9-1CA00438EC2E},ProductName=Microsoft System Center 2012 - Service Manager,PackageName=SM.msi,Language=0,Version=117771097,Assignment=1,ObsoleteArg=0,ProductIcon=ServiceManager.ico,,PackageCode={1B3B79AF-1391-4E6E-9BE2-2BD0832DADE7},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
MSI (s) (80:88) [11:30:40:029]: Executing op: CustomActionRollback(Action=_Rollback_RegisterVssExpressWriterSM,ActionType=1345,Source=BinaryData,Target=RemoveVssExpressWriterSM,)
MSI (s) (80:EC) [11:30:40:772]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI920E.tmp, Entrypoint: RemoveVssExpressWriterSM
CAPACK: Extracting custom action to temporary directory: C:\Windows\Installer\MSI920E.tmp-\
CAPACK: CLR version v2.0.50727 is installed.
CAPACK: CLR version v2.0.50727 is detected.
CAPACK: CLR version v4.0.30319 is installed.
CAPACK: CLR version v4.0.30319 is detected.
CAPACK: Binding to CLR version v2.0.50727
Calling custom action CAManaged!Microsoft.MOMv3.Setup.VssWriterCAs.RemoveVssExpressWriterSM
RemoveVssExpressWriter: Unregistering VSS express writer.
MSI (s) (80:EC) [11:30:43:808]: NOTE: custom action _Rollback_RegisterVssExpressWriterSM unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
RemoveVssExpressWriter: VSS express writer unregister succeeded.
MSI (s) (80:88) [11:30:43:834]: Executing op: ActionStart(Name=_RegisterVssExpressWriterSM,,)
MSI (s) (80:88) [11:30:43:853]: Executing op: ActionStart(Name=_EnabledDiscoveryDataAuthorization,,)
MSI (s) (80:88) [11:30:43:862]: Executing op: ActionStart(Name=PublishProduct,Description=Publishing product information,)
MSI (s) (80:88) [11:30:43:892]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Net,SecurityDescriptor=BinaryData,BinaryType=1,,)
MSI (s) (80:88) [11:30:43:898]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList,SecurityDescriptor=BinaryData,BinaryType=1,,)
MSI (s) (80:88) [11:30:43:910]: Executing op: RegRemoveValue(Name=LastUsedSource,Value=#%n;1;E:\SCSM2012sp1\amd64\Setup\Server\,)
MSI (s) (80:88) [11:30:43:916]: Executing op: RegCreateKey()
MSI (s) (80:88) [11:30:43:925]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2,SecurityDescriptor=BinaryData,BinaryType=1,,)
MSI (s) (80:88) [11:30:43:930]: Executing op: RegRemoveValue(Name=Clients,Value=[~]:,)
MSI (s) (80:88) [11:30:43:937]: Executing op: RegCreateKey()
MSI (s) (80:88) [11:30:43:944]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Media,SecurityDescriptor=BinaryData,BinaryType=1,,)
MSI (s) (80:88) [11:30:43:951]: Executing op: RegRemoveValue(Name=1,Value=;,)
MSI (s) (80:88) [11:30:43:959]: Executing op: RegCreateKey()
MSI (s) (80:88) [11:30:43:980]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Media,,BinaryType=1,,)
MSI (s) (80:88) [11:30:43:986]: Executing op: RegRemoveValue(Name=DiskPrompt,Value=Please Insert Disk 1,)
MSI (s) (80:88) [11:30:43:994]: Executing op: RegRemoveKey()
MSI (s) (80:88) [11:30:43:994]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Media 3: 2
MSI (s) (80:88) [11:30:43:999]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Net,,BinaryType=1,,)
MSI (s) (80:88) [11:30:44:005]: Executing op: RegRemoveValue(Name=1,Value=#%E:\SCSM2012sp1\amd64\Setup\Server\,)
MSI (s) (80:88) [11:30:44:011]: Executing op: RegRemoveKey()
MSI (s) (80:88) [11:30:44:011]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Net 3: 2
MSI (s) (80:88) [11:30:44:017]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList,,BinaryType=1,,)

Cannot add a New Essbase server into the EAS Console

Hi can someone assist me...........
I have installed Essbase on a new / additional server (that all went rather well, its not hard just pressing NEXT, NEXT, NEXT).
I then used a essadmin account to configure, i have to say its not the same as the other essbase server (so i am wondering if this was the start of my problems)!!. I did not use the same essadmin as the password is unknown its not known and the orginal installation was not recorded. I do however know and used the admin account for the shared services.
I then logged into EAS Console (single instance of the EAS, with a plan to add 3 new essbase servers to this console over the next couple of days.) i added the new essbase server, then externalised and all was happy with the world. SUCCESS :-)
I closed EAS, and went back in and thats where the fun started, it then stated that it could not connect and i recieved the invalid login message in essbase. I have read some forums and followed the advise of going into Shared Services and manually removing the new essbase server registry under projects, cleared down and replaced the essbase.sec file etc etc to the originals and stop/started the services.
So can anyone help on what my next steps should be?, I don't want to run off and re-register again via the console for shared services if i need to use the original essadmin password in my configuration. Any help will be gratefully recieved.

Hi can someone assist me...........
I have installed Essbase on a new / additional server (that all went rather well, its not hard just pressing NEXT, NEXT, NEXT).
I then used a essadmin account to configure, i have to say its not the same as the other essbase server (so i am wondering if this was the start of my problems)!!. I did not use the same essadmin as the password is unknown its not known and the orginal installation was not recorded. I do however know and used the admin account for the shared services.
I then logged into EAS Console (single instance of the EAS, with a plan to add 3 new essbase servers to this console over the next couple of days.) i added the new essbase server, then externalised and all was happy with the world. SUCCESS :-)
I closed EAS, and went back in and thats where the fun started, it then stated that it could not connect and i recieved the invalid login message in essbase. I have read some forums and followed the advise of going into Shared Services and manually removing the new essbase server registry under projects, cleared down and replaced the essbase.sec file etc etc to the originals and stop/started the services.
So can anyone help on what my next steps should be?, I don't want to run off and re-register again via the console for shared services if i need to use the original essadmin password in my configuration. Any help will be gratefully recieved.

Adding new WhoIs server

Similar Messages

Maybe you are looking for