Deployment Plan not replicating across clusters

I am deploying application in clustred environment, where Admin and one ms are in one physical box and other Managed Server is in another physical box.
When redoplying the application after making few changes, viz:
1. Updating the resource file.
2. Updating the deployment paln file.
3. Upgrading the application, this changes are working in only one managed server but not in the other managed server which is other physical box. Once you manually copy the deployment paln file, the second managed server also reflects the changes.
Even bouncing the server, will not reflect the changes.
Any suggestions?

RAC supports a mixture of storage types.. raw, file system and ASM.
I believe you can have several options..
1. you can continue to maintain your FLASH on ASM with the RMAN backups only going to the shared filesystem location
2. can maintain the RMAN backups on ASM and then when you backup from disk to tape (D2T) you can restore from tape to populate the development /test environments
3 like you say can maintain the entire FLASH area on shared file system.
When sharing a common area between development, test and production environments with some these critical files? hmmm! security & safety of files comes to my mind as a concern..
You have not mentioned the O/S details,,, however the cost factor involved in having a third party file system in the mix should also be considered.

Similar Messages

Session not replicated in clustered oc4j instances

The application is deployed to two clustered oc4j instances(A and B) and is configured to use PEER replication protocol. After logging into the application(say A handled the request, created and stored a user object in http session), we shutdown A, and click on application link, the request is routed to B, but B shows no user object in http session is found, this happens in a servlet filter. Could somebody provide some suggestions why?

Hmm, OK. Then we need to dig in a little further.
Can you post what the orion-application.xml file looks like for these applications?
It has the <cluster> tag set in it.
You can find it in $ORACLE_HOME/j2ee/home/application-deployments/<app-name>
Are these clustered OC4J instances on the same server -- if so, did you set allow-colocation="false", which would prevent the replica from being stored on the same physical host, and thus not be avaialble when you need it?
You can enable logging for the clsuter session manager -- you can acess the logging propeties page in ASC and then set the "oracle.j2ee.cluster" to the FINEST level to start pumping some log messages into the log file.
Note: in 10.1.3.0 the settings are not persisted when made via ASC -- you have to enter them manually in the j2ee/<instance-name>/config/j2ee-logging.xml file. In 10.1.3.1 the settings are persisted automatically into this file.
The easiest way to see the log messages in the file is using the Log Viewer function in ASC as well. Look for the "Diagnostics" log in the particular Oc4J instance where the app is deployed.
cheers
-steve-

Transactional Replication Not replicating non-clustered Indexes

Hi
I have created a transactional replication.I am sure that I have configured it to replicate Non-Clustered indexes,
but It does not do so.
I tried several times to reinitialize the subscription,but still no luck.
Regards

It is True for sure.
But the problem is solved.I had to wait until the Initialize process get completed.
But I am sure that this problem happened before.Sometimes it works fine but sometimes not.
Hi ArashMasroor,
According to your description, it seems that you encounter the issue that non-clustered indexes property is reset to “False” sometimes.
To work around this issue, you can use a post-replication SQL script to create the indexes. Whatever articles you’re publishing open up the indexes drop down list of the article in object explorer, right-click on an index and levitate over Script Index as,
then Create-to, then click New Query Window editor.
Up will pop up a new query window with the resulting index. Work your way through all the indexes on all the articles of the publication, copy and pasting just the create index line and below of each script, pull them all together into one query window.
Once you’re done find a safe folder somewhere on your hard drive and save the SQL query as an .sql file with a sensible name. Then you can execute this script after applying the Snapshot. For more details, please review this
blog.
There is also a similar thread for your reference.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/b0f3870d-1a65-4384-a17b-96825ec5f098/transactional-replication-nonclustered-indexes-not-copying?forum=sqlreplication
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

FileOutputStream - upload not replicated

