Closing the PR collectively

Hi all , I have created some PRs through Sales Order ( Third Party Process). I want to close these PRs collectively .
I have checked to close it by checking the tick Closed but this check mark is grayed out . Then How can I close the PRs

OK but pls explain properly . Is there any way for collective deletion

Similar Messages

MissingResourceException when I iterator a collection after closing the PM

I retrieve a collection, call pm.retrieveAll on it, and then close the PM.
When I try to iterator over the collection, I get a
MissingResourceException. I can't figure out why I'm getting the exception,
if I do a retrieveAll it should retrieve all the fields of all the objects
in the collection. It's as if there is a rule "Thou shall not iterator over
a collection after closing the PM". Is this true?
java.util.MissingResourceException: Can't find resource for bundle
java.util.PropertyResourceBundle, key resultlist-closed
at java.util.ResourceBundle.getObject(ResourceBundle.java:314)
at java.util.ResourceBundle.getString(ResourceBundle.java:274)
at serp.util.Localizer.get(Localizer.java:270)
at serp.util.Localizer.get(Localizer.java:121)
at
com.solarmetric.kodo.impl.jdbc.runtime.LazyResultList.checkClosed(LazyResult
List.java:349)
at
com.solarmetric.kodo.impl.jdbc.runtime.LazyResultList.listIterator(LazyResul
tList.java:403)
at
com.solarmetric.kodo.impl.jdbc.runtime.LazyResultList.iterator(LazyResultLis
t.java:397)
at
com.verideon.siteguard.services.SchedulerService.getMonitorsToRun(SchedulerS
ervice.java:103)
at
com.verideon.siteguard.services.SchedulerService.schedule(SchedulerService.j
ava:59)
at
com.verideon.siteguard.web.util.TimerServlet$scheduleTask.run(TimerServlet.j
ava:84)
at java.util.TimerThread.mainLoop(Timer.java:432)
at java.util.TimerThread.run(Timer.java:382)
Here is my code:
private Collection getMonitorsToRun() {
Collection c = new LinkedList();
PersistenceManager pm = null;
try {
pm = JDOFactory.getPersistenceManager();
Extent extent = pm.getExtent(Monitor.class, true);
String filter = "nextDate <= now";
Query q = pm.newQuery(extent, filter);
q.declareParameters("java.util.Date now");
q.setOrdering("nextDate ascending");
Hashtable p = new Hashtable();
p.put("now", new Date());
c = (Collection) q.executeWithMap(p);
pm.retrieveAll(c);
} catch (JDOException e) {
log.warn("Received JDO Exception while retrieving Monitors " + e);
} finally {
pm.close();
log.debug("Retrieved " + c.size() + " Monitors ready to be ran.");
Iterator i = c.iterator();
while (i.hasNext()) {
Monitor m = (Monitor) i.next();
log.debug("m id = " + m.getId());
return c;

It appears to be a query in which case, yes, a Query result Collection cannot be iterated over.
The simple way to bypass this is to transfer the results to a non-closing Collection.
Collection results = (Collection) q.execute ();
results = new LinkedList (results);
pm.retrieveAll (results);
pm.close ();
On Thu, 27 Feb 2003 14:49:17 +0100, Michael Mattox wrote:
I retrieve a collection, call pm.retrieveAll on it, and then close the PM.
When I try to iterator over the collection, I get a
MissingResourceException. I can't figure out why I'm getting the exception,
if I do a retrieveAll it should retrieve all the fields of all the objects
in the collection. It's as if there is a rule "Thou shall not iterator over
a collection after closing the PM". Is this true?
java.util.MissingResourceException: Can't find resource for bundle
java.util.PropertyResourceBundle, key resultlist-closed
at java.util.ResourceBundle.getObject(ResourceBundle.java:314)
at java.util.ResourceBundle.getString(ResourceBundle.java:274)
at serp.util.Localizer.get(Localizer.java:270)
at serp.util.Localizer.get(Localizer.java:121)
at
com.solarmetric.kodo.impl.jdbc.runtime.LazyResultList.checkClosed(LazyResult
List.java:349)
at
com.solarmetric.kodo.impl.jdbc.runtime.LazyResultList.listIterator(LazyResul
tList.java:403)
at
com.solarmetric.kodo.impl.jdbc.runtime.LazyResultList.iterator(LazyResultLis
t.java:397)
at
com.verideon.siteguard.services.SchedulerService.getMonitorsToRun(SchedulerS
ervice.java:103)
at
com.verideon.siteguard.services.SchedulerService.schedule(SchedulerService.j
ava:59)
at
com.verideon.siteguard.web.util.TimerServlet$scheduleTask.run(TimerServlet.j
ava:84)
at java.util.TimerThread.mainLoop(Timer.java:432)
at java.util.TimerThread.run(Timer.java:382)
Here is my code:
private Collection getMonitorsToRun() {
Collection c = new LinkedList();
PersistenceManager pm = null;
try {
pm = JDOFactory.getPersistenceManager();
Extent extent = pm.getExtent(Monitor.class, true);
String filter = "nextDate <= now";
Query q = pm.newQuery(extent, filter);
q.declareParameters("java.util.Date now");
q.setOrdering("nextDate ascending");
Hashtable p = new Hashtable();
p.put("now", new Date());
c = (Collection) q.executeWithMap(p);
pm.retrieveAll(c);
} catch (JDOException e) {
log.warn("Received JDO Exception while retrieving Monitors " + e);
} finally {
pm.close();
log.debug("Retrieved " + c.size() + " Monitors ready to be ran.");
Iterator i = c.iterator();
while (i.hasNext()) {
Monitor m = (Monitor) i.next();
log.debug("m id = " + m.getId());
return c;
Stephen Kim
[email protected]
SolarMetric, Inc.
http://www.solarmetric.com

Open cursors are NOT closed only by closing the ResultSet or Statement

I've realised that the open cursors are only closed by closing the connection.
In my example code I have for-loop with a vector of table-names. For every table-name I start a query to retrieve metainformation (row-size, column-names). Although I close the ResultSet (which automatically closes the PreparedStatement/Statement) I reached after the 150th loop a max-cursor-exception (ora-01000) ?!
It seems that there is only the workaround to close and re-open the connection at the end of the for-loop. Which is performance-side pretty bad :-(.
Is there really no other solution?
Besides: does anyone know WHY the statement.close() also closes the ResultSet?? I think this is a bad design (hence to tight dependency between both classes). What if the garbage collector closes the statement (and hence to the JDOC the statement.close()-method also closes the ResultSet)? For example if a method uses a local Statement and returns a ResultSet (and the Statement-garbage is collected), then the ResultSet would cause an exception?!
Thanks for the help in advance
Tai

I've realised that the open cursors are only closed by
closing the connection.Or by closing the Statement!
In my example code I have for-loop with a vector of
table-names. For every table-name I start a query to
retrieve metainformation (row-size, column-names).
Although I close the ResultSet (which automatically
closes the PreparedStatement/Statement) I reached
after the 150th loop a max-cursor-exception
(ora-01000) ?!Closing the ResutSet does not automatically close the PreparedStatement/Statement.
>
It seems that there is only the workaround to close
and re-open the connection at the end of the for-loop.
Which is performance-side pretty bad :-(.
Is there really no other solution?
Just explicitly close the PreparedStatement/Statement!
Besides: does anyone know WHY the statement.close()
also closes the ResultSet?? You need to think of a resultset as a live connection to the database.
Consider SELECT * FROM ABIGTABLE, it would be inefficient to populate the Resultset with all of the rows (could even eat up all memory) so the first n rows are returned ( n = Statement.getFetchSize() ) and the next n rows are returned as needed.
I think this is a bad
design (hence to tight dependency between both
classes). What if the garbage collector closes the
statement (and hence to the JDOC the
statement.close()-method also closes the ResultSet)?
For example if a method uses a local Statement and
returns a ResultSet (and the Statement-garbage is
collected), then the ResultSet would cause an
exception?!You should use a statment and resultset, read all your data into a collection or a CachedRowSet (http://www.javaworld.com/javaworld/jw-02-2001/jw-0202-cachedrow.html) then close the statment as soon as possible. Never return a resultset form your data tier: that is tight coupling between the tiers of your application!

Closing the Capture window crashes Premiere

Hi,
I'm attempting to capture video from a Sony DHR-FX1. The capture window doesn't show the video as it plays, but it appears to record it; when I stop and save the clip, the saved video appears in the Library window with a visible thumbnail of the video. As soon as I close the capture window, Premiere suddenly shuts down.
The settings in Premiere:
HDV 1080i30 (60)
29.97
1440x1080 (1.33 anamorphic)
16x9
48kHz 16 bit
The computer is a MacPro Tower with OSX Snow Leopard and I'm running version CS5.5.
Thanks much,
--Chaz

My version of OSX is 10.6.2
I purchased the Master Collection just this week so this is my first time using CS5.5 (and on a Mac no less). I downloaded the latest updates for Premiere [5.5.2] and there was a small improvement. Which now means the program doesn't crash immediately after closing the capture window, though it does eventually. I'm wondering if the crash when closing the capture may have been a coinidence before anyway.
There was a small delay before my latest crash which gave me enough time to save a short 5-sec test snippet. The footage was still in the file when I restarted so we're headed in the right direction. I'm attempting to record the entire tape at once to see if I can manage to save that with the same results.
Are there Codecs associated with this product or for the Mac that you're aware of?

Lightroom mobile sync "hangs" - I am trying to sync several small LR collections from my desktop computer. The first collection syncs, and then Lightroom syncing seems to hang. It shows "Syncing 150 photos" in top left, but never progresses even after c

I am using Lightroom 5.5 on OS X. I have created several small collections with about 180 images and I am trying to sync them via Lightroom mobile for later iPad access. The first collection syncs properly, and then Lightroom syncing seems to hang. The label in the upper right shows "Syncing 150 photos" but does not count down. Opening and closing LR does not restart the process.

PROBLEM STILL EXISTS...
I spoke to soon! I tried adding a couple of more collections to sync. Lightroom shows "Syncing 814" photos on upper left, but never apparently syncs any. If I exit Lightroom it notifies me there are 814 images to sync. When I reopen it seems to pick up and stall where it left off. These new collections are not posting - this is the same problem as before.
I am pretty sure there is a serious bug in Lightroom here. I encourage support to contact me.

Anyone know how to get the Nik Collection of plugins to work with PSCC?

As above..

Info from Nik:
From Nik:
On a Windows:
1. Make sure all versions of Photoshop are closed.
2. Run the Nik Collection installer from the file you received via email and downloaded. If you no longer have this file, you may email customer support ([email protected]) to have the file sent to you again.
3. During the installation process when you get to the Host Application window, you will notice a plus sign to add an install location. Click that button and navigate to C:\Program Files\Adobe\Photoshop CC\Plug-Ins\.
4. Complete the installation, then open Photoshop CC to ensure that the plug-ins have successfully been installed.
On a Macintosh:
1. Make sure all versions of Photoshop are closed.
2. Run the Nik Collection installer from the file you received via email and downloaded. If you no longer have this file, you may email customer support ([email protected]) to have the file sent to you again.
3. During the installation process when you get to the Host Application window, you will notice a plus sign to add an install location. Click that button and navigate to Mac HD|Applications|Adobe Photoshop CC|Plug-Ins and paste the Google folder into this location.
4. Complete the installation, then open Photoshop CC to ensure that the plug-ins have successfully been installed.

How do I selectivly close the only not responding window (without closing the other 3 responding windows)

Presently, I have 4 windows opened, each with a bunch of tabs.
Since I restarted firefox this morning, one out these 4 windows, keeps on not displaying.
How do I selectivly close this only window (without closing the 3 others windows)

Here is what the manpage shows:
[ps(1)|http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/p s.1.html]
state The state is given by a sequence of letters, for example, ``RWNA''. The first letter indicates the run
state of the process:
I Marks a process that is idle (sleeping for longer than about 20 seconds).
R Marks a runnable process.
S Marks a process that is sleeping for less than about 20 seconds.
T Marks a stopped process.
U Marks a process in uninterruptible wait.
Z Marks a dead process (a ``zombie'').
Additional characters after these, if any, indicate additional state information:
+ The process is in the foreground process group of its control terminal.
< The process has raised CPU scheduling priority.
<div class="jive-quote"> The process has specified a soft limit on memory requirements and is currently exceeding that
limit; such a process is (necessarily) not swapped.
A the process has asked for random page replacement (VA_ANOM, from vadvise(2), for example,
lisp(1) in a garbage collect).
E The process is trying to exit.
L The process has pages locked in core (for example, for raw I/O).
N The process has reduced CPU scheduling priority (see setpriority(2)).
S The process has asked for FIFO page replacement (VA_SEQL, from vadvise(2), for example, a large
image processing program using virtual memory to sequentially address voluminous data).
s The process is a session leader.
V The process is suspended during a vfork.
W The process is swapped out.
X The process is being traced or debugged.

MBP (13-inch, early 2011) goes into hibernation instead of safe sleep upon closing the lid (only when using battery power)

MBP details
13-inch MacBook Pro, early 2011 (model identifier: MacBookPro8,1)
Running Yosemite, OS X 10.10.1 (however, problem started while using Mavericks)
2.5 GHz Intel Core i5
4 GB memory
Symptoms
* the MBP goes into hibernation instead of sleep upon closing the lid on battery power (i.e., when AC adapter is NOT connected)
-- problem does not occur when AC adapter is connected
* putting the computer to sleep by other means does not induce the problem; these other means include:
-- [i] option+command+Power,
-- [ii] Apple Icon --> Sleep,
-- [iii] in Terminal: pmset sleepnow
* the battery is NOT getting drained at all; if I close the lid on 87%, the battery is still at about 87% when I get the MBP back up and running
To be as clear as possible:
(1) MBP is on and in use (power source: battery); battery is at X%
(2) the lid is then closed
(3) the battery indicator light glows bright for about 10 seconds, then shuts off, and with it so does the MBP (all fans and sounds cease)
(4) opening the lid and pressing any key on the keyboard does nothing (the computer is not sleeping)
(5) to turn the MBP back on, I must hit the power button once; this brings up and the gray screen and loading bar indicative of returning from hibernation
(6) log in; battery is still at X%
Attempted Solutions / Fixes
There are Apple Discussions addressing similar MBP issues, many of which at least have work-arounds, if not full-blown solutions. However, I have tried many of the proposed work-arounds and solutions; nothing has solved my problem. Such attempted solutions include:
* made sure EFI/SMC firmware was up to date
* updated all software
* logged in as a different user
* booted in Safe Mode
* reset the PRAM
* repaired disk permissions using Disk Utility
* repaired additional disk permissions in recovery mode (a la this chron.com advice)
* ran the Apple Hardware Test multiple times (short test while plugged in, short test on battery, extended test while plugged in, extended test on battery)
* booted from an external known-good OS on USB drive
* reseated the RAM
* used MemTest to test the RAM's health (it was good)
* tested my battery's health with the app Battery Health (it is healthy!)
* booted my computer with one stick of the MBP's original RAM at a time (figured "why not?")
* booted my computer using other sticks of RAM
* checked my power management settings using PMSET in the terminal (e.g., pmset -g); tried various hibernation modes (e.g., sudo pmset -a hibernationmode X, where X=0,1,3, etc)
* searched/grepped through my power management logs and Console messages to look for googleable items (e.g., pmset -g log | grep WORD, where WORD=failure, sleep, etc); still have not found help online
* brought the MBP to a Mac Genius
-- he ran some further tests, but found nothing;
-- he re-installed my OS as a hopeful-hail-mary-just-maybe-last-ditch effort; the problem persisted!
-- we both agreed that we had ruled out a software cause
-- he offered me to leave my MBP to get fixed for a flat fee of $300.00 (which after a couple weeks of trying to figure this out is starting to sound more and more reasonable)
Given that it is likely not a software issue, what hardware might it be? By booting from an OS on an external drive, I think I've ruled out a bad hard drive or hard drive cable. Also, given that inducing sleep in any way other than closing the MBP's lid does not cause the problem, it seems there might be a wire (or something) in the hinge section of the MBP that gets moved when the lid is closed possibly causing some kind of short circuit...or something.
If someone with more experience interpreting Console messages, for example, can help, I'd be happy to provide some logs, or any additional information.
Thank you for your time and consideration.

Ok, this is a crazy-simple, quasi-embarrassing fix, but I'll post it anyway just in case anyone is having a similar problem (for example, this guy: Changes to pmset being ignored).
Some time around late last August / early September (2014) this issue began happening for me (specifically, issue = closing lid while on battery power induces hibernation / shut down instead of sleep --- independent of hibernation mode). Maybe it was when I upgraded to Yosemite (not sure what the exact date of that was). As detailed in my original post, I frantically tried everything I could think of... At that time, however, I had quite a few presentations and posters to create and present at meetings and conferences, so I held off fixing it for a couple of months and returned to it this past week, where I tried a few more things listed above, but again to no avail...
This morning, I simply tried fudging around with all my power management settings again (via pmset in Terminal). The simplicity of the fix surprised me. But now that I understand it, I know it is likely the same fix for other threads I've read, such as the one above:
(TLDR in bold)
(1) Take note of your power management settings (Terminal: pmset -g custom)
(2) Is the "standby" flag set to 0? If so, set it to 1. Wa-la! Done.
This fix is crazy and embarrassing b/c I was so close to it for so long. I tried changing my hibernation modes multiple times (sudo pmset -a hibernatemode X, where X=0,1,3,25,etc). I read about manipulating other PMSET settings that helped other people with newer MBPs, like "autopoweroff" and "autopoweroffdelay" --- settings that I do not have on the MBP early 2011 (check your settings: pmset -g cap). And most amazingly of all, I even messed with the "standbydelay" setting, trying to make it so long that my computer should never go into hibernation... Yet, from what I can tell by looking over my notes, I never simply set "standby" from 0 to 1.
There are interesting questions that arise due to this fix. For example, why did this problem persist on clean installs of OS Yosemite? Is "standby" being set to 0 the Yosemite default? I'm not sure. If it is, then Kappy was right: this was normal behavior... It just wasn't always the normal behavior...at least not for my MBP. Normal behavior (hibernatemode 3) used to be (and now is again) that the MBP goes into safe sleep, and then only after an allotted amount of time will it go into full-blown hibernation.
NOTE: the "standby" and "standbydelay" PMSET settings are not available in some earlier MBP models (e.g., my brother has a 2010 and does not have these settings); so if you're having a similar problem with an earlier model, this fix might not be of any help to you.

Difference between closing the connection before and after committing user transaction?

          I was wondering what's the difference between closing the connection before committing
          the transaction versus closing the connection after committing the transaction?...
          for e.g....
          Scenario 1.........
          UserTransaction useretran;
          usertran.begin();
          Connection con = datasource.getCOnnection();
          // do bunch of stuff...
          conn.close();
          usertran.commit()
          Scenario 2...
          UserTransaction useretran;
          usertran.begin();
          Connection con = datasource.getCOnnection();
          // do bunch of stuff...
          usertran.commit()
          conn.close();
          thanks....
          Srini


Hi. As long as you're sure there's a transaction going on, and the connection
is a transaction-aware object (from a TxDataSource), either will be fine.
In the first scenario the actual semantics of the close() call are less than
normal, because we really don't close the connection or return it to the
pool until the actual transaction commits, and in the second case, we have
already taken the connection out of your service as of the commit().
The second scenario is the usual coding style. If there's ever a chance your
code will get non-transaction-aware connections, it is crucial to close
connections, and I always recommend putting the close() in a finally block
so it's guaranteed to happen.
Joe
srinivas wrote:
I was wondering what's the difference between closing the connection before committing
the transaction versus closing the connection after committing the transaction?...
for e.g....
Scenario 1......... UserTransaction useretran; usertran.begin(); Connection con =
datasource.getCOnnection(); // do bunch of stuff... conn.close(); usertran.commit()
Scenario 2... UserTransaction useretran; usertran.begin(); Connection con = datasource.getCOnnection();
// do bunch of stuff... usertran.commit() conn.close();
thanks....
Srini

User has contribute access but he is not able to access the site collection...

User has contribute access but he is not able to access the site collection...

What error does he get.
Can you share fiddler trace(check if any 404 error)
what error do we see in ULS Logs
Create disableloopback
registry on server
http://support.microsoft.com/kb/926642/en-us

I lose the connection when closing the CMD

Hi guys,
I have configured a standalone listener as following:
C:\Program Files (x86)\Java\jre6\bin> java -Dapex.home=D:\list -Dapex.images=C:\images -jar D:\apex.war
Afterward,
If I close the CMD, I will lose the connection, and I have to reconfigure it again.
If I open APEX locally , I mean by using the shortcut "Get Started With Oracle Database 11g Express Edition" , Then I will lose the connection that uses the default port of the listener, that is 8080.
After I configured the listener I got this message on the CMD
-- listing properties --
PropertyCheckInterval=60
ValidateConnection=true
MinLimit=1
MaxLimit=10
InitialLimit=3
AbandonedConnectionTimeout=900
MaxStatementsLimit=10
InactivityTimeout=1800
MaxConnectionReuseCount=1000
APEX Listener version : 1.1.2.131.15.23
APEX Listener server info: Grizzly/1.9.18-o
May 21, 2011 5:14:41 PM com.sun.grizzly.Controller logVersion
INFO: Starting Grizzly Framework 1.9.18-o - Sat May 21 17:14:41 GST 2011
INFO: http://localhost:8080/apex started.
Using JDBC driver: Oracle JDBC driver version: 11.2.0.2.0
Regards,

Hi,
I'm not sure I got your question right, but I'll try to find some solution anyway.
If I close the CMD, I will lose the connection, and I have to reconfigure it again.That's what happens when a shell is terminated - all associated processes will stop as well. However, if you have a apex-config.xml in your apex.home you shouldn't need to configure your APEX Listener each time your start it, but it would reuse an existing configuration.
If I open APEX locally , I mean by using the shortcut "Get Started With Oracle Database 11g Express Edition" , Then I will lose the connection that uses the default port of the listener, that is 8080.Now, if you have XE running on the same (local) machine as you have your APEX Listener running in standalone mode, you probably have a port conflict: By default, both APEX Listener in standalone mode and the Embedded PL/SQL Gateway (EPG) use port 8080. The EPG is activated as web server for APEX in XE after a fresh installation, the APEX Listener would be an alternative in that case. You can either stop the EPG, or reconfigure any of the two web servers to use a different port, if you want to run them parallel.
To change the port used by the APEX Listener in standalone mode, you simply add another parameter to the startup: -Dapex.port=8888 and you're done.
To change the port used by the EPG, connect as sys and run the following
EXEC DBMS_XDB.SETHTTPPORT(8888);
COMMIT;If you want to disable the EPG, simply set the port to *0* .
After I configured the listener I got this message on the CMDThat's what it should look like.
No, since your topic is "lose the connection when closing the CMD", I assume you search for an alternative. You could run the APEX Listener as a Windows service, even in standalone mode. To do this, you create a batch file, e.g.
%JAVA_HOME%\java -Dapex.home=D:\oracle\APEX_Listener\_home -Dapex.images=D:\oracle\apex_4_0_2\images -Dapex.port=8888 -jar D:\oracle\APEX_Listener\apex_listener.1.1.2.131.15.23\apex.war >>D:\oracle\APEX_Listener\apex_listener.1.1.2.131.15.23\my_apex_listener.log 2>&1Note that you have to set JAVA_HOME as system property or replace the call with the absolute path to your JDK or make sure the JDK is in your PATH variable.
Of course, you can and should change the other directories as well to fit to your system.
Next, create a Windows service, e.g. using [url https://iain.cx/src/nssm/]NSSM (free) or [url http://support.microsoft.com/kb/137890]SRVANY (MS, non-free), that starts your batch as a windows service.
The command for creating that service using NSSM could look as follows
nssm install APEX_Listener D:\oracle\APEX_Listener\apex_listener.1.1.2.131.15.23\startup.cmdYou can edit the service properties afterwards, e.g. change the start mode from "Automatic" to "On Demand".
I hope this answers your question. If not, please point me into the right direction.
Thanks,
Udo

Recycle bin to show all deleted items on the site collection for specific user group

hi there, is there any way where a certain sharepoint group (i.e. site collection members) to view and restore deleted items on theentire collection, without giving them site collection rights orgive them more rights than necessary? we wanted to create
aSP group that has the permission to restore deleted items and give them to selected users so that our users won't have to contact us when they want to restore a deleted item

I don't believe you can. If an item get's deleted it should go to the first recycle bin @ /_layouts/15/RecycleBin.aspx
The Recycle Bin gives a site collection administrator
greater control when users delete files, versions of files, list items, libraries, lists, and folders from a SharePoint site by providing a second stage safety net before an item is permanently deleted from a site. When a user deletes an item from the Recycle
Bin, the item is sent to a second stage Recycle Bin (also known as the Site Collection Recycle Bin) that the site collection administrator manages. This article focuses on how a site collection administrator can manage the Recycle Bin for a site collection.
https://support.office.com/en-US/Article/Manage-the-Recycle-Bin-of-a-SharePoint-site-collection-5fa924ee-16d7-487b-9a0a-021b9062d14b
Ibrahim Sukari, Technical Consultant | SharePoint | Dynamics CRM |
LinkedIn Profile

Closing the Report Viewer causes the application to hang

Hi,
Since a few days we are experiencing some problems with the Crystal Reports viewer. When closing a report viewer in our application, the application hangs for a few minutes. The strange thing is, that it only seems to happen on Windows 7 and Windows 2008 R2 Server.
Our application with the integrated Crystal Report Viewer is running on 2 application servers :
- Windows 2008 Server, versie 6.0 Build 6002, Service Pack 2
- Windows 2008 R2 Server versie 6.1, Build 7600
Crystal Reports version installed on both servers : 12.01.0007.1144
On the 2008 Server, the application works correctly.
On the 2008 R2 server, the application hangs for about 5 minutes while closing the report preview window.
Both server have exactly the same version of Crystal Reports and the same application version.
I'm having the same issue on a Windows 7 x64 (6.1 Build 7600).
I've installed all updates and hotfixes up to SP3 Fix Pack (12.3.3.812 / 12.3.2003.812) but I'm still having the same problem.
We didn't have this problem until a few days ago, so I assume it has something to do with a windows update which only affects Windows 7 and Windows 2008 R2.
Please advice us with a possible workaround, because our application is distributed to a few thousand users ...
Some more debug info :
This is the call of from the main thread when the application hangs :
     [Managed to Native Transition]
>     mscorlib.dll!System.__ComObject.ReleaseSelf() + 0x5 bytes
     mscorlib.dll!System.Runtime.InteropServices.Marshal.ReleaseComObject(object o) + 0x8b bytes
     CrystalDecisions.Shared.dll!CrystalDecisions.Shared.SharedUtils.ReleaseComObject(object obj = {CrystalDecisions.ReportAppServer.ClientDoc.ReportClientDocumentClass}) + 0x75 bytes
     CrystalDecisions.CrystalReports.Engine.dll!CrystalDecisions.ReportAppServer.ISCDClientDocumentEvents_EventProvider.Dispose(bool bDisposeManaged = true) + 0x1a2 bytes
     CrystalDecisions.CrystalReports.Engine.dll!CrystalDecisions.ReportAppServer.ISCDClientDocumentEvents_EventProvider.Dispose() + 0x32 bytes
     CrystalDecisions.CrystalReports.Engine.dll!CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.DisconnectEventRelay() + 0xfc bytes
     CrystalDecisions.CrystalReports.Engine.dll!CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.InternalClose(bool bSetupForNextReport = false, bool bAutoClose = true) + 0x10e bytes
     CrystalDecisions.CrystalReports.Engine.dll!CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.Dispose(bool bDisposeManaged = true) + 0xad bytes
     System.dll!System.ComponentModel.Component.Dispose() + 0x12 bytes
     CrystalDecisions.CrystalReports.Engine.dll!CrystalDecisions.CrystalReports.Engine.ReportDocument.ClearCache(bool clearDocument = true) + 0x9d bytes
     CrystalDecisions.CrystalReports.Engine.dll!CrystalDecisions.CrystalReports.Engine.ReportDocument.InternalClose(bool bSetupForNextReport = true) + 0x81 bytes
     CrystalDecisions.CrystalReports.Engine.dll!CrystalDecisions.CrystalReports.Engine.ReportDocument.Close() + 0x3f bytes
     SyDelSoftControlLibCrystalReports.dll!SyDelSoft.ControlLib.CrystalReports.cReportForm.Dispose(bool disposing = true) + 0x55 bytes
     SDProjects.exe!SDProjects.GUI.ReportForm.Dispose(bool disposing) + 0x38 bytes
SharedUtils.ReleaseComObject
Kind regards,
Frederic Hoornaert

CrystalReportsDisposeIssue.crpe.Diagnostics.0.log
--> Form3 closed
..\..\src\print\datasource\datasrc2.cpp:535,Releasing subreport data sources,Start Time,"17:39:17"
N/A:-1,Releasing subreport data sources,Elapsed Time,"1"
..\..\src\crpe\crpe.cpp:791,Closing engine,Start Time,"17:39:17"
..\..\src\crpe\crpe.cpp:833,Closing engine,Before close engine use count,"7"
..\..\src\crpe\crpe.cpp:858,Closing engine,After close engine use count,"6"
N/A:-1,Closing engine,Elapsed Time,"2"
..\..\src\crpe\crpe.cpp:791,Closing engine,Start Time,"17:39:17"
..\..\src\crpe\crpe.cpp:833,Closing engine,Before close engine use count,"6"
..\..\src\crpe\crpe.cpp:858,Closing engine,After close engine use count,"5"
N/A:-1,Closing engine,Elapsed Time,"2"
--> Form2 closed
..\..\src\print\datasource\datasrc2.cpp:535,Releasing subreport data sources,Start Time,"17:39:52"
N/A:-1,Releasing subreport data sources,Elapsed Time,"1"
..\..\src\crpe\crpe.cpp:791,Closing engine,Start Time,"17:39:52"
..\..\src\crpe\crpe.cpp:833,Closing engine,Before close engine use count,"4"
..\..\src\crpe\crpe.cpp:858,Closing engine,After close engine use count,"3"
N/A:-1,Closing engine,Elapsed Time,"2"
--> Form1 closed..\..\src\print\datasource\datasrc2.cpp:535,Releasing subreport data sources,Start Time,"17:40:29"
N/A:-1,Releasing subreport data sources,Elapsed Time,"1"
..\..\src\crpe\crpe.cpp:791,Closing engine,Start Time,"17:40:29"
..\..\src\crpe\crpe.cpp:833,Closing engine,Before close engine use count,"2"
..\..\src\crpe\crpe.cpp:858,Closing engine,After close engine use count,"1"
N/A:-1,Closing engine,Elapsed Time,"2"
..\..\src\crpe\crpe.cpp:791,Closing engine,Start Time,"17:40:29"
..\..\src\crpe\crpe.cpp:833,Closing engine,Before close engine use count,"1"
..\..\src\crpe\crpe.cpp:858,Closing engine,After close engine use count,"0"
N/A:-1,Closing engine,Elapsed Time,"100017"
CrystalReportsDisposeIssue.crpe.functions.0.log
0xfb8     17:39:17.871          0     PESetUserSessionInfo               0     PEUserSessionInfoW:<StructSize:262><userName:><requestID:22>     IN          21     <==
0xfb8     17:39:17.871     0     0     PESetUserSessionInfo               0     OUT     PEUserSessionInfoW:<StructSize:262><userName:><requestID:22>          21     <==
0xfb8     17:39:17.874          3     PEClosePrintJob     report {657D0ECA-BC6A-4EC6-9476-02B77376E07C}.rpt          0     jobN:3     IN          22     <==
0xfb8     17:39:17.874     36     3     PEClosePrintJob     report {657D0ECA-BC6A-4EC6-9476-02B77376E07C}.rpt          0     OUT     jobN:3          22     <==
0xfb8     17:39:17.913          0     PECloseEngine               0     void     IN          22     <==
0xfb8     17:39:17.913     3     0     PECloseEngine               0     OUT     void          22     <==
0xfb8     17:39:17.923          0     PECloseEngine               0     void     IN          0     <==
0xfb8     17:39:17.923     3     0     PECloseEngine               0     OUT     void          0     <==
0xfb8     17:39:52.421          0     PESetUserSessionInfo               0     PEUserSessionInfoW:<StructSize:262><userName:><requestID:23>     IN          0     <==
0xfb8     17:39:52.421     0     0     PESetUserSessionInfo               1032     OUT     PEUserSessionInfoW:<StructSize:262><userName:><requestID:23>          0     <==
0xfb8     17:39:52.423          1     PEClosePrintJob     report {F2574C5C-00BC-4627-9A05-B8133D6E6F7D}.rpt          0     jobN:1     IN          0     <==
0xfb8     17:39:52.423     15     1     PEClosePrintJob     report {F2574C5C-00BC-4627-9A05-B8133D6E6F7D}.rpt          0     OUT     jobN:1          0     <==
0xfb8     17:39:52.441          0     PECloseEngine               0     void     IN          0     <==
0xfb8     17:39:52.441     3     0     PECloseEngine               1032     OUT     void          0     <==
0xfb8     17:40:29.281          0     PESetUserSessionInfo               0     PEUserSessionInfoW:<StructSize:262><userName:><requestID:24>     IN          0     <==
0xfb8     17:40:29.281     0     0     PESetUserSessionInfo               1032     OUT     PEUserSessionInfoW:<StructSize:262><userName:><requestID:24>          0     <==
0xfb8     17:40:29.283          2     PEClosePrintJob     report {C78FE11F-6465-478F-83AB-49D8F0C6D64A}.rpt          0     jobN:2     IN          0     <==
0xfb8     17:40:29.283     24     2     PEClosePrintJob     report {C78FE11F-6465-478F-83AB-49D8F0C6D64A}.rpt          0     OUT     jobN:2          0     <==
0xfb8     17:40:29.310          0     PECloseEngine               0     void     IN          0     <==
0xfb8     17:40:29.310     2     0     PECloseEngine               1032     OUT     void          0     <==
0x1568     17:40:29.315          0     PECloseEngine               0     void     IN          0     <==
0x1568     17:40:29.315     100018     0     PECloseEngine               0     OUT     void          0     <==

Closing the report generating engine automatically

how can i close the report generating engine after displaying a report automatically ie when closing the report window the report generating engine also need to be closed. now i have to manually close the report background window also and it becomes annoying to users . i am using the rdf files and not rep files.

There is a parameter ORACLE_SHUTDOWN. Set it to YES.
When you have large, complex reports, the Reports Background engine sometimes eats lots of memory and leads to GPF. If you have lots of GPF when running a report, you should use this parameter.
null

Closing the device deletes what has been typed to that point. Is this normal?

Closing the device deletes what has been typed as an e-mail up to that point. Is this normal, and can it be avoided?

If the content you typed was actually saved before you quit the session, it should be there
later on when you open it again. There may be some settings in preference to auto-save
that may need checking; or perhaps there could be something else behind this issue...
To be sure, which device do you refer?

Closing the PR collectively

Similar Messages

Maybe you are looking for