2008 R2 Session Broker allowing multiple sessions

I have the options set to restrict a user to a single session in RDS however I am having problems with two things. i initially thought it was because I had a startup script setup in GPO however I removed that and the issue is still happening.
1. If a user disconnects they do not always get reconnected to their disconnected session.
2. A user with an active session can go on a different device and connect and get a new session on a different session host.
Configuration:
3 Session hosts
RDS Session Broker (Is the session broker for 2 different RDS farms)
GPO to restrict users to a single session in place for session hosts

Hi,
Can you able to connect each RDSH server with its unique IP address?
You can check under RDSH configuration on RDSH server that IP redirection for selecting dedicated IP address for individual server is used. For a connection to redirect for RDSH server it must be the unique IP address for destination RDSH server.
For this issue there is hotfix (KB 977541) available for Server 2008 (you can refer for workaround part), might it works for your case. Refer below article for more information on
IP redirection.
About IP Address and Token Redirection
http://technet.microsoft.com/en-us/library/cc732852.aspx
Hope it helps!
Thanks.

Similar Messages

How to allow multiple-session changes to fields in a PDF using Reader 7

Good morning
We used Adobe LiveCycle Designer ES 8.2 to create a seminar registration form that people can download from our website.
The idea is they fill it in and email it back as an attachment.
There are some browser plug-in issues - e.g. in Internet Explorer I can fill in the form and save it to my PC, and the PDF created on my PC contains the data I entered. If I do the same thing in Firefox, the saved file is empty (the data isn't saved).
But the real problem is, if I open the PDF in Reader 9 (at work) I can fill in the form, save, re-open and make changes.
With Reader 7.0 (at home), if I enter data and save and re-open, I get a message as follows:
"The document contained certain rights to enable special features in Adobe
Reader. The document has been changed since it was created and these rights
are no longer valid. Please contact the author of the original version of this
document."
...meaning, with Reader 7.0 I only get one chance to fill in the form.
Is there a way of creating the PDF that allow users with earlier versions of Reader to have more than one crack at it?
e.g. would saving the file for Reader version 7 solve the issue?
thanks in advance
PS: I didn't do the form, not sure how it's done, and I don't have Reader 7 where I am now.

CtDave wrote:
Reader enable the form then users of Adobe Reader will be able to fill in and save.
Be well...
Shouldn't one use Acrobat to enable the form?

How to kill particular Oracle Session from the multiple Session of User

Hi,
I am working on Web Application using ASP.NET , C# with Oracle. I am excuting queries from multiple connection of same user. I want to kill particular user session. I have tried to Kill session by using ALTER SYSTEM KILL SESSION 'sid,serial#' it is working fine but how can i identify which session is generated by particular connection so that i can kill that particular session.
Suppose there us user 'abc' there are multple instance of this user and all are active but same USERNAME. So Please tell me how can i identify that session through which i am executing the query.
Thanks,
Nitin

Some ideas for how to pick the right session:
-Look at the time the session was connected (logon_time)
-Look at the time the session last started it's most recent statement (last_call_et)
-Look at the sql that the session is running (join with sql_address and sql_hash_value over to v$sqltext_with_newlines or one of the other views that show you the sql they are running)
That usually gets me most of the way, if it's possible to distinguish them. ("Yeah I just started this query and I want you to kill it." is different than "I started five different queries at about the same time and I'm not sure which one I need killed.")

Hyperion Smart Cut Session Issue streaming multiple reports at a time using

This is a lengthly post with details, Please review with Patience:
We are trying to integrate Workspace based web Analysis reports within our intranet portal, thru portlets (made from individual workspace smartcut link), so that users can customize their page as needed, Once they login thru intranet, Cookie is set and passed to succeeding smart cut links via secured http headers. This part is fine, but mainly running into issue with streaming several multiple web-analysis reports at a time,+ we are using Iframe to display and stream multiple individual reports on to one page, but unfortunately all Iframes are sharing one session rather than creating individual session, mostly because of limitation of current web analysis system architecture and IE browser behavior with sessions .
Which Hyperion reporting tool does allow to stream multiple reports at a time? ideally we want to create Iframe of each workspace report so that users can customize and pick portlets as needed. To stream multiple reports at a time.
Problem Description: Hypeiron Web Analsysis, Smart cut reports incorrectly rendering images and intermixing dash boards on POV changes upon multiple reports being diplayed at one time thru Iframe's, issue seem to mostly relate to Hyperion using single session rather to multiple session when displaying several web reports at a time.
Steps Needed To Reproduce:
User logs into workspace.
user click on expolore and able to view the report without any issues.
When right on any of the report and select properties.
Select the SmartCut url and paste it in the Internet explorer.
The webanalysis report opens without any issues.
Similarly user copies the smartcut url for a different report and paste the link on a different tab or new window of same browser.
The report on the first tab gets over written of the report of the second tab of the browser.
The issue happens when two different reports and opened on a browser with multiple tabs. The reports get over written.
Oracle development answer:
In the described scenario opening new browser window does not spawn a separate independent browser session. A new browser window is supplied with URL pointing to the same domain, so all browser cookies including the "ORA_WA_SID" (WA session cookie) are shared between the windows. But multiple application instances cannot run in the same browser session simultaneously because of session sharing. This is not actually a defect, but rather a limitation of current system architecture and browser behavior. And there is no way to fix it programmatically on the product side.

Hi MeHyper,
Your current arrangement puts most of the session handling and persistence on the client. This forces you to accept whatever the client decides to persist and propogate between browser elements (in this case iframes).
My approach would be to:
Consider coding your portlets to manage the sessions. Manage using a somewhat stateless strategy so that each request to the server requires a login and connect, retrieve, and disconnect. Each Iframe should access a different portlet url (or provide a different query) based on its content.
This way, in theory, you can invalidate the sessions and related cookies and update the various report elements independently.
Is smartview out of the question here?
Regards,
Robb Salzmann

Session broker and custom conversion manager

I'm having some problem using session broker and a custom conversion manager. I just moved from using single session to using a session broker in the sessions.xml. I'm using a custom conversion manager as shown in this tech. tips URL
http://www.oracle.com/technology/products/ias/toplink/technical/tips/customconversion/index.html
Here's my conversion manager set up code -
public class JpmiConversionManagerSetup extends SessionEventAdapter
* During the pre-login event the new MyConversionManager must be installed
* @see oracle.toplink.sessions.SessionEventAdapter#preLogin
* @param event
public void preLogin(SessionEvent event) {
ConversionManager cm= new JpmiConversionManager();
ConversionManager.setDefaultManager(cm);
event.getSession().getLogin().getPlatform().setConversionManager(cm);
My session broker manages 2 sessions. In sessions.xml for one session I have the <event-listener-class> entry where I need some conversion, another session I don't have any such entry as I don't need any conversion.
Now when I try to run a named query using session broker the conversion part blows up, throws a ConversionException. Any idea? Do I need to configure the session broker instead of session in the preLogin or anything like that?

I think sessions editor is not available in 10.1.3dp4 yet. So I have to write the sessions.xml by hand. But the parser throwing me an error saying that <session-broker> is not allowed in sessions.xml.
SessionLoaderExceptions:
org.xml.sax.SAXParseException: <Line 41, Column 18>: XML-24534: (Error) Element 'session-broker' not expected.
     at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:415)
     at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:284)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:302)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:199)
     at oracle.xml.jaxp.JXDocumentBuilder.parse(JXDocumentBuilder.java:155)
     at oracle.xml.jaxp.JXDocumentBuilder.parse(JXDocumentBuilder.java:111)
     at oracle.toplink.platform.xml.xdk.XDKParser.parse(XDKParser.java:160)
     at oracle.toplink.platform.xml.xdk.XDKParser.parse(XDKParser.java:190)
     at oracle.toplink.tools.sessionconfiguration.XMLSessionConfigLoader.loadDocument(XMLSessionConfigLoader.java:191)
     at oracle.toplink.tools.sessionconfiguration.XMLSessionConfigLoader.loadDocument(XMLSessionConfigLoader.java:151)
     at oracle.toplink.tools.sessionconfiguration.XMLSessionConfigLoader.load(XMLSessionConfigLoader.java:88)
     at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(SessionManager.java:364)
     at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(SessionManager.java:331)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