Hi,
I have the following problem.
We have an environment with a central instance with 1 server process, and 4 dialog instances, each with 4 server processes.
I created an iView, which should save a file on the filesystem, with the following code:
public void onGenerate(Event event) {
 IPortalComponentRequest rq = (IPortalComponentRequest) getRequest();
 String result = generateXML("Location", rq);
 //result contains XML data
 xmlGenerationBean.setXmlResult(result);
 log.info(request.getPublicResourcePath());
 log.info(request.getPrivateResourcePath());
 String xmlPath = request.getPrivateResourcePath() + File.separator + "xml" + File.separator + "filename.xml";
 InputStream is = null;
 try {
 is = new ByteArrayInputStream(result.getBytes("UTF-8"));
 } catch (UnsupportedEncodingException e) {
 // TODO Auto-generated catch block
 e.printStackTrace();
 if (is != null) {
 try {
 FileOutputStream fos = new FileOutputStream(xmlPath);
 int c;
 while ((c = is.read()) != -1) {
 fos.write(c);
 } catch (FileNotFoundException e1) {
 // TODO Auto-generated catch block
 e1.printStackTrace();
 } catch (IOException e1) {
 // TODO Auto-generated catch block
 e1.printStackTrace();
The result of this method is the xml file gets written, but is not replicated across all 21 .../serverX/... folders on all servers. The file location is specified in the bold line of code
How can I make this code work, so the file is saved and then replicated across all locations?
Any help will be rewarded a nice cold glass of beer
Kind regards,
Robin van het Hof

No one any bright ideas?

JNDI bindings not being replicated across servers in a cluster

According to the Weblogic Server documentation, JNDI bindings are
 automatically replicated across the servers in a cluster.
 http://www.weblogic.com/docs45/classdocs/weblogic.jndi.WLContext.html#REPLIC
 ATE_BINDINGS
 This is not proving to be true in my testing. Perhaps it's "just broken", or
 perhaps my cluster isn't correctly configured...
 Here is a reproducible case. Install the following on two or more servers in
 a cluster. You'll need to change line 26 of test1 to reference one of the
 servers explicitly.
 Test 1 works fine, since both web servers connect to the same server for
 JNDI usage. The test should return the last host to hit the page, along with
 the current host name. Alternating between servers in the cluster will
 alternate the results. However, the fact that I'm specifically naming a
 server in the cluster breaks the whole point of clustering -- if that server
 goes down, the application ceases to function properly.
 Test 2, which is supposedly the right way to do it, does not work, an error
 message is logged:
 Tue Jan 04 08:17:15 CST 2000: <ConflictHandler> ConflictStart
 lastviewhost:java.lang.String (from
 [email protected]:[80,80,7002,7002,-1])
 And then both servers begin to report that they have been the only server to
 hit the page. Alternating between servers will have no effect -- both
 servers are looking solely at their own copies of the JNDI tree. No
 replication is occurring.
 What is up with this? Any ideas?
 Tim
 [test1.jsp]
 [test2.jsp]


1. yes
 <JMSConnectionFactory AllowCloseInOnMessage="false"
 DefaultDeliveryMode="Persistent" DefaultPriority="4"
 DefaultTimeToLive="0"
 JNDIName="xlink.jms.factory.commerceFactory"
 MessagesMaximum="10" Name="xlink.jms.factory.commerceFactory"
 OverrunPolicy="KeepOld" Targets="bluej,biztalk-lab,devtestCluster"/>
 2. No I am just using the jndi name of the queue.
 This is an example of how I send a message:
 Context ctx = new InitialContext();
 QueueConnectionFactory qconFactory;
 QueueConnection qcon;
 QueueSession qsession;
 QueueSender qsender;
 Queue queue;
 ObjectMessage msg;
 qconFactory = (QueueConnectionFactory) ctx.lookup("xlink.jms.factory.commerceFactory");
 qcon = qconFactory.createQueueConnection();
 qsession = qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
 queue = (Queue) ctx.lookup("xlink.jms.queue.biztalk-lab.OrdrspImport");
 qsender = qsession.createSender(queue);
 msg = qsession.createObjectMessage(reportExecutorContainer);
 qcon.start();
 qsender.send(msg);
 qsender.close();
 qsession.close();
 qcon.close();
 3. I don't know those setting (wl 6.1sp7)

Weblogic deployment plan will not override variables (Weblogic 10.3.5).

I am having some trouble trying to adjust the deployment settings of our application in weblogic. I feel what I'm trying to do ought to be quite simple, but it's not working as expected.
I am just trying to override the context-root in weblogic.xml and the JNDI name for the data source, so these can both be configured at deployment time.
I have removed the application.xml from the ear file, so that shouldn't be affecting the overrides.
What I have so far:
weblogic.xml:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-web-app xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.2/weblogic-web-app.xsd">
<context-root>mosaic</context-root>
<resource-description>
<res-ref-name>jdbc/LogicalDS</res-ref-name>
<jndi-name>LogicalDS</jndi-name>
</resource-description>
web.xml
<?xml version='1.0' encoding='UTF-8'?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<resource-ref>
<description>A logical reference to the datasource - mapped in deployment plan</description>
<res-ref-name>jdbc/LogicalDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
plan.xml
<?xml version="1.0" encoding="UTF-8"?>
<wls:deployment-plan xmlns:wls="http://xmlns.oracle.com/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/j2ee_1_4.xsd" global-variables="true">

<wls:application-name>mosaic.ear</wls:application-name>
<wls:variable-definition>
<wls:variable>
<wls:name>datasource_name</wls:name>
<wls:value xsi:nil="true"></wls:value>
<wls:description>The name of the datasource to map to the mosaic application</wls:description>
</wls:variable>
<wls:variable>
<wls:name>new_context_root</wls:name>
<wls:value xsi:nil="true"></wls:value>
<wls:description>URL to deploy Mosaic at</wls:description>
</wls:variable>
</wls:variable-definition>
<wls:module-override>
<wls:module-name>mosaic.war</wls:module-name>
<wls:module-type>war</wls:module-type>
<wls:module-descriptor>
<wls:root-element>weblogic-web-app</wls:root-element>
<wls:uri>WEB-INF/weblogic.xml</wls:uri>
<wls:variable-assignment>
<wls:name>new_context_root</wls:name>
<wls:xpath>/weblogic-web-app/context-root</wls:xpath>
<wls:operation>replace</wls:operation>
</wls:variable-assignment>
<wls:variable-assignment>
<wls:description>Data source for mosaic application</wls:description>
<wls:name>datasource_name</wls:name>
<wls:xpath>/weblogic-web-app/resource-env-description/resource-env-ref-name</wls:xpath>
<wls:operation>replace</wls:operation>
</wls:variable-assignment>
<wls:variable-assignment>
<wls:name>datasource_name</wls:name>
<wls:xpath>/weblogic-web-app/resource-description/[res-ref-name="jdbc/LogicalDS"]/jndi-name</wls:xpath>
<wls:operation>replace</wls:operation>
</wls:variable-assignment>
</wls:module-descriptor>
</wls:module-override>
</wls:deployment-plan>
Nothing happens when I use the deployment plan, and neither of the variables appear under the Deployment Plan configuration screens in the admin console. From what I understand, I should at least be asked for these variables, since I have specified that they are null in the deployment plan.
When I use WLST to browse the tree, I find that the runtime configuration just stays as the values in the deployment descriptors.
I have verified the deployment plan is being used in the general tab of the admin console.
Can anyone help me find out what I am doing wrong here? If I don't create a data source called LogicalDS, I get errors about this, suggesting it is not correctly overriding. I am puzzled to why I do not see any variables to specify though..

The documentation implies that this is not the case - see:
http://docs.oracle.com/cd/E24329_01/web.1211/e24443/export.htm#autoId13
'Assigning Null Variables to Require Administrator Input'.
However, require administrator input where? My thoughts were that this option would appear in the admin console under 'deployment plan'. However, although I have specified resource dependencies in the deployment descriptors, and the plan, nothing appears under 'resource dependencies' for the application.
Is the only way to change the context-root deployment URL by actually manually editing an XML file?
To me that seems primitive and will cause us support issues when distributing our application - is there any other way I can enable the ability to specify the data source name and context-root through the web console prior to/during deployment?
Edited by: user12032953 on 11-Jun-2012 07:20

Deployment plan cookie-name not applying

I have a ear containing multiple wars. The EAR has a weblogic-application.xml containing:
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-application xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/920/weblogic-application.xsd">
<application-param>
<param-name>webapp.encoding.default</param-name>
<param-value>UTF-8</param-value>
</application-param>
<session-descriptor id="ID000193">
<cookie-name>ZSESSIONID</cookie-name>
<timeout-secs>900</timeout-secs>
<id-length>14</id-length>
<sharing-enabled>true</sharing-enabled>
<url-rewriting-enabled>false</url-rewriting-enabled>
</session-descriptor>
</weblogic-application>
That is the only place the cookie-name ZSESSIONID is mentioned in any config file in the ear.
I have a deployment plan that has in part:
<deployment-plan xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-deployment-plan.xsd" global
-variables="false">
<application-name>myapp.ear</application-name>
<variable-definition>
<variable>
<name>SessionDescriptor_CookieName_125796842519611</name>
<value>XSESSIONID</value>
</variable>
</variable-definition>
<module-override>
<module-name>myapp.ear</module-name>
<module-type>ear</module-type>
<module-descriptor external="false">
<root-element>weblogic-application</root-element>
<uri>META-INF/weblogic-application.xml</uri>
<variable-assignment>
<name>SessionDescriptor_CookieName_125796842519611</name>
<xpath>/weblogic-application/session-descriptor/cookie-name</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
<module-descriptor external="false">
<root-element>application</root-element>
<uri>META-INF/application.xml</uri>
</module-descriptor>
</module-override>
The change is not having any effect. I know that the plan is being applied since I see "References were found in deployment plan for module ..." in my startup and if I intentionally syntax error the file it fails to launch. This is Weblogic 10.0 MP1 / java 1.5. Any suggestions on how to troubleshoot this or what might cause it?
Edited by: jhmartin on Dec 4, 2009 11:48 AM

Hi,
I have developed a Simple TestCase with Step By Step Instructions It's Working fine for me in WLS-10.3. Please let me know if you are following any thing else...
http://jaysensharma.wordpress.com/2009/12/16/updating-cookiename-using-plan-xml/
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (Wonders of WebLogic Are Here)
Edited by: Jay SenSharma on Dec 16, 2009 1:23 PM

Replacing web.xml values with a deployment plan. Not working on WL 10.3.2

Hi All-
I am trying to replace a value from web.xml with one in a weblogic deployment plan. I deployed the application on WL 10.3.2 and used the deployment plan below. No matter what I do it doesn't seem to want to take the value.
web.xml:
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<context-param>
<param-name>TokenGroup</param-name>
<param-value>oldvalue</param-value>
</context-param>
</web-app>
Deployment Plan:
<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd"
global-variables="false">
<application-name>APPName</application-name>
<variable-definition>
<variable>
<name>TokenGroup</name>
<value>Key123456</value>
</variable>
</variable-definition>
<module-override>
<module-name>APPName.war</module-name>
<module-type>war</module-type>
<module-descriptor external="false">
<root-element>web-app</root-element>
<uri>WEB-INF/web.xml</uri>
<variable-assignment>
<name>TokenGroup</name>
<xpath>/web-app/context-param/[param-name="TokenGroup"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
</module-override>
</deployment-plan>
I've also tried other formats for the xpath such as:
/web-app/context-param/{param-name="TokenGroup"}/param-value
/web-app/context-param[param-name="TokenGroup"]/param-value
Any ideas why this doesnt work?
Thanks,
Joe

"web.xml"
<?xml version='1.0' encoding='WINDOWS-1252'?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<context-param>
<param-name>name</param-name>
<param-value>Joe</param-value>
</context-param>
<context-param>
<param-name>password</param-name>
<param-value>password</param-value>
</context-param>
<servlet>
<servlet-name>ParameterServlet</servlet-name>
<servlet-class>ParameterServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>ParameterServlet</servlet-name>
<url-pattern>/ParameterServlet</url-pattern>
</servlet-mapping>
</web-app>
ParameterServlet
import java.io.IOException;
import javax.servlet.ServletConfig;
import javax.servlet.ServletContext;
import javax.servlet.ServletException;
import javax.servlet.ServletOutputStream;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
public class ParameterServlet extends HttpServlet {
private String dbName = "";
private String dbPassword = "";
public void init(ServletConfig config) throws ServletException {
super.init(config);
ServletContext context = getServletContext();
dbName = context.getInitParameter("name");
dbPassword = context.getInitParameter("password");
public void doGet(HttpServletRequest req, HttpServletResponse res)
throws IOException {
ServletOutputStream out = res.getOutputStream();
res.setContentType("text/html");
out.println("<html><head><title>Basic Servlet</title></head>");
out.println("<body>Database username is " + dbName);
out.println(" Database password is " + dbPassword + "");
out.println("</body></html>");
"Plan.xml"
<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd" global-variables="false">
<application-name>virtual</application-name>
<variable-definition>
<variable>
 <name>name</name>
 <value>akshay1</value>
 </variable>
 <variable>
 <name>password</name>
 <value>koul1</value>
 </variable>
</variable-definition>
<module-override>
<module-name>virtual</module-name>
<module-type>war</module-type>
<module-descriptor external="false">
<root-element>web-app</root-element>
<uri>WEB-INF/web.xml</uri>
 <variable-assignment>
 <name>name</name>
 <xpath>/web-app/context-param/[param-name="name"]/param-value</xpath>
 <operation>replace</operation>
 </variable-assignment>
 <variable-assignment>
 <name>password</name>
 <xpath>/web-app/context-param/[param-name="password"]/param-value</xpath>
 <operation>replace</operation>
 </variable-assignment>
</module-descriptor>
</module-override>
<config-root>C:\DOCUME~1\user\LOCALS~1\Temp\user\.\config\deployments\virtual\plan</config-root>
</deployment-plan>
It works for me... I think your "web.xml" is causing the issue.
Try replacing
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
with
<?xml version='1.0' encoding='WINDOWS-1252'?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
Hope this helps.
-Akshay

Plan driven procurement: PO not replicated at backend

Hi Experts,
I am working with extended classic scenario (SRM 7.0 and ECC 6.0).
If I create a shopping cart and then PO at SRM, this PO is transfer to ECC sucessfully.
But for external requirements, purchase order is not replicated into ECC. So, if purchase requisitions is created at backend, transfer to SRM, PO created at SRM without errors, then PO is not replicated at backend.
No errors appear at SLG1 nor RZ20 nor SMQ1/2.
After debugging I found out that SUBTYPE field from BBP_PDIGP table is empty.
Any idea how can this issue could be solved? How can be PO replicated at ECC?
Thanks in advance!
Best Regards,
Martín Amat

Hello,
You can check if there is an error returning from backend.
Follow the steps below:
- Breakpoint at FM B46B_DPO_TRANSFER;
- SE37 BBP_PD_PO_TRANSFER_EXEC, enter PO header GUID and execute;
- Program will stop at FM where the BP was set.
- Look for statement CALL FUNCTION 'BBP_PO_INBOUND' DESTINATION lv_destination;
- F6 or F5 to debug into ERP (2nd session will start). Here you can check the table lt_bapi_return in order to check the result.
If you have a RFC with dialog user, you can debug through the ECC system and check why and when the error message is generated.
Regards,
Ricardo

Resource plan not migrating to all targeted cluster members

Hi,
We got an environment setup like:
Physical machine 1: AdminServer, OSB1, WLS1
Physical machine 2: OSB2, WLS2
Where we have put OSB[1,2] into a cluster and WLS[1,2] into a cluster. The servers are running WLS 10.3.3.4.
The problem is that: When creating a new connectionFactory for the DBAdapter, the plan.xml is only updated on 1 machine (not both of them). In my setup, it is always physical machine 1 that gets the updated plan.xml
I looked at the target for the deployment, and it is set for AdminServer and OSBCluster (meaning, OSB1 and OSB2). And when going into the "Monitoring -> Outbound Connection Pools", I can also see that only the AdminServer and OSB1 has an outbound connection pool.
To fix this, I've had to use SCP from OSB1 -> OSB2 for the plan.xml and then doing a redeploy of the DBAdapter. Then, I see an outbound connection from OSB2.
Have I miss understood something? Shouldn't the configurations (plan.xml) be replicated across all targeted members, in case one servers fails?
Best Regards,
Mathias

hello,
          and what about ServerAffinity (to be set on the ConnectionFactory-level)? Should be "false". Antoher explanation is that your cluster is out of sync (check, if multicast has been set correctly).
          load balancing and server affinity for dd
          regards,
          makiey

Failover is not working in clustering

we installed infrastructure in the one system and added 2 instances app1.mycompany.com,app2.mycompany.com into it.
for loadbalancing we r using webcache.
we configured origin servers,site definitions,site-server mappings.
in the cluster two instances showing up.
that we can see in health monitor in Up/Down* parameter of web cache administrator console.
we deployed same ear in two instances.
but when i down one instance say app1.mycompany.com,
In the health monitor its not showing up DOWN parameter for host: app1.mycompany.com.same for UP also.
immediately its not showing changes when i am testing failover.
Is webcache loadbalancing is Round robin based ?
when i down one of the instances session replication is not happening properly.sometimes session expired is coming.
when 2 instances r up if user access application all the requests r coming to one instance if down that instance session expired is coming.
i think failover is not working in clustering.
i checked replication properties and added <distributable> tag in both the instances.
in webcache console page what will sessionbinding will do?i have not configured anything.

Why are you using Webcache?
Web cache will certainly work, but its more common role is to more access as a simple load balancer over HTTP servers, not OC4J instances.
What I'd do is to simplify your situation to verify you have the server setup correctly.
That means using the Oracle HTTP Server which will be part of your cluster as the common routing point. OHS and mod_oc4j are session state aware and know about all the OC4J instances. In the situation where an OC4J instance dies for some reason, mod_oc4j will know to which other OC4J instance(s) the request can be routed to pickup the replicated session state.
Once you have verified that the failover is working on the backend, you can then configure another OHS instance and position webcache in front of them to act as a request router and failover handler for when the OHS instances are inactive.
The Enterprise Deployment Guide offers some guidance in typical architectures, well worth a read.
cheers
-steve-

Session not replicated in WL6.1

          We are having session-not-replicated problem in WL6.1 Clustering.
          We have 3 servers on different machines running WL6.1 sp1, 1 is running the admin
          server and the
          other 2 are running as managed weblogic server.
          We have a web application that has been deployed to the cluster and is set
          for PersistantStoreType equal to replicated.
          We are using a Cisco Local Redirector with "sticky load balancing" infront of
          the servers.
          In our applications, most of JSP pages can modify the session data using session.setAttribute().
          And we use session.removeAttribute() to clean a session data.
          session.setAttribute("mysession1", data1);
          ....some codes......
          if (session.getAttribute("mysession") != null)
               session.removeAttribute("mysession");
          session.setAttribute("mysession", data2);
          With session.removeAttibute() in our codes, some session data is not replicated
          to secondary server.
          We checked all session data in secondary server after shutting down the primary
          server.
          But if we comment out all session.removeAttribute() methods, failovers tested
          successfully.
          All our session data is serializable. Some are String and Some are Objects.
          Is this a known problems in WL6.1? Anyone has any idea?
          thanks,
          Hong


          We are having session-not-replicated problem in WL6.1 Clustering.
          We have 3 servers on different machines running WL6.1 sp1, 1 is running the admin
          server and the
          other 2 are running as managed weblogic server.
          We have a web application that has been deployed to the cluster and is set
          for PersistantStoreType equal to replicated.
          We are using a Cisco Local Redirector with "sticky load balancing" infront of
          the servers.
          In our applications, most of JSP pages can modify the session data using session.setAttribute().
          And we use session.removeAttribute() to clean a session data.
          session.setAttribute("mysession1", data1);
          ....some codes......
          if (session.getAttribute("mysession") != null)
               session.removeAttribute("mysession");
          session.setAttribute("mysession", data2);
          With session.removeAttibute() in our codes, some session data is not replicated
          to secondary server.
          We checked all session data in secondary server after shutting down the primary
          server.
          But if we comment out all session.removeAttribute() methods, failovers tested
          successfully.
          All our session data is serializable. Some are String and Some are Objects.
          Is this a known problems in WL6.1? Anyone has any idea?
          thanks,
          Hong

HttpSession not replicating

 I am trying to deploy our application in a clsutered environment. So far we have
 developed the product w/o thinking about clustering and now one of our client
 requires our product to be deployed in clustered environment.
 Our app has a ear file which has lot of jars, 3 wars.
 I configured my cluster with 3 servers ( 1 admin and 2 managed). Lets admin is
 called msAdmin, and 2 managed servers are called ms1 and ms2. I also created a
 web app outside the cluster httpProxy for HttpClusterServlet.
 Before testing our app, I deployed a simple webapp as part of the same ear file
 to test if the httpsession replication works or not and it seemed to work absolutely
 fine. I could see the httpsession replicated and at the time of fail over I could
 see another server handling the request.
 Then I tested our app to see if httpsession is getting replicated or not but i
 could not see it getting replicated. One thing I noticed is that the http session
 has some non-serializable objects in it but I expect only those non-seriazable
 object be not replicated. All the seriazable objects should have been replicated.
 Any ideas of why the httpsession is not getting replicated.
 Praveen


The actual problem once if weblogic throws an error saying Non-serializable
 exception then it will not try replicating any more new session.
 Here is the CR 102655 in which they have fixed the problem., but i have not
 tested so far.
 Aravind
 "Rajesh Mirchandani" <[email protected]> wrote in message
 news:[email protected]...
 > This is a known issue. Contact [email protected] for a patch.
 >
 > Praveen Peddi wrote:
 > > Hi Anand,
 > > Thanks for the response. It was the problem in our code. We were putting
 a non-serializable
 > > object in a hashmap and putting that hashmap in the httpSession. But I
 think there
 > > is a bug in weblogic 7.0. For some reason it did not replicate any
 objects (even
 > > the objects that are perfectly serializable.
 > >
 > >
 > > anand raman <[email protected]> wrote:
 > >
 > >>hi praveen
 > >>
 > >>I am not sure why http session replication isnt happening. Can you
 briefly
 > >>explain how you
 > >>1) performed the test with the simple web app
 > >>2) show us your web.xml
 > >>
 > >>cheers
 > >>anand
 > >>
 > >>In article <[email protected]>, Praveen Peddi wrote:
 > >>
 > >>>I am trying to deploy our application in a clsutered environment. So
 > >>
 > >>far we have
 > >>
 > >>>developed the product w/o thinking about clustering and now one of
 > >>
 > >>our client
 > >>
 > >>>requires our product to be deployed in clustered environment.
 > >>>Our app has a ear file which has lot of jars, 3 wars.
 > >>>I configured my cluster with 3 servers ( 1 admin and 2 managed). Lets
 > >>
 > >>admin is
 > >>
 > >>>called msAdmin, and 2 managed servers are called ms1 and ms2. I also
 > >>
 > >>created a
 > >>
 > >>>web app outside the cluster httpProxy for HttpClusterServlet.
 > >>>Before testing our app, I deployed a simple webapp as part of the same
 > >>
 > >>ear file
 > >>
 > >>>to test if the httpsession replication works or not and it seemed to
 > >>
 > >>work absolutely
 > >>
 > >>>fine. I could see the httpsession replicated and at the time of fail
 > >>
 > >>over I could
 > >>
 > >>>see another server handling the request.
 > >>>Then I tested our app to see if httpsession is getting replicated or
 > >>
 > >>not but i
 > >>
 > >>>could not see it getting replicated. One thing I noticed is that the
 > >>
 > >>http session
 > >>
 > >>>has some non-serializable objects in it but I expect only those
 non-seriazable
 > >>>object be not replicated. All the seriazable objects should have been
 > >>
 > >>replicated.
 > >>
 > >>>Any ideas of why the httpsession is not getting replicated.
 > >>>
 > >>>Praveen
 > >>
 > >
 >
 >
 > --
 > Rajesh Mirchandani
 > Developer Relations Engineer
 > BEA Support
 >

How do I change the context-root of a web app with a deployment plan?

I've been trying to figure this out for several hours.
I'm deploying a .ear file which sets the context root for the single web application it deploys in its application.xml deployment descriptor:
<application>
<display-name>MyApp</display-name>
<module>
<web>
<web-uri>MyAppViewControler.war</web-uri>
<context-root>MyApp</context-root>
</web>
</module>
</application>
I want to change the context-root from /MyApp to something else when deploying the ear file. It seemed to me that using a deployment plan was the way to do this. But when I use this plan:
<deployment-plan>
<application-name>MyApp<application-name>
<variable-definition>
<variable>
<name>NEWCONTEXTROOT</name>
<value>foobar</value>
</variable>
</variable-definition>
<module-override>
<module-name>MyApp</module-name>
<module-type>ear</module-type>
<module-descriptor external="false">
<root-element>application</root-element>
<uri>META-INF/application.xml</uri>
<variable-assignment>
<name>NEWCONTEXTROOT</name>
<xpath>/application/module/web/context-root</xpath>
</variable-assignment>
</module-descriptor>
</module-override>
</deployment-plan>
I get an error:
weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
/bea/user_projects/domains/devod1/nullplan.xml:0: problem: cvc-complex-type.2.4a: Expected element 'web-uri@http://java.sun.com/xml/ns/javaee' instead of 'context-root@http://java.sun.com/xml/ns/javaee' here in element web@http://java.sun.com/xml/ns/javaee:<nullplan.xml>
I looked at http://e-docs.bea.com/wls/docs103/pdf/deployment.pdf which says:
"You cannot use a deployment plan to change the context-root in an application.xml
file. However, if an application is deployed as a library, you can either change the
context-root through an weblogic-application.xml file or use the deployment plan
to change the context-root in an weblogic-application.xml file."
I don't understand what this means. I'm not deploying my application as a library.
Does anyone know how to change the context-root for an application?
Any help would be greatly appreciated!

Hi James,
I am quite new to Welogic if i am wrong please correct me.I have re-deployed my application (.war) with this Plan.xml
<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://www.bea.com/ns/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/deployment-plan http://www.bea.com/ns/weblogic/deployment-plan/1.0/deployment-plan.xsd" global-variables="false">
<application-name>BrowserR08.003</application-name>
*<variable-definition>*
* <variable>*
* <name>CONTEXTROOT</name>*
* <value>BrowserWeb/servlet/BrowserServlet</value>*
* </variable>*
* </variable-definition>*
<module-override>
<module-name>BrowserWeb.war</module-name>
<module-type>war</module-type>
<module-descriptor external="true">
<root-element>weblogic-web-app</root-element>
<uri>WEB-INF/weblogic.xml</uri>
<hash-code>1231953167814</hash-code>
*<variable-assignment>*
* <name>CONTEXTROOT</name>*
* <xpath>/weblogic-web-app/context-root</xpath>*
* <operation>add</operation>*
* </variable-assignment>*
</module-descriptor>
<module-descriptor external="false">
<root-element>web-app</root-element>
<uri>WEB-INF/web.xml</uri>
</module-descriptor>
<module-descriptor external="true">
<root-element>wldf-resource</root-element>
<uri>META-INF/weblogic-diagnostics.xml</uri>
</module-descriptor>
</module-override>
<config-root>/export/home1/tecapp/BrowserR08.003/plan</config-root>
</deployment-plan>
I do not know wether i will require the other module descriptor definition in this Plzn.xml. Now when I go to following link.
Deployments --> MyApp --> Testing
It gives me following url as a test page:
http://localhost:7001/BrowserWeb/servlet/BrowserServlet
as soon as i click on to the above link it redirects me to following.
http://localhost:7001/BrowserWeb/servlet/BrowserServlet/servlet/BrowserServlet
Same if i remove these context-root part my normal Testing menu shows me following link as my webapp access path
http://localhost:7001/BrowserWeb <-- My war file name is BrowserWeb.war so it is default name of my deployed application if i am not wrong
and as soon as i click on above link it redirects me to the following one.
http://localhost:7001/BrowserWeb/servlet/BrowserServlet
It means application server know that my full web access page is with '*servlet/BrowserServlet*' because its adding it in both the cases.
What I want is a constant URL whcih does not change?
Hope this helps :)

SSRS in SharePoint Mode: Reporting Services scale-out deployment is not supported in this edition of Reporting Services [not true]

Hello,
We are experiencing some issues with SharePoint 2013 which is driving me insane.
We have a deployment with two SQL Servers (HA groups) and four SharePoint servers: 2 Application servers, and 2 Web FrontEnd servers.
We installed SSRS for SharePoint in both application servers. The disc I have used is the MSDN image of SQL Enterprise 2012 w/ SP2.
ISO name: en_sql_server_2012_enterprise_edition_with_service_pack_2_x64_dvd_4685849.iso
MD5: 003e14c55fa648ad15f8be1e2439bd06
The installation completes without any problems. We can start the SSRS SharePoint Service in the first application server without any issues. However when we try to start the second one, we get the following error:
Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the sql reporting services service in the farm. The SQL Server Reporting Services cannot be started on
this server unless it is stopped on all other servers in the farm.
Now I am at a loss here. As I mentioned, we have used an image of SQL Server Enterprise. This is the same image we used on other environment, which worked as expected (we got no such error).
I have included the text related to the correlation error from the SP logs below.
Has anyone ever seen this issue before? Very, very strange!
Regards,
P.
01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (POST:http://spap-01:5555/_admin/Server.aspx?ServerId=7f7d5eec-3791-44cf-a992-673eaea90f48) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=, ClaimsCount=0 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Logging Correlation Data xmnv Medium Site=/ 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (PostAuthenticateRequestHandler). Execution Time=9.742 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.28 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General 6t8h High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.23, Original Level: Verbose] {0} 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.28 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Web Controls 88wu High [Forced due to logging gap, Original Level: Verbose] SPGridView.OnRowCreated() - Row.RowType={0}, .RowState={1}, .RowIndex={2}, .DataItemIndex={3} 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.37 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General af4yd High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.28, Original Level: Verbose] TenantAppEtag record requested but there is no sitesubscription or tenantId for site {0} so we will use the WebApp Id for the cache. 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.37 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Asp Runtime aj1kp High [Forced due to logging gap, Original Level: Verbose] SPRequestModule.PreSendRequestHeaders 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.43 OWSTIMER.EXE (0x1F10) 0x0B40 SharePoint Foundation Health abire Medium Failed to Sql Query data XEvent collector on sql-01. The error is Object reference not set to an instance of an object.
01/29/2015 14:13:26.51 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 7034 Critical An attempt to start/stop instance of service Microsoft SQL Server Reporting Services Shared Service on server SPAP-01 did not succeed. Re-run the action via UI or command line on the specified server. Additional information is below. Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database ahjqp High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.40, Original Level: Verbose] SQL connection time: 0.0821 for Data Source=sql-01;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][2][SharePoint_Config] 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 88b9 High [Forced due to logging gap, Original Level: Verbose] Determining if the current user is a SharePoint Farm Administrator 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 8xqz Medium Updating SPPersistedObject ReportingWebServiceInstance. Version: 1118292 Ensure: False, HashCode: 52212853, Id: 5a4058b9-2ecd-421e-b9ae-818bbc57c8c6, Stack: at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error) at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb) at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.79 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database ahjqp High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.57, Original Level: Verbose] SQL connection time: 0.0965 for Data Source=sql-01;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][2][SharePoint_Config] 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.79 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database 8acb High [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.86 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 88ch High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.84, Original Level: Verbose] {0} 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.86 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General 8nca Medium Application error when access /_admin/Server.aspx, Error=Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.87 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Runtime tkau Unexpected System.InvalidOperationException: Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.89 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General ajlz0 High Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.InvalidOperationException: Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.92 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Micro Trace uls4 Medium Micro Trace Tags: 0 nasq,2 agb9s,9 b4ly,309 8xqz,331 8nca,15 tkau,8 ajlz0 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.92 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (POST:http://spap-01:5555/_admin/Server.aspx?ServerId=7f7d5eec-3791-44cf-a992-673eaea90f48)). Execution Time=712.2145 6f83e49c-cc03-d049-90f4-81439b542cf8

Hi Wynn,
I appreciate your attempt to address my concerns, but even your reply seems to ignore the fact that I have not only provided the name of the ISO, but the MD5 checksum of the ISO as well. Also this is the first time I am being asked to double-check the version
of SSRS. The first reply I got to my query simply disregarded the version mismatch.
As per your request, I have checked under the folder you have specified (C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\WebServices\LogFiles), but unfortunately there are no files under this folder in neither of my two application
servers.
We only have logfiles under C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS
Is there a way I can turn those logs on?
In the meantime, we run the SQL Server Discovery tool and I have attached the summary for you to see that it finds the Enterprise Edition of SQL Server:
Final result: Passed
Exit code (Decimal): 0
Start time: 2015-01-29 15:17:44
End time: 2015-01-29 15:17:56
Requested action: RunDiscovery
Machine Properties:
Machine name: SP-AP-02
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered Configured
SQL Server 2012 Management Tools - Basic 1033 Enterprise Edition 11.2.5058.0 No Yes
SQL Server 2012 Reporting Services - SharePoint 11.2.5058.0 No Yes
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation edition:
User Input Settings:
ACTION: RunDiscovery
CONFIGURATIONFILE:
ENU: true
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
QUIET: false
QUIETSIMPLE: false
UIMODE: Normal
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150129_151743\ConfigurationFile.ini
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: The rule result report file is not available.
The \Setup Bootstrap\Log folder also has several log files that indicates the version of SQL Server that has been installed. For instance here is an entry of the Detail.txt file:
(01) 2015-01-28 19:10:27 Slp: -- SkuPublicConfigObject : CreateSKUCookie succeeded, new checksum is 195 bytes.
(01) 2015-01-28 19:10:27 Slp: -- SkuPublicConfigObject : Updated skuCheckSumInfo -> daysLeft=0 sqlEdition='ENTERPRISE' (0x6B9471A8) fileTimeInstalled=0 timeBombValue=0 editionType='Enterprise Edition' edition='Enterprise Edition' writeEditionStrings='True' checkSum=195bytes
(01) 2015-01-28 19:10:27 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
I hope this help while we don't have any logfiles in the folder you asked me to look into. Please advise me as in how to proceed if logfiles must be generated.
Regards,
P.

Deployment Plan not replicating across clusters

Similar Messages

Maybe you are looking for