Any idea how to or where to write sessions broker in sessions.xml for 10.1.3dp4???

How do I create a program with multiple sessions?

I need to allow multiple sessions with this program.
I realize that it involves threading of some sort, but I'm pretty new to this area and am not sure how I should go about this.
Here are the instructions:
"�     Write an application that will create an online dictionary a data file will be supplied that contains a list of words and their meanings. The hash table will contain a key (the word in question) and a value (byte offset of the word meaning stored in a random access file). You will also provide methods for entering, searching and deleting words online. The program must allow for multiple sessions."
I have most of this all done, and have a dictionaryBroker ready to write the add, delete and search methods.
But what about the mutliple sessions?
I'm thinking that my hashTable and RandomAccessFile classes are both going to have to be singleton.
What I want is for multiple people to be able to run the program at the same time, but if one person adds or deletes a record, I want it to update instantly for everyone.
But it also needs to run smoothly for everyone using it.
Thanks for any help, I just need a little push in the right direction here to help get me going.

Well here is the entire assignment:
     Write an interface for a hash table that satisfies the following criteria:
The hash table will contain a key (String) and a value (Object)
Allow for a specific load capacity, if the capacity is exceeded the table is rehashed. The rehash may be called independently
Must allow for maintaining the hash table (adding modifying etc) the key will not be changed
Must allow for retrieving information from the table
Must allow addition using a Map object or one key, value pair at a time
The addition using a Map and the rehash must be a two pass approach
�     Implement the interface.
�     Write a test routine to test all aspects of the interface. The test must calculate the efficiency of your hashing algorithm.
�     Write an application that will create an online dictionary a data file will be supplied that contains a list of words and their meanings. The hash table will contain a key (the word in question) and a value (byte offset of the word meaning stored in a random access file). You will also provide methods for entering, searching and deleting words online. The program must allow for multiple sessions.
Submission
Submit your eclipse project or executable jar file through WebCT. An efficiency of 70% or better must be attained for the assignment to be graded.
I'm in Canada, not the US.
It says online dictionary, but I don't think we actually have to do that. I'm pretty sure I can just use a simple GUI to allow them access to the dictionary.
So, I'm assuming that I just have to make sure that if multiple people are trying to access it at the same time it needs to update at the same time or something. The hashtable was the main part of the assignment so this part shouldn't be too large.

Windows 2008 R2 Doesn't Allow DPI (Font Size / Scaling) Changes on Remote Sessions

I am using latest version of RDP Client 6.1 from my local Windows 7 Enterprise system, as well as RDP Client 6.1 from a Windows 2008 R2 server.
When I connect to other Windows 2008 R2 servers, I am unable to increase the DPI settings. In Control Panel > Ease of Access > Optimize Visual Display > Change the size of text and icons, I get a screen which says “The display settings
can’t be changed from a remote session”.
This is unacceptable. I am able to change this setting on any Windows 2008 (pre-R2) server in multiple environments. When is MSFT going to fix this issue in R2?
I have seen other posts on this issue
such as this one -- one person suggests exporting the registry settings under
[HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics and then to set them on my R2 server.
Can I export those registry keys from a 2008 (non-R2) server where I have set the DPI to 125%, and then import them onto the R2 server?
Thank you.

This sort of works:
Run this .reg file and logoff/logon.
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics]
"BorderWidth"="-15"
"CaptionFont"=hex:f2,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,bc,02,00,00,\
00,00,00,01,00,00,00,00,54,00,72,00,65,00,62,00,75,00,63,00,68,00,65,00,74,\
00,20,00,4d,00,53,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"CaptionHeight"="-375"
"CaptionWidth"="-270"
"IconFont"=hex:f2,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,90,01,00,00,00,\
00,00,01,00,00,00,00,54,00,61,00,68,00,6f,00,6d,00,61,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"IconSpacing"="-1125"
"IconTitleWrap"="1"
"IconVerticalspacing"="-1125"
"MenuFont"=hex:f2,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,90,01,00,00,00,\
00,00,01,00,00,00,00,54,00,61,00,68,00,6f,00,6d,00,61,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"MenuHeight"="-285"
"MenuWidth"="-270"
"MessageFont"=hex:f2,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,90,01,00,00,\
00,00,00,01,00,00,00,00,54,00,61,00,68,00,6f,00,6d,00,61,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"ScrollHeight"="-255"
"ScrollWidth"="-255"
"Shell Icon BPP"="16"
"SmCaptionFont"=hex:f2,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,bc,02,00,\
00,00,00,00,01,00,00,00,00,54,00,61,00,68,00,6f,00,6d,00,61,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"SmCaptionHeight"="-255"
"SmCaptionWidth"="-255"
"StatusFont"=hex:f2,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,90,01,00,00,\
00,00,00,01,00,00,00,00,54,00,61,00,68,00,6f,00,6d,00,61,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"Shell Icon Size"="32"
"MinAnimate"="1"

Cannot connect to Session broker server, but can to other servers in Cluster

Hi Everyone,
Hopefully this is the right place to post. Have searched quite a bit through the forums (not all 19000+ pages though), and can't seem to find a similiar issue.
I have also searched the internet and tried all solutions others with a similiar problem have.
This is my problem:
We have two servers running Server 2008 R2, set up as Remote Desktop Servers in a cluster setup.
The session broker is located on the second server (This is an active server which has sessions load balanced to it). There is also a DNS round robin setup
Problem: When sessions are allowed to be load balanced on Server2, then the users cannot connect to the cluster. The round robin seems to still send some sessions to the first server, and these seem to connect fine.
I suspected the issue was with the WMI Respository, and so started. I found a lot of errors, but have been unable to fix them.
I downlaoded the WMIDiag from Microsoft, and here is the report:
48866 15:56:44 (0) ** WMIDiag v2.1 started on 15 April 2015 at 15:48.
48867 15:56:44 (0) **
48868 15:56:44 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
48869 15:56:44 (0) **
48870 15:56:44 (0) ** This script is not supported under any Microsoft standard support program or service.
48871 15:56:44 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
48872 15:56:44 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
48873 15:56:44 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
48874 15:56:44 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
48875 15:56:44 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
48876 15:56:44 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
48877 15:56:44 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
48878 15:56:44 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
48879 15:56:44 (0) ** of the possibility of such damages.
48880 15:56:44 (0) **
48881 15:56:44 (0) **
48882 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48883 15:56:44 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
48884 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48885 15:56:44 (0) **
48886 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48887 15:56:44 (0) ** Windows Server 2008 R2 - Service pack 1 - 64-bit (7601) - User 'MIBCO\CONN.LOMBARD' on computer 'SSCRDS02'.
48888 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48889 15:56:44 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
48890 15:56:44 (0) ** INFO: => 3 possible incorrect shutdown(s) detected on:
48891 15:56:44 (0) **          - Shutdown on 05 December 2014 22:55:28 (GMT-0).
48892 15:56:44 (0) **          - Shutdown on 12 December 2014 06:43:00 (GMT-0).
48893 15:56:44 (0) **          - Shutdown on 27 February 2015 05:19:26 (GMT-0).
48894 15:56:44 (0) **
48895 15:56:44 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #1).
48896 15:56:44 (0) ** Drive type: ......................................................................................................... SCSI (DELL PERC H700 SCSI Disk Device).
48897 15:56:44 (0) ** There are no missing WMI system files: .............................................................................. OK.
48898 15:56:44 (0) ** There are no missing WMI repository files: .......................................................................... OK.
48899 15:56:44 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
48900 15:56:44 (0) ** AFTER running WMIDiag:
48901 15:56:44 (0) ** The WMI repository has a size of: ................................................................................... 26 MB.
48902 15:56:44 (0) ** - Disk free space on 'C:': .......................................................................................... 297281 MB.
48903 15:56:44 (0) **   - INDEX.BTR,                     5513216 bytes,      2015/04/15 03:52:21 PM
48904 15:56:44 (0) **   - MAPPING1.MAP,                  76804 bytes,        2015/04/15 03:50:51 PM
48905 15:56:44 (0) **   - MAPPING2.MAP,                  76804 bytes,        2015/04/15 03:52:21 PM
48906 15:56:44 (0) **   - OBJECTS.DATA,                  22036480 bytes,     2015/04/15 03:52:21 PM
48907 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48908 15:56:44 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
48909 15:56:44 (0) ** Windows Firewall Profile: ........................................................................................... DOMAIN.
48910 15:56:44 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
48911 15:56:44 (0) ** => This will prevent any WMI remote connectivity to this computer except
48912 15:56:44 (0) **    if the following three inbound rules are ENABLED and non-BLOCKING:
48913 15:56:44 (0) **    - 'Windows Management Instrumentation (DCOM-In)'
48914 15:56:44 (0) **    - 'Windows Management Instrumentation (WMI-In)'
48915 15:56:44 (0) **    - 'Windows Management Instrumentation (ASync-In)'
48916 15:56:44 (0) **    Verify the reported status for each of these three inbound rules below.
48917 15:56:44 (0) **
48918 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' GROUP rule: ............................................. ENABLED.
48919 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-Out)' rule: ............................................... ENABLED.
48920 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ................................................ ENABLED.
48921 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ............................................... ENABLED.
48922 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: .............................................. ENABLED.
48923 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48924 15:56:44 (0) ** DCOM Status: ........................................................................................................ OK.
48925 15:56:44 (0) ** WMI registry setup: ................................................................................................. OK.
48926 15:56:44 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
48927 15:56:44 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
48928 15:56:44 (0) ** - SMS Agent Host (CCMEXEC, StartMode='Automatic')
48929 15:56:44 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
48930 15:56:44 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
48931 15:56:44 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
48932 15:56:44 (0) **          this can prevent the service/application to work as expected.
48933 15:56:44 (0) **
48934 15:56:44 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
48935 15:56:44 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
48936 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48937 15:56:44 (0) ** WMI service DCOM setup: ............................................................................................. OK.
48938 15:56:44 (0) ** WMI components DCOM registrations: .................................................................................. OK.
48939 15:56:44 (0) ** WMI ProgID registrations: ........................................................................................... OK.
48940 15:56:44 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
48941 15:56:44 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
48942 15:56:44 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
48943 15:56:44 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
48944 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48945 15:56:44 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
48946 15:56:44 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
48947 15:56:44 (0) **    i.e. You can start your scripts or WMIC commands from an elevated command
48948 15:56:44 (0) **         prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
48949 15:56:44 (0) **         selecting 'Run as Administrator'.
48950 15:56:44 (0) **    i.e. You can also execute the WMI scripts or WMIC commands as a task
48951 15:56:44 (0) **         in the Task Scheduler within the right security context.
48952 15:56:44 (0) **
48953 15:56:44 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
48954 15:56:44 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
48955 15:56:44 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
48956 15:56:44 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
48957 15:56:44 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
48958 15:56:44 (0) **
48959 15:56:44 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
48960 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\SYSTEM' DOES NOT match corresponding expected trustee rights (Actual->Default)
48961 15:56:44 (0) **        - ACTUAL ACE:
48962 15:56:44 (0) **          ACEType: &h0
48963 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
48964 15:56:44 (0) **          ACEFlags: &h4
48965 15:56:44 (0) **                    NO_PROPAGATE_INHERIT_ACE
48966 15:56:44 (0) **          ACEMask: &hB
48967 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
48968 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
48969 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
48970 15:56:44 (0) **        - EXPECTED ACE:
48971 15:56:44 (0) **          ACEType: &h0
48972 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
48973 15:56:44 (0) **          ACEFlags: &h0
48974 15:56:44 (0) **          ACEMask: &h1F
48975 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
48976 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
48977 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
48978 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
48979 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
48980 15:56:44 (0) **
48981 15:56:44 (0) ** => The actual ACE has the right(s) '&h14 DCOM_RIGHT_LAUNCH_REMOTE DCOM_RIGHT_ACTIVATE_REMOTE' removed!
48982 15:56:44 (0) **    This will cause some operations to fail!
48983 15:56:44 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
48984 15:56:44 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
48985 15:56:44 (0) **
48986 15:56:44 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
48987 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\INTERACTIVE' DOES NOT match corresponding expected trustee rights (Actual->Default)
48988 15:56:44 (0) **        - ACTUAL ACE:
48989 15:56:44 (0) **          ACEType: &h0
48990 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
48991 15:56:44 (0) **          ACEFlags: &h4
48992 15:56:44 (0) **                    NO_PROPAGATE_INHERIT_ACE
48993 15:56:44 (0) **          ACEMask: &hB
48994 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
48995 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
48996 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
48997 15:56:44 (0) **        - EXPECTED ACE:
48998 15:56:44 (0) **          ACEType: &h0
48999 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
49000 15:56:44 (0) **          ACEFlags: &h0
49001 15:56:44 (0) **          ACEMask: &h1F
49002 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
49003 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
49004 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
49005 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
49006 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
49007 15:56:44 (0) **
49008 15:56:44 (0) ** => The actual ACE has the right(s) '&h14 DCOM_RIGHT_LAUNCH_REMOTE DCOM_RIGHT_ACTIVATE_REMOTE' removed!
49009 15:56:44 (0) **    This will cause some operations to fail!
49010 15:56:44 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
49011 15:56:44 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
49012 15:56:44 (0) **
49013 15:56:44 (0) **
49014 15:56:44 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
49015 15:56:44 (0) ** DCOM security error(s) detected: .................................................................................... 2.
49016 15:56:44 (0) ** WMI security warning(s) detected: ................................................................................... 0.
49017 15:56:44 (0) ** WMI security error(s) detected: ..................................................................................... 0.
49018 15:56:44 (0) **
49019 15:56:44 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
49020 15:56:44 (0) ** Overall WMI security status: ........................................................................................ OK.
49021 15:56:44 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
49022 15:56:44 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 5.
49023 15:56:44 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
49024 15:56:44 (0) **   'select * from MSFT_SCMEventLogEvent'
49025 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
49026 15:56:44 (0) **   'SELECT * FROM __NamespaceCreationEvent'
49027 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
49028 15:56:44 (0) **   'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy_EmbeddedObject"'
49029 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
49030 15:56:44 (0) **   'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy_Config"'
49031 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
49032 15:56:44 (0) **   'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy"'
49033 15:56:44 (0) **
49034 15:56:44 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
49035 15:56:44 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 3 NAMESPACE(S)!
49036 15:56:44 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
49037 15:56:44 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
49038 15:56:44 (0) ** - ROOT/SERVICEMODEL.
49039 15:56:44 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
49040 15:56:44 (0) **    use an encrypted connection by specifying the PACKET PRIVACY authentication level.
49041 15:56:44 (0) **    (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
49042 15:56:44 (0) **    i.e. 'WMIC.EXE /NODE:"SSCRDS02" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
49043 15:56:44 (0) **
49044 15:56:44 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
49045 15:56:44 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
49046 15:56:44 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 34 ERROR(S)!
49047 15:56:44 (0) ** - Root/CIMV2, MSFT_NetInvalidDriverDependency, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49048 15:56:44 (0) **   MOF Registration: ''
49049 15:56:44 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49050 15:56:44 (0) **   MOF Registration: ''
49051 15:56:44 (0) ** - Root/CIMV2, Win32_OsBaseline, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49052 15:56:44 (0) **   MOF Registration: ''
49053 15:56:44 (0) ** - Root/CIMV2, Win32_DriverVXD, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49054 15:56:44 (0) **   MOF Registration: ''
49055 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49056 15:56:44 (0) **   MOF Registration: ''
49057 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49058 15:56:44 (0) **   MOF Registration: ''
49059 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49060 15:56:44 (0) **   MOF Registration: ''
49061 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49062 15:56:44 (0) **   MOF Registration: ''
49063 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49064 15:56:44 (0) **   MOF Registration: ''
49065 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49066 15:56:44 (0) **   MOF Registration: ''
49067 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49068 15:56:44 (0) **   MOF Registration: ''
49069 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49070 15:56:44 (0) **   MOF Registration: ''
49071 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49072 15:56:44 (0) **   MOF Registration: ''
49073 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49074 15:56:44 (0) **   MOF Registration: ''
49075 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_NETDataProviderforOracle_NETDataProviderforOracle, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49076 15:56:44 (0) **   MOF Registration: ''
49077 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_NETDataProviderforOracle_NETDataProviderforOracle, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49078 15:56:44 (0) **   MOF Registration: ''
49079 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49080 15:56:44 (0) **   MOF Registration: ''
49081 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49082 15:56:44 (0) **   MOF Registration: ''
49083 15:56:44 (0) ** - Root/WMI, ReserveDisjoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49084 15:56:44 (0) **   MOF Registration: ''
49085 15:56:44 (0) ** - Root/WMI, ReserveLateCount, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49086 15:56:44 (0) **   MOF Registration: ''
49087 15:56:44 (0) ** - Root/WMI, ReserveJoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49088 15:56:44 (0) **   MOF Registration: ''
49089 15:56:44 (0) ** - Root/WMI, ReserveDelete, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49090 15:56:44 (0) **   MOF Registration: ''
49091 15:56:44 (0) ** - Root/WMI, ReserveBandwidth, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49092 15:56:44 (0) **   MOF Registration: ''
49093 15:56:44 (0) ** - Root/WMI, ReserveCreate, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49094 15:56:44 (0) **   MOF Registration: ''
49095 15:56:44 (0) ** - Root/WMI, SystemConfig_PhyDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49096 15:56:44 (0) **   MOF Registration: ''
49097 15:56:44 (0) ** - Root/WMI, SystemConfig_Video, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49098 15:56:44 (0) **   MOF Registration: ''
49099 15:56:44 (0) ** - Root/WMI, SystemConfig_IDEChannel, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49100 15:56:44 (0) **   MOF Registration: ''
49101 15:56:44 (0) ** - Root/WMI, SystemConfig_NIC, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49102 15:56:44 (0) **   MOF Registration: ''
49103 15:56:44 (0) ** - Root/WMI, SystemConfig_Network, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49104 15:56:44 (0) **   MOF Registration: ''
49105 15:56:44 (0) ** - Root/WMI, SystemConfig_CPU, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49106 15:56:44 (0) **   MOF Registration: ''
49107 15:56:44 (0) ** - Root/WMI, SystemConfig_LogDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49108 15:56:44 (0) **   MOF Registration: ''
49109 15:56:44 (0) ** - Root/WMI, SystemConfig_Power, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49110 15:56:44 (0) **   MOF Registration: ''
49111 15:56:44 (0) ** - root/ccm/LocationServices, ClientInfo, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49112 15:56:44 (0) **   MOF Registration: ''
49113 15:56:44 (0) ** - root/ccm/LocationServices, ClientInfo, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49114 15:56:44 (0) **   MOF Registration: ''
49115 15:56:44 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
49116 15:56:44 (0) **    a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
49117 15:56:44 (0) **    You can refresh the WMI class provider buffer with the following command:
49118 15:56:44 (0) **
49119 15:56:44 (0) **    i.e. 'WINMGMT.EXE /SYNCPERF'
49120 15:56:44 (0) **
49121 15:56:44 (0) ** WMI MOF representations: ............................................................................................ OK.
49122 15:56:44 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
49123 15:56:44 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
49124 15:56:44 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
49125 15:56:44 (2) !! WARNING: WMI GET VALUE operation errors reported: ................................................................... 5 WARNING(S)!
49126 15:56:44 (0) ** - Root, Instance: __EventConsumerProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
49127 15:56:44 (0) ** - Root, Instance: __EventProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
49128 15:56:44 (0) ** - Root, Instance: __EventSinkCacheControl=@, Property: ClearAfter='00000000000015.000000:000' (Expected default='00000000000230.000000:000').
49129 15:56:44 (0) ** - Root, Instance: __ObjectProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
49130 15:56:44 (0) ** - Root, Instance: __PropertyProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
49131 15:56:44 (0) **
49132 15:56:44 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
49133 15:56:44 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
49134 15:56:44 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
49135 15:56:44 (0) ** WMI static instances retrieved: ..................................................................................... 6304.
49136 15:56:44 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
49137 15:56:44 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 3.
49138 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49139 15:56:44 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
49140 15:56:44 (0) **   DCOM: ............................................................................................................. 0.
49141 15:56:44 (0) **   WINMGMT: .......................................................................................................... 0.
49142 15:56:44 (0) **   WMIADAPTER: ....................................................................................................... 0.
49143 15:56:44 (0) **
49144 15:56:44 (0) ** # of additional Event Log events AFTER WMIDiag execution:
49145 15:56:44 (0) **   DCOM: ............................................................................................................. 0.
49146 15:56:44 (0) **   WINMGMT: .......................................................................................................... 0.
49147 15:56:44 (0) **   WMIADAPTER: ....................................................................................................... 0.
49148 15:56:44 (0) **
49149 15:56:44 (0) ** 34 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
49150 15:56:44 (0) ** => This error is typically a WMI error. This WMI error is due to:
49151 15:56:44 (0) **    - a missing WMI class definition or object.
49152 15:56:44 (0) **      (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
49153 15:56:44 (0) **      You can correct the missing class definitions by:
49154 15:56:44 (0) **      - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
49155 15:56:44 (0) **      Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
49156 15:56:44 (0) **            (This list can be built on a similar and working WMI Windows installation)
49157 15:56:44 (0) **            The following command line must be used:
49158 15:56:44 (0) **            i.e. 'WMIDiag CorrelateClassAndProvider'
49159 15:56:44 (0) **      Note: When a WMI performance class is missing, you can manually resynchronize performance counters
49160 15:56:44 (0) **            with WMI by starting the ADAP process.
49161 15:56:44 (0) **    - a WMI repository corruption.
49162 15:56:44 (0) **      In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
49163 15:56:44 (0) **      to validate the WMI repository operations.
49164 15:56:44 (0) **    Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
49165 15:56:44 (0) **          executing the WriteInRepository command. To write temporary data from the Root namespace, use:
49166 15:56:44 (0) **          i.e. 'WMIDiag WriteInRepository=Root'
49167 15:56:44 (0) **    - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
49168 15:56:44 (0) **      the WMI repository must be reconstructed.
49169 15:56:44 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
49170 15:56:44 (0) **          otherwise some applications may fail after the reconstruction.
49171 15:56:44 (0) **          This can be achieved with the following command:
49172 15:56:44 (0) **          i.e. 'WMIDiag ShowMOFErrors'
49173 15:56:44 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
49174 15:56:44 (0) **          ALL fixes previously mentioned.
49175 15:56:44 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
49176 15:56:44 (0) **
49177 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49178 15:56:44 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!
49179 15:56:44 (0) ** INFO: Unexpected registry key value:
49180 15:56:44 (0) **   - Current: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 0
49181 15:56:44 (0) **   - Expected: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 1
49182 15:56:44 (0) **     From the command line, the registry configuration can be corrected with the following command:
49183 15:56:44 (0) **     i.e. 'REG.EXE Add "HKLM\SOFTWARE\Microsoft\WBEM\CIMOM" /v "Logging" /t "REG_SZ" /d "1" /f'
49184 15:56:44 (0) **
49185 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49186 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49187 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49188 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49189 15:56:44 (0) **
49190 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49191 15:56:44 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
49192 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49193 15:56:44 (0) **
49194 15:56:44 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\CONN.LOMBARD\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_2K8R2.SRV.SP1.64_SSCRDS02_2015.04.15_15.48.25.LOG' for details.
49195 15:56:44 (0) **
49196 15:56:44 (0) ** WMIDiag v2.1 ended on 15 April 2015 at 15:56 (W:110 E:41 S:1).
This seems to be the biggest problem:
48960 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\SYSTEM' DOES NOT match corresponding expected trustee rights (Actual->Default)
This seems to be the second biggest error (and there are a few of them):
0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
I have tried:
winmgmt /resyncperf
winmgmt /verifyrepository
winmgmt /salvagerepository
winmgmt /resetrepository
I have also tried registering the mof files with
MOFCOMP <FileName.mof>
Lastly, I even disabled the WMI service, renamed the Repository folder, and had it rebuild the repository.
I got stuck on re registering the 'NT AUTHORITY\SYSTEM' (I think it is in the Components section in Administrative tools), as I could not find clear instructions on exactly how to go about it.
Chkdsk found no errors
Sfc /scannow found no errors
winmgmt /verifyrepository finds no errors.
I'm hoping someone here might be able to steer me in the right direction to get this resolved, as I do not want to rebuild a server that hosts a connection broker and has over 100 user profiles on it, as well as some very annoying and finniky LOB apps installed,
which will have to manually be reinstalled for each profile.

Hi,
Here is a blog regarding how to fix WMI issue might be useful to you:
Fixing WMI issues Using Batch Script
http://social.technet.microsoft.com/wiki/contents/articles/6887.fixing-wmi-issues-using-batch-script.aspx
In addition, you mentioned Remote Desktop Servers are in a cluster setup, would you tell us how did you create the cluster?
As far as I know, with RD Connection Broker, we don’t need to create a cluster but just add multiple RD session hosts into one collection, then RD connection Broker would redirect sessions automatically.
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Terminalserver Session Broker not reconnecting to existing session

Hi!
Following scenario:
Terminalserver-Farm
2x RemoteDesktopServer (Windows Server 2008R2)
1x TS Session Broker (Windows Server 2008)
A user connects to TS-Farm -> occasionally it happens that he is redirected to (for example) TS2, even if he has an active session on TS1. There is no error message displayed on the client. Subsequently he has 2 sessions, allthough the setting on the Session
Broker is set to "allow only 1 session per user". Interestingly this happens to 2 users only - both are the only ones working on Windows 8 clients (other users are on Win7).
Any ideas how to track down the problem? I don't see the correlation with Windows 8 clients at all.
Best Regards,
Stefan

Hi!
Affected are ThinClients with RDP 5.2 - it's still working on one of the 2008R2, not on the 2nd.
I used network monitor to see traffic from an XP-Thin Client to both Terminalservers. I can see (but not understand): "T125:Disconnect Provider Ultimatum, rn-user-requested" in line 27 at the non-working Terminalserver
Client -> TS 2008R2 with working RDP:
3 11:57:33 08.01.2014 5.3233299 10.5.4.173 10.5.0.106 TCP TCP:Flags=......S., SrcPort=1633, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=2968904019, Ack=0, Win=65535 ( ) = 65535 {TCP:2, IPv4:1}
4 11:57:33 08.01.2014 5.3238252 10.5.0.106 10.5.4.173 TCP TCP:Flags=...A..S., SrcPort=MS WBT Server(3389), DstPort=1633, PayloadLen=0, Seq=2063055863, Ack=2968904020, Win=8192 ( Scale factor not supported ) = 8192 {TCP:2, IPv4:1}
5 11:57:33 08.01.2014 5.3242143 10.5.4.173 10.5.0.106 TCP TCP:Flags=...A...., SrcPort=1633, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=2968904020, Ack=2063055864, Win=65535 (scale factor 0x0) = 65535 {TCP:2, IPv4:1}
6 11:57:33 08.01.2014 5.3255958 10.5.4.173 10.5.0.106 X224 X224:Connection Request {ISOTS:3, TCP:2, IPv4:1}
7 11:57:33 08.01.2014 5.3273352 10.5.0.106 10.5.4.173 TCP TCP:Flags=...A...., SrcPort=MS WBT Server(3389), DstPort=1633, PayloadLen=0, Seq=2063055864, Ack=2968904031, Win=64240 (scale factor 0x0) = 64240 {TCP:2, IPv4:1}
8 11:57:33 08.01.2014 5.3274171 10.5.0.106 10.5.4.173 X224 X224:Connection Confirm {ISOTS:3, TCP:2, IPv4:1}
9 11:57:33 08.01.2014 5.3293456 10.5.4.173 10.5.0.106 T125 T125:MCSConnect Initial {T125:4, ISOTS:3, TCP:2, IPv4:1}
10 11:57:33 08.01.2014 5.3298119 10.5.0.106 10.5.4.173 T125 T125:MCSConnect Response {T125:4, ISOTS:3, TCP:2, IPv4:1}
11 11:57:33 08.01.2014 5.3315607 10.5.4.173 10.5.0.106 TCP TCP:Flags=...A...., SrcPort=1633, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=2968904443, Ack=2063057917, Win=65535 (scale factor 0x0) = 65535 {TCP:2, IPv4:1}
12 11:57:33 08.01.2014 5.3322727 10.5.4.173 10.5.0.106 T125 T125:Erect Domain Request, SubHeight = 0, SubInterval = 0 {T125:4, ISOTS:3, TCP:2, IPv4:1}
13 11:57:33 08.01.2014 5.3324046 10.5.4.173 10.5.0.106 T125 T125:Attach User Request {T125:4, ISOTS:3, TCP:2, IPv4:1}
14 11:57:33 08.01.2014 5.3324212 10.5.0.106 10.5.4.173 TCP TCP:Flags=...A...., SrcPort=MS WBT Server(3389), DstPort=1633, PayloadLen=0, Seq=2063057917, Ack=2968904463, Win=63808 (scale factor 0x0) = 63808 {TCP:2, IPv4:1}
15 11:57:33 08.01.2014 5.3324293 10.5.0.106 10.5.4.173 T125 T125:Attach User Confirm, Result = rt-successful, Indicator = 0x3ef {T125:4, ISOTS:3, TCP:2, IPv4:1}
16 11:57:33 08.01.2014 5.3330774 10.5.4.173 10.5.0.106 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ef {T125:4, ISOTS:3, TCP:2, IPv4:1}
17 11:57:33 08.01.2014 5.3331055 10.5.0.106 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1007, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
18 11:57:33 08.01.2014 5.3340565 10.5.4.173 10.5.0.106 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3eb {T125:4, ISOTS:3, TCP:2, IPv4:1}
19 11:57:33 08.01.2014 5.3340826 10.5.0.106 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1003, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
20 11:57:33 08.01.2014 5.3345604 10.5.4.173 10.5.0.106 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ec {T125:4, ISOTS:3, TCP:2, IPv4:1}
21 11:57:33 08.01.2014 5.3345856 10.5.0.106 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1004, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
22 11:57:33 08.01.2014 5.3356991 10.5.4.173 10.5.0.106 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ed {T125:4, ISOTS:3, TCP:2, IPv4:1}
23 11:57:33 08.01.2014 5.3357256 10.5.0.106 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1005, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
24 11:57:33 08.01.2014 5.3362559 10.5.4.173 10.5.0.106 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ee {T125:4, ISOTS:3, TCP:2, IPv4:1}
25 11:57:33 08.01.2014 5.3362827 10.5.0.106 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1006, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
26 11:57:33 08.01.2014 5.3450865 10.5.4.173 10.5.0.106 RDPBCGR RDPBCGR: {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
27 11:57:33 08.01.2014 5.3456510 10.5.4.173 10.5.0.106 RDPBCGR RDPBCGR:TsClientSecurityExchangePDU Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
28 11:57:33 08.01.2014 5.3456706 10.5.0.106 10.5.4.173 TCP TCP:Flags=...A...., SrcPort=MS WBT Server(3389), DstPort=1633, PayloadLen=0, Seq=2063058003, Ack=2968904946, Win=63325 (scale factor 0x0) = 63325 {TCP:2, IPv4:1}
29 11:57:33 08.01.2014 5.3460200 10.5.0.106 10.5.4.173 RDPELE RDPELE:Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
30 11:57:33 08.01.2014 5.3900913 10.5.0.106 10.5.4.173 RDPBCGR RDPBCGR:SlowPathPacket Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
31 11:57:33 08.01.2014 5.3909177 10.5.4.173 10.5.0.106 TCP TCP:Flags=...A...., SrcPort=1633, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=2968904946, Ack=2063058498, Win=64954 (scale factor 0x0) = 64954 {TCP:2, IPv4:1}
32 11:57:33 08.01.2014 5.4047118 10.5.4.173 10.5.0.106 RDPBCGR RDPBCGR:SlowPathPacket Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
33 11:57:33 08.01.2014 5.4047805 10.5.0.106 10.5.4.173 RDPBCGR RDPBCGR:SlowPathPacket Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
34 11:57:33 08.01.2014 5.4047946 10.5.0.106 10.5.4.173 RDPBCGR RDPBCGR:SlowPathPacket Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
Client -> TS 2008R2 with non-working RDP:
3 11:21:03 08.01.2014 4.7063150 10.5.4.173 10.5.0.144 TCP TCP:Flags=......S., SrcPort=1526, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=459527613, Ack=0, Win=65535 ( ) = 65535 {TCP:2, IPv4:1}
4 11:21:03 08.01.2014 4.7067575 10.5.0.144 10.5.4.173 TCP TCP:Flags=...A..S., SrcPort=MS WBT Server(3389), DstPort=1526, PayloadLen=0, Seq=2589137033, Ack=459527614, Win=8192 ( Scale factor not supported ) = 8192 {TCP:2, IPv4:1}
5 11:21:03 08.01.2014 4.7071555 10.5.4.173 10.5.0.144 TCP TCP:Flags=...A...., SrcPort=1526, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=459527614, Ack=2589137034, Win=65535 (scale factor 0x0) = 65535 {TCP:2, IPv4:1}
6 11:21:03 08.01.2014 4.7101168 10.5.4.173 10.5.0.144 X224 X224:Connection Request {ISOTS:3, TCP:2, IPv4:1}
7 11:21:03 08.01.2014 4.7101591 10.5.0.144 10.5.4.173 X224 X224:Connection Confirm {ISOTS:3, TCP:2, IPv4:1}
8 11:21:03 08.01.2014 4.7110721 10.5.4.173 10.5.0.144 T125 T125:MCSConnect Initial {T125:4, ISOTS:3, TCP:2, IPv4:1}
9 11:21:03 08.01.2014 4.7114117 10.5.0.144 10.5.4.173 T125 T125:MCSConnect Response {T125:4, ISOTS:3, TCP:2, IPv4:1}
10 11:21:03 08.01.2014 4.7130978 10.5.4.173 10.5.0.144 TCP TCP:Flags=...A...., SrcPort=1526, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=459528060, Ack=2589139965, Win=65535 (scale factor 0x0) = 65535 {TCP:2, IPv4:1}
11 11:21:03 08.01.2014 4.7131136 10.5.0.144 10.5.4.173 TCP TCP:[Continuation to #9]Flags=...AP..., SrcPort=MS WBT Server(3389), DstPort=1526, PayloadLen=2286, Seq=2589139965 - 2589142251, Ack=459528060, Win=63828 (scale factor 0x0) = 63828 {TCP:2, IPv4:1}
12 11:21:03 08.01.2014 4.7137283 10.5.4.173 10.5.0.144 TCP TCP:Flags=...A...., SrcPort=1526, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=459528060, Ack=2589141425, Win=65535 (scale factor 0x0) = 65535 {TCP:2, IPv4:1}
13 11:21:03 08.01.2014 4.7142557 10.5.4.173 10.5.0.144 T125 T125:Erect Domain Request, SubHeight = 0, SubInterval = 0 {T125:4, ISOTS:3, TCP:2, IPv4:1}
14 11:21:03 08.01.2014 4.7143931 10.5.4.173 10.5.0.144 T125 T125:Attach User Request {T125:4, ISOTS:3, TCP:2, IPv4:1}
15 11:21:03 08.01.2014 4.7144101 10.5.0.144 10.5.4.173 TCP TCP:Flags=...A...., SrcPort=MS WBT Server(3389), DstPort=1526, PayloadLen=0, Seq=2589142251, Ack=459528080, Win=63808 (scale factor 0x0) = 63808 {TCP:2, IPv4:1}
16 11:21:03 08.01.2014 4.7144276 10.5.0.144 10.5.4.173 T125 T125:Attach User Confirm, Result = rt-successful, Indicator = 0x3ef {T125:4, ISOTS:3, TCP:2, IPv4:1}
17 11:21:03 08.01.2014 4.7152352 10.5.4.173 10.5.0.144 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ef {T125:4, ISOTS:3, TCP:2, IPv4:1}
18 11:21:03 08.01.2014 4.7152672 10.5.0.144 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1007, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
19 11:21:03 08.01.2014 4.7162762 10.5.4.173 10.5.0.144 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3eb {T125:4, ISOTS:3, TCP:2, IPv4:1}
20 11:21:03 08.01.2014 4.7163087 10.5.0.144 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1003, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
21 11:21:03 08.01.2014 4.7172413 10.5.4.173 10.5.0.144 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ec {T125:4, ISOTS:3, TCP:2, IPv4:1}
22 11:21:03 08.01.2014 4.7172699 10.5.0.144 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1004, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
23 11:21:03 08.01.2014 4.7183019 10.5.4.173 10.5.0.144 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ed {T125:4, ISOTS:3, TCP:2, IPv4:1}
24 11:21:03 08.01.2014 4.7183348 10.5.0.144 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1005, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
25 11:21:03 08.01.2014 4.7193451 10.5.4.173 10.5.0.144 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ee {T125:4, ISOTS:3, TCP:2, IPv4:1}
26 11:21:03 08.01.2014 4.7193736 10.5.0.144 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1006, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
27 11:21:03 08.01.2014 4.7234596 10.5.4.173 10.5.0.144 T125 T125:Disconnect Provider Ultimatum, rn-user-requested {T125:4, ISOTS:3, TCP:2, IPv4:1}
28 11:21:03 08.01.2014 4.7237173 10.5.4.173 10.5.0.144 TCP TCP:Flags=...A...F, SrcPort=1526, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=459528149, Ack=2589142337, Win=64623 (scale factor 0x0) = 64623 {TCP:2, IPv4:1}
29 11:21:03 08.01.2014 4.7237356 10.5.0.144 10.5.4.173 TCP TCP:Flags=...A...., SrcPort=MS WBT Server(3389), DstPort=1526, PayloadLen=0, Seq=2589142337, Ack=459528150, Win=63739 (scale factor 0x0) = 63739 {TCP:2, IPv4:1}
30 11:21:03 08.01.2014 4.7237527 10.5.0.144 10.5.4.173 TCP TCP:Flags=...A.R.., SrcPort=MS WBT Server(3389), DstPort=1526, PayloadLen=0, Seq=2589142337, Ack=459528150, Win=0 (scale factor 0x0) = 0 {TCP:2, IPv4:1}

RD Session Broker will not redirect to the Collection Servers.

Host server running 2012 Hyper V with 3 VM's
One RD Broker configured
Two Session Hosts in a collection - not in drain mode.
All are 2012 R2
I can use RDweb and the RD broker will divert me to one of the host servers. I can use the RDP icon and works.
I would rather use the new remote desktop app in windows 8, and use Desktop Sessions (Terminal Services), not VDI or RD web.
I'm hoping that the Broker is in drain mode but the server will not redirect. I am not sure what's going on, I haven't placed the domain users in the remote desktop users on the Broker because I cannot place the Broker into drain mode like I had in the pass
with 2008 R2
Doesn't make sense and I have done a heap of searching.
My objective is to use the remote desktop app and log into one of 2 servers with a desktop session.
I believe this is the error I need to get past.
I have placed Broker into the Windows Authorization Access Group
Remote Desktop Connection Broker Client failed to redirect the user domain\user. Error:NULL

Hi,
As I understand it, if we put the TS server in drain mode, it prevents new users from logging onto the server, while allowing currently logged on users to reconnect to their existing sessions. I guess if you want to know how to put the server in drain mode
so it won’t accept any new connections. Do this by selecting its collection in RDMS. In the Host Servers section, right-click the server and choose “Do not allow new connections.” For more information, you may refer to this article,
http://technet.microsoft.com/en-us/magazine/dn235779.aspx
Moreover, if there is something misunderstood, please send me the related srceenshots to be clear. Hope it is useful to you.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Accessing the same stateful session bean from multiple clients in a clustered environment

I am trying to access the same stateful session bean from multiple
          clients. I also want this bean to have failover support so we want to
          deploy it in a cluster. The following description is how we have tried
          to solve this problem, but it does not seem to be working. Any
          insight would be greatly appreciated!
          I have set up a cluster of three servers. I deployed a stateful
          session bean with in memory replication across the cluster. A client
          obtains a reference to an instance of one of these beans to handle a
          request. Subsequent requests will have to use the same bean and could
          come from various clients. So after using the bean the first client
          stores the handle to the bean (actually the replica aware stub) to be
          used by other clients to be able to obtain the bean. When another
          client retrieves the handle gets the replica aware stub and makes a
          call to the bean the request seems to unpredictably go to any of the
          three servers rather than the primary server hosting that bean. If the
          call goes to the primary server everything seems to work fine the
          session data is available and it gets backed up on the secondary
          server. If it happens to go to the secondary server a bean that has
          the correct session data services the request but gives the error
          <Failed to update the secondary copy of a stateful session bean from
          home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
          to the primary server will not reflect changes made on the secondary
          and vice versa. If the request happens to go to the third server that
          is not hosting an instance of that bean then the client receives an
          error that the bean was not available. From my understanding I thought
          the replica aware stub would know which server is the primary host for
          that bean and send the request there.
          Thanks in advance,
          Justin


          If 'allow-concurrent-call' does exactly what you need, then you don't have a problem,
          do you?
          Except of course if you switch ejb containers. Oh well.
          Mike
          "FBenvadi" <[email protected]> wrote:
          >I've got the same problem.
          >I understand from you that concurrent access to a stateful session bean
          >is
          >not allowed but there is a
          >token is weblogic-ejb-jar.xml that is called 'allow-concurrent-call'
          >that
          >does exactly what I need.
          >What you mean 'you'll get a surprise when you go to production' ?
          >I need to understand becouse I can still change the design.
          >Thanks Francesco
          >[email protected]
          >
          >"Mike Reiche" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> Get the fix immediately from BEA and test it. It would be a shame to
          >wait
          >until
          >> December only to get a fix - that doesn't work.
          >>
          >> As for stateful session bean use - just remember that concurrent access
          >to
          >a stateful
          >> session bean is not allowed. Things will work fine until you go to
          >production
          >> and encounter some real load - then you will get a surprise.
          >>
          >> Mike
          >>
          >> [email protected] (Justin Meyer) wrote:
          >> >I just heard back from WebLogic Tech Support and they have confirmed
          >> >that this is a bug. Here is their reply:
          >> >
          >> >There is some problem in failover of stateful session beans when its
          >> >run from a java client.However, it is fixed now.
          >> >
          >> >The fix will be in SP2 which will be out by december.
          >> >
          >> >
          >> >Mike,
          >> >Thanks for your reply. I do infact believe we are correctly using
          >a
          >> >stateful session bean however it may have been misleading from my
          >> >description of the problem. We are not accessing the bean
          >> >concurrently from 2 different clients. The second client will only
          >> >come into play if the first client fails. In this case we want to
          >be
          >> >able to reacquire the handle to our stateful session bean and call
          >it
          >> >from the secondary client.
          >> >
          >> >
          >> >Justin
          >> >
          >> >"Mike Reiche" <[email protected]> wrote in message
          >news:<[email protected]>...
          >> >> You should be using an entity bean, not a stateful session bean
          >for
          >> >this application.
          >> >>
          >> >> A stateful session bean is intended to be keep state (stateful)
          >for
          >> >the duration
          >> >> of a client's session (session).
          >> >>
          >> >> It is not meant to be shared by different clients - in fact, if
          >you
          >> >attempt to
          >> >> access the same stateful session bean concurrently - it will throw
          >> >an exception.
          >> >>
          >> >> We did your little trick (storing/retrieving handle) with a stateful
          >> >session bean
          >> >> on WLS 5.1 - and it did work properly - not as you describe. Our
          >sfsb's
          >> >were not
          >> >> replicated as yours are.
          >> >>
          >> >> Mike
          >> >>
          >> >> [email protected] (Justin Meyer) wrote:
          >> >> >I am trying to access the same stateful session bean from multiple
          >> >> >clients. I also want this bean to have failover support so we want
          >> >to
          >> >> >deploy it in a cluster. The following description is how we have
          >tried
          >> >> >to solve this problem, but it does not seem to be working. Any
          >> >> >insight would be greatly appreciated!
          >> >> >
          >> >> >I have set up a cluster of three servers. I deployed a stateful
          >> >> >session bean with in memory replication across the cluster. A client
          >> >> >obtains a reference to an instance of one of these beans to handle
          >> >a
          >> >> >request. Subsequent requests will have to use the same bean and
          >could
          >> >> >come from various clients. So after using the bean the first client
          >> >> >stores the handle to the bean (actually the replica aware stub)
          >to
          >> >be
          >> >> >used by other clients to be able to obtain the bean. When another
          >> >> >client retrieves the handle gets the replica aware stub and makes
          >> >a
          >> >> >call to the bean the request seems to unpredictably go to any of
          >the
          >> >> >three servers rather than the primary server hosting that bean.
          >If
          >> >the
          >> >> >call goes to the primary server everything seems to work fine the
          >> >> >session data is available and it gets backed up on the secondary
          >> >> >server. If it happens to go to the secondary server a bean that
          >has
          >> >> >the correct session data services the request but gives the error
          >> >> ><Failed to update the secondary copy of a stateful session bean
          >from
          >> >> >home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
          >> >> >to the primary server will not reflect changes made on the secondary
          >> >> >and vice versa. If the request happens to go to the third server
          >that
          >> >> >is not hosting an instance of that bean then the client receives
          >an
          >> >> >error that the bean was not available. From my understanding I
          >thought
          >> >> >the replica aware stub would know which server is the primary host
          >> >for
          >> >> >that bean and send the request there.
          >> >> >
          >> >> >Thanks in advance,
          >> >> >Justin
          >>
          >
          >

How to avoid multiple session for the same username

I need suggestions on implementing single user login , like My system has a user with a username jdavid and my application should not allow two different sessions for the same username jdavid , can one session peep into all other session
to see if the any has a usernaem jdavid, I am basically looking for some pattern if any available for restricting multiple session for the same username . like jaas or any other security api provides this ?

Store a Map<User, HttpSession> in application scope and let your application intercept on that. On login, just check if the User is already there, then get the associated HttpSession, invalidate it and replace it by the current HttpSession, else just store the current User-HttpSession pair in the map. On logout obviously remove the User-HttpSession pair from the map.

Multiple sessions in a single database connection.

I have copied the following text from Forms Developer2000
"At runtime, Form Builder automatically establishes and manages a single connection to ORACLE. By default, one user session is created for this connection. However, the multiple-sessioning feature of ORACLE allows a single client to establish multiple sessions within a single connection. ORACLE transaction-management and read-consistency features all are implemented at the session level, so creating multiple sessions allows a single user to have multiple, independent transactions."
If ORACLE allows a single client to establish multiple sessions within a single connection, I want to leverage on this feature in my application which uses BC4J.
Can anybody tell me if
1. its possible achieve this in Java(BC4J).
2. If Yes, How?
regards,
vikrant

Thank you for your valuable suggestion.
I believe createing multiple root Application
Modules, will create as many number of connections to
database, hence multiple transactions.
But What I wanted was multiple sessions in a single
connection, who's behavior will be similar to two
different connections.Could you tell me the advantage you're looking for in multiple sessions in one connection vs. multiple connections (where connections may be pooled)?
Thanks.
Sung

Setup for Discoverer to have multiple sessions opening in different browser

What is the setup for Discoverer or Windows 6 browser to have multiple discoverer sessions opening in different browser windows at the same time in Discoverer 10g Plus?
We have implemented Discoverer 10g Plus just to be used as an extract tool. We have some workbooks retrieving 200,000 or more rows from an Oracle database. It is taking 30 to 45 minutes to download. Some users are able to open multiple sessions in different browsers to download more then one worksheet at the time, but we have other users who get an error message that they can only open one session at the time. What is the setup to allow users to open more than one Discoverer session?

Additional research in Metalink found the following:
Hdr: 7261918 10.2 USER_JAV 10.1.2.54.25 PRODID-964 PORTID-46
Abstract: ALLOW ABILITY TO LAUNCH TWO DISCOPLUS SESSIONS FROM SAME BROWSER CONNECTION PAGE
*** 07/17/08 07:31 am REQUEST TEXT ***
Please refer to bug 6656139. Need to get Discoverer Plus certified to
support launching two plus sessions from same browser connections page when
using SUN JRE 1.5/1.6 or higher.
As per bug 6656139 it appears to be JVM 1.5.x limitation, because same
actions work fine when using SUN JRE 1.4.2_xx.
*** 07/17/08 07:31 am BUSINESS NEED ***
Impossible to run reports against two different databases simultaniously
using same Discoverer instace, or just several reports at the same time,
which would save much time instead of running reports one by one.
*** 07/19/09 11:57 pm *** (CHG: Sta->97)
*** 07/19/09 11:57 pm RESPONSE ***
ALSO SEE THIS FROM SUPPORT
Error 'Unable To Connect Discoverer Server: Null' When Opening A Second Plus Session From The Same Browser [ID 790187.1]
Cause
Bug 6656139, JVM 1.5 : RUNNING TWO PLUS SESSIONS ERRORS WITH UNABLE TO CONNECT: NULL
The Java Console reports the following error:
Error: java.lang.StackOverflowError
java.lang.StackOverflowError
at java.awt.DefaultFocusTraversalPolicy.accept(Unknown Source)
at java.awt.ContainerOrderFocusTraversalPolicy.getFirstComponent(Unknown Source)
at java.awt.ContainerOrderFocusTraversalPolicy.getFirstComponent(Unknown Source)
at javax.swing.DefaultFocusManager.getFirstComponent(Unknown Source)
Per Bug 6656139 this problem is a limitation/bug with current Sun JRE 1.5
and higher and needs to be addressed by Sun.
Solution
Currently launching two Discoverer Plus sessions from the same browser connection page is not supported/certified.
Enhancement Request :
Bug 7261918, ALLOW ABILITY TO LAUNCH TWO DISCOPLUS SESSIONS FROM SAME BROWSER CONNECTION PAGE
has been logged for this issue but is still waiting on a Sun Java fix.
Use the following workaround:
Use JRE 1.4.2_xx until the ER is implemented and the SUN JRE bug is fixed.

How to handle multiple session in ADF using jdevloper11g

Hello All
i want to use the form in Multiple sessions.
i have one sign up form. user enter only 4 to 5 fields & he may not fill the the manditory field & he left.but data base dont give the error to him. but next day he will come at the next day to complet his sign up i.e. when he commit the all detail that time all validation will hapen.
for that i use one table without constrain to store the temarory detail.& use other table (with constrains) for final submition.
1) i creat the view n entity for temparory table
2) & also i create views n entity for Final table
n i create one methos in viewRowImple file in that file i overrid create method from using this i set the value from tempary to final table...
but when user left the manditory field then it allow to submit the data in temparory field but when i copy that data to final table(with constrain) n user submit the data then validation happn i.e. "this fild is mandatory".when i click this error message it goes to first screen.
IS Thiis Possible.. in ADF

Generally this can be done.
I see a problem with your use case, which has nothing to do with jdev or java:
How do you identify the user when he comes back to finish the form?
For this you can't use information like session cookie or IP address because they change.
So you have to save some information about the user which lets you identify him when he comes back. All other requirements can be implemented by ADF.
Timo

2008 R2 Session Broker allowing multiple sessions

Similar Messages

Maybe you are looking for