Serious locking issues with Main Stage 3

Having serious locking issues with main stage 3. I just did a music gig over the weekend with main stage 3, and the application locked up 8 times during my performance. There were also several times where there was a delay between the time I struck a key on the midi controller and the time sound actually came out of the audio interface. Has anyone else ran into this problem??
10.
I am running mountain lion 10.8.5, on a 2009 Macbook 2.53 GHz Intel Core 2 Duo. w 8 GB Ram.
Anyone know how to fix this, if even possible?

Just read some reviews. There seems to be a lot of problems with the latest main stage update. I didn't notice these latency problems until did the latest update..
Apple please fix this quickly!!!

Similar Messages

Serious resolution issues with After Effects CC (2014) on Windows 8.1 Pro on Dell Precision M3800 laptop??

My new company installed Adobe Creative Cloud (There was some annoying Proxy issues at first, because of the seriously tight I.T policies) but we are having some serious resolution issues with After Effects CC 2014 (also have this resolution problem with Adobe Premiere, Media Encoder, Muse) on Windows 8.1 Pro on a Dell Precision M3800 laptop with icons and interface looking too small and hard to see, is there a fix, an update or a work around, can anyone help?
Any help will be appreciated!
k.regards
Ramon

Hi Todd is there a time-frame for this fix, there is a lot of pressure on me, because I convinced my company to get the Creative Cloud and quite a lot of the CC software is not compatible with the latest Windows 8.1 OS.
Is there at least a work around, until this big fix comes along?
k.regards
Ramon

[ADF-11.1.2] Locking issue with SQL 92

I see one Locking issue with SQL92 Oracle ADF Application.
ADF Version: [ADF-11.1.2]
Database: Oracle 10g Express Edition
Situation 1:
With Following setting:
File: Application Resource > Description > ADF META-INF > adf-config.xml
    <startup>
      <amconfig-overrides>
        <config:Database jbo.SQLBuilder="SQL92" jbo.locking.mode="optimistic"/>
      </amconfig-overrides>
    </startup>I have a page showing record 'x' of view object. I open same record on another page. Now I have same record showing on two different tabs of browser.
1. I modify first record and save it. It worked... Got commited to database.
2. I goto second tab and modify same record and tried to same it. It throws me an error - Another user has changed the row with primary key oracle.jbo.Key[38 ] . As expected...
3. I then, reopen the same record on 3rd tab of browser. Modify it and tried to save it. It just hang... as if it is processing the record endlessly.
If I see the Log:
<BaseSQLBuilderImpl> <doEntitySelectForAltKey> [312] BaseSQLBuilderImpl Executing doEntitySelect ... (true)
<BaseSQLBuilderImpl> <doEntitySelectForAltKey> [313] Generating new LOCK statement
<BaseSQLBuilderImpl> <buildSelectString> [314] Built select: 'SELECT ID, CI_ID, COLUMN_NAME, DISPLAY_COLUMN_NAME, COLUMN_VALUE, CREATE_DATE, CREATE_BY FROM ESUSER.CI_AUDIT'
<BaseSQLBuilderImpl> <doEntitySelectForAltKey> [315] Executing LOCK "SELECT ID, CI_ID, COLUMN_NAME, DISPLAY_COLUMN_NAME, COLUMN_VALUE, CREATE_DATE, CREATE_BY FROM ESUSER.CI_AUDIT WHERE ID=? FOR UPDATE"
<BaseSQLBuilderImpl> <bindWhereAttrValue> [316] Where binding param 1: 38
That's it.. nothing happens further.. If I execute above query on SQL Worksheet, it doesn't come up with the result. Just hang for something...
SELECT ID, CI_ID, COLUMN_NAME, DISPLAY_COLUMN_NAME, COLUMN_VALUE, CREATE_DATE, CREATE_BY FROM ESUSER.CI_AUDIT WHERE ID='38' FOR UPDATE I can execute above query for other record of same table but not '38'. Even if I fire commit command to database, it is not working.
I have to restart the database services to bring everything to normal state.
Situation 2:
With Oracle as Database :
    <startup>
      <amconfig-overrides>
        <config:Database jbo.SQLBuilder="Oracle" jbo.locking.mode="optimistic"/>
      </amconfig-overrides>
    </startup>Everything is working file. i.e. at step 3, record is getting modified successfully with following log:
<OracleSQLBuilderImpl> <doEntitySelectForAltKey> [27] OracleSQLBuilder Executing doEntitySelect on: ESUSER.CI_AUDIT (true)
<ADFLogger> <begin> Entity read all attributes
<OracleSQLBuilderImpl> <buildSelectString> [28] Built select: 'SELECT ID, CI_ID, COLUMN_NAME, DISPLAY_COLUMN_NAME, COLUMN_VALUE, CREATE_DATE, CREATE_BY FROM ESUSER.CI_AUDIT CIAudit'
<OracleSQLBuilderImpl> <doEntitySelectForAltKey> [29] Executing LOCK...SELECT ID, CI_ID, COLUMN_NAME, DISPLAY_COLUMN_NAME, COLUMN_VALUE, CREATE_DATE, CREATE_BY FROM ESUSER.CI_AUDIT CIAudit WHERE ID=? FOR UPDATE NOWAIT
<ADFLogger> <addContextData> Entity read all attributes
<OracleSQLBuilderImpl> <bindWhereAttrValue> [30] Where binding param 1: 38
<ADFLogger> <addContextData> Entity read all attributes
<ADFLogger> <end> Entity read all attributes
<ADFLogger> <end> Lock Entity
<ADFLogger> <begin> Before posting the entity's changes
<ADFLogger> <begin> Updating audit columns
<ADFLogger> <end> Updating audit columns
<ADFLogger> <end> Before posting the entity's changes
<OracleSQLBuilderImpl> <doEntityDML> [31] OracleSQLBuilder Executing, Lock 2 DML on: ESUSER.CI_AUDIT (Update)
<OracleSQLBuilderImpl> <buildUpdateStatement> [32] UPDATE buf CIAudit>#u SQLStmtBufLen: 210, actual=60
<OracleSQLBuilderImpl> <doEntityDML> [33] UPDATE ESUSER.CI_AUDIT CIAudit SET COLUMN_VALUE=? WHERE ID=?
<ADFLogger> <begin> Entity DML
<OracleSQLBuilderImpl> <bindUpdateStatement> [34] Update binding param 1: cip7ri1
<OracleSQLBuilderImpl> <bindWhereAttrValue> [35] Where binding param 2: 38
<ADFLogger> <addContextData> Entity DML
<ADFLogger> <end> Entity DML
Can any one please tell me, what is the issue with SQL92 setting ?
Edited by: Anandsagar Sah on Mar 11, 2012 8:10 AM

The framework works correctly in the Situation #1. Please, note that the locking statement in this case is "SELECT ... FOR UPDATE", but not "SELECT ... FOR UPDATE NOWAIT" (as it is in the Situation #2). When you entered the 2nd tab and tried to update the row, then the framework executed the locking statement and the row was locked (and it remained locked because the framework detected that another user had modified the row, so it stopped the processing and no COMMIT operation was executed). When you entered the 3rd tab and tried to update the row, then the framework tried to lock the row againg, but the locking statement was blocked by the existign lock and it started waiting on the lock from the 2nd tab. So this is expected behaviour.
The interesting question is why you do not get any error in the Situation #2. In my opinion you should get an error because the locking statement from the 3rd tab should fail immediately (because the row should have been locked from the 2nd tab and the locking statement is with NOWAIT option). I suspect that when the DB is Oracle and you use Oracle SQLBuilder, then the ADF issues a DB savepoint at the beginning of the DML operation and rolls back to the savepoint is a case of some failure, so the 2nd tab has not left any lock. You can check this by setting on SQL trace on the DB server.
Dimitar

SERIOUS lag issues with Intel iMac

Hello everyone,
I'm pretty frustrated right now. I've been having this serious lag issue with my new iMac for the past few days. I think it may have started after I ran the last security update.
What happens:
When switching between apps, the system will hang for 1-3 seconds between doing anything. This includes typing, mouse requests, etc. It's VERY frustrating. I have activity monitor open currently, and I am seeing both Safari and SystemUIServer hogging up the CPU resources like CRAZY. I've even seen Safari recently give a CPU usage of 120%, right before I loaded this webpage. tis isn't just centralized to Safari too.... I have the following apps running:
Adium 0.89.1
FoireFox 1.5.0.8
Safari
Activity Monitor
My Memory stats currently are:
175MB Wired
708MB Active
618MB Inactive
1.47GB Used
There should be no reason I'm getting these lags with just two web browsers and a chat client open.
Has anyone else expierenced the lags?? Any suggestions? I'm almost ready to reinstall OS X and not run the last security update. Thanks
iMac 1.83 GHz Core Duo Mac OS X (10.4.8) 1.5GB RAM, Extermal LaCie 160GB FW Porsche Drive, Griffin iMate, iPod Min 4GB, JBL Creature Speakers

Hello Matthew
Are you running any maintenance scripts on a regular basis?
http://www.thexlab.com/faqs/maintscripts.html
I would manually run this script from The X Lab, and my load times would improve greatly. The problem was, I would forget to run them untill I noticed web pages loading slow or iTunes and iPhoto taking for ever. It wasn't untill someone here in discussions suggested Anacron that I saw the light. WOW what a difference Anacron has been making in my overall system speed. My iMac has not been shutdown for 11days 5hrs 34mins (sleep or use only) and opening new App's, switching App's and web pages load as fast or faster than after a fresh start up. If your system is operating properly and you are having only what seems to be a slow or sluggish issue Anacron will make a difference.
http://members.cox.net/18james/anacron-tiger.html
Dennis
17" iMac Intel Core Duo 1.5GB Ram Mac OS X (10.4.8) Maxtor 300GB FireWire 2G Nano

Serious Power Issues with T61

All,
The organization I work for has started to have some serious power issues with our T61 model Thinkpads. Additionally, the problem now seem to be carrying over into our T500 Thinkpads.
About 4 months ago we started receiving consistant calls regarding users that can't power their laptops on. These are T61 and T500 laptops mounted to mobile carts in our various nursing units in numerous hospitals. These laptops sit stationary for 95% of the time and are almost always plugged into wall power. We quickly discovered that the only way to get the laptops to power on was to unplug them from all power sources and reseat the battery, after which they powered right on. We've had this problem in the past with users T61s that aren't on carts, but this is slightly different as the batteries on the cart mounted laptops are always 100% drained after we reseat them.
I'm completely baffled by this issue. I've tried every variation of 3 different carts, -- one with external battery on cart, two without -- both 90 and 65 watt power supplies, and standard and 9 cell batteries that I can come up with and the problem continues to occur. Initially we had atributed the problem to ESD because this started during the low humidity months of winter, but it is now spring and the problem is still happening.
Under normal circumstances I'd just replace the few ailing laptops and call them in under warranty, but this seems to be a general model issue as this is occuring across the board on 100+ laptops at this hospital alone. Any assistance to help identify the issue and/or how to resolve it would be appreciated.
Thanks,
David

Slider5634,
Do you have a critical situation open for this? If so, while you are free to post here, working through the project office as a managed account should get you to the right level of support to address an issue that sounds pervasive, and may or may not be influenced by unknown environmental factors.
If you don't have a situation open, then I would urdge you to contact your account rep. If you need help, or unsure of this, please send me a PM with your contact information, and your hospital or corp account name so I can get you the right level of assistance.
jgm1234,
What model type T61's are you experiencing this issue with? Can you provide some more information here about the situation? Configuration, when this first started occuring, environment (connected to lan, wired / wireless, stand alone, all in same physical location, or distributed at multiple locations, etc)
Thanks!
Mark
ThinkPads: S30, T43, X60t, X1, W700ds, IdeaPad Y710, IdeaCentre: A300, IdeaPad K1
Mark Hopkins
Program Manager, Lenovo Social Media (Services)
twitter @lenovoforums
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

Row locking issue with version enabled tables

I've been testing the effect of locking in version enabled tables in order to assess workspace manager restrictions when updating records in different workspaces and I have encountered a locking problem where I can't seem to update different records of the same table in different sessions if these same records have been previously updated & committed in another workspace.
I'm running the tests on 11.2.0.3. I have ROW_LEVEL_LOCKING set to ON.
Here's a simple test case (I have many other test cases which fail as well but understanding why this one causes a locking problem will help me understand the results from my other test cases):
--Change tablespace names as required
create table t1 (id varchar2(36) not null, name varchar2(50) not null) tablespace XXX;
alter table t1 add constraint t1_pk primary key (id) using index tablespace XXX;
exec dbms_wm.gotoworkspace('LIVE');
insert into t1 values ('1', 'name1');
insert into t1 values ('2', 'name2');
insert into t1 values ('3', 'name3');
commit;
exec dbms_wm.enableversioning('t1');
exec dbms_wm.gotoworkspace('LIVE');
exec dbms_wm.createworkspace('TESTWSM1');
exec dbms_wm.gotoworkspace('TESTWSM1');
--update 2 records in a non-LIVE workspace in preparation for updating in different workspaces later
update t1 set name = name||'changed' where id in ('1', '2');
commit;
quit;
--Now in a separate session (called session 1 for this example) run the following without committing the changes:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--Now in another session (session 2) update a different record from the same table. The below update will hang waiting on the transaction in session 1 to complete (via commit/rollback):
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
I'm surprised records of different ids can't be updated in different sessions i.e. why does session 1 lock the update of record 2 which is not being updated anywhere else. I've tried this using different non-LIVE workspaces with similar results. I've tried changing table properties e.g. initrans with and still get a lock. The changes to table properties are successfully propagated to the _LT tables but not all the related workspace manager tables created for table T1 above. I'm not sure if this is the issue.
Note an example of the background workspace manager query that may create the lock is something like:
UPDATE TESTWSM.T1_LT SET LTLOCK = WMSYS.LT_CTX_PKG.CHECKNGETLOCK(:B6 , LTLOCK, NEXTVER, :B3 , 0,'UPDATE', VERSION, DELSTATUS, :B5 ), NEXTVER = WMSYS.LT_CTX_PKG.GETNEXTVER(NEXTVER,:B4 ,VERSION,:B3 ,:B2 ,683) WHERE ROWID = :B1
Any help with this will be appreciated. Thanks in advance.

Hi Ben,
Thanks for your quick response.
I've tested your suggestion and it does work with 2 workspaces but the same problem is enountered when additional workspaces are created.
It seems if multiple workspaces are used in a multi user environment, locks will be inevitable which will degrade performance especially if a long transaction is used.
Deadlocks can also be encountered where eventually one of the sessions is rolled back by the database.
Is there a way of avoiding this e.g. by controlling the creation of workspaces and table updates?
I've updated my test case below to demonstrate the extra workspace locking issue.
--change tablespace name as required
create table t1 (id varchar2(36) not null, name varchar2(50) not null) tablespace XXX;
alter table t1 add constraint t1_pk primary key (id) using index tablespace XXX;
exec dbms_wm.gotoworkspace('LIVE');
insert into t1 values ('1', 'name1');
insert into t1 values ('2', 'name2');
insert into t1 values ('3', 'name3');
commit;
exec dbms_wm.enableversioning('t1');
exec dbms_wm.gotoworkspace('LIVE');
exec dbms_wm.createworkspace('TESTWSM1');
exec dbms_wm.gotoworkspace('TESTWSM1');
update t1 set name = name||'changed' where id in ('1', '2');
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
--end of original test case, start of additional workspace locking issue:
Session 1:
rollback;
Session 2:
rollback;
--update record in both workspaces
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '3';
commit;
exec dbms_wm.gotoworkspace('TESTWSM1');
update t1 set name = 'changed' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
exec dbms_wm.gotoworkspace('LIVE');
exec dbms_wm.createworkspace('TESTWSM2');
exec dbms_wm.gotoworkspace('TESTWSM2');
update t1 set name = name||'changed2' where id in ('1', '2');
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this now gets locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
--update record 3 in TESTWSM2
exec dbms_wm.gotoworkspace('TESTWSM2');
update t1 set name = 'changed' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this is still locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
--try updating LIVE
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this is still locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
--try updating TESTWSM1 workspace too - so all have been updated since TESTWSM2 was created
exec dbms_wm.gotoworkspace('TESTWSM1');
update t1 set name = 'changed' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this is still locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
--try updating every workspace afresh
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changedA' where id = '3';
commit;
exec dbms_wm.gotoworkspace('TESTWSM1');
update t1 set name = 'changedB' where id = '3';
commit;
exec dbms_wm.gotoworkspace('TESTWSM2');
update t1 set name = 'changedC' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this is still locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;

Triggering program form(subroutine) from MIGO using output types gives lock issue with Bapi_sag_change

Hi,
On creating the GR from MIGO tcode, based on the quantity check i am updating the field ELIKZ using BAPI_SAG_CHANGE.
And updation logic is written in a zprogram using with in FORM XXXXX...ENDFORM XXXXX. ( FORM XXXXX is configured in the output type ).
So the problem i am facing is on creation of the first GR with scheduling agreement number GR is posted successfully and under the output tab the i can see the green icon.
But on creation of the second GR with same scheduling agreement its showing red icon. The following is the error message " User locked the scheduling agreement ...."
I even tried using dequeue fm and transaction commit, but it didnt work. Please let me know how to over come the lock issue.
Thanks & regards,
Manojkumar K

Solved it myself....
Regards,
Manoj

Serious boot issues with Powerbook G3 (Wallstreet II, OS 9.2.2)

Hello,
I have major issues with a Powerbook Wallstreet II I got recently. When it's finally running, it works just as well as Wallstreet Powerbooks usually do, no errors, no crashing, smooth performance, everything fine.
But booting it up is, to put it mildy, a bloody pain. First off, it does not power up, when it's only connected to batteries. I have two of them, both working fine for several hours when put in after bootup, but no matter if I place one or both of them in any bays, nothing happens when pressing or holding the power button (apart from screen flickering and speaker crackling). I'm always forced to connect the power adapter, which immediatly (without pressing the power button) causes the power LED to light and the cooling fan insanely spins up for a mere couple of split seconds until everything wents silent again.
Having reached this point, I can disconnect the power supply (if at least one battery is in) and usually hear a nice "BONG" when pressing the power button once again. Thereafter, nothing happens for a oppressive 30 seconds, then, the screen finally lits and shows the Mac OS 9.2.x splash screen on monochrome background. Sadly, this is already the end of most of my first boot up tries, because at this point, I usually get told by a dialogbox that a bus error has just happened. The box also has a nice "Reboot" button, which I cannot click as the trackpad hangs as well.
Pressing ShiftFn+CrtlPower works here in about one out of three time, so in most cases, I have to go through the same procedure. Pull out power sources, give a shot via PSU, have it iddling for 30 secs. In most cases, this second try lets me pass splash screen, loader, yes, it even lets me see the desktop, the taskbar, the HDD icon and... pouf. Success is so close but no, it has to suddenly drop into sleep mode and
a short press on power proves the apprehension true, that it won't be easy to wake it up again. Hrmph. But I don't give that easily. So pulling everthing out for the second time, connect PSU for the third time and look there, it fully boots.
Three tries to successfully boot is about average at first try series. Afterwards, it seems to be "warmed up" and things get easier. I made a log recently with 5 test series, made at very frequent intervals:
Series 1:
1. Bootup: Bus Failure (Hard reboot fails) (bays empty)
2. Bootup: Sleep Mode (bays empty)
3. Bootup: Sleep Mode (bays empty)
4. Bootup: Sleep Mode (both batteries)
5. Bootup: Bus Failure (Hard reboot successful)(both batteries)
6. Bootup: Success (left battery, right bay empty)
Series 2:
1. Bootup: Success(left battery, right bay empty)
Series 3:
1. Bootup: Bus Failure (!!!) (left battery, right bay empty)
2. Bootup: Success (bays empty)
Series 4:
1. Bootup Success (left bay empty, right battery)
Series 5:
1. Bootup Success (both batteries)
Thanks in advance for any helpful suggestions.

jpl,
Thank you for continuative support.
If you plan on buying a 256MB memory module, the Wallstreet requires
a 256 specifically made for it (and the early iMac
and Lombard). Modules 128MB and smaller can be
generic if they meet the Wallstreet's specs.
Thanks for this information.
You might find it useful to disassemble the 'book to the PMU, carefully remove/reseat the PMU card, then test.
Well, to be honest, I don't have the time to perform this very labour-intensive work. However, I pulled out the large PMU connector (the one that can be reached by lifting the keyboard) and reseated it, without any results. Shouldn't that suffice? Or is there another connection that could need maintenance?
Regarding sleep: There is no display position sensor, only a simple magnet in the right display bezel approximately 4" from the bottom...you can stick a paperclip to it. When the display closes, it triggers a sleep switch located next to the delete key in the side rail.
Ah, okay.
According to Apple, if the powerbook will not run on battery, it could be the charge card or PMU board or power supply card or logic board. However, your 'book apparently runs on battery once started via power adapter.
Actually, it does not allow me to power up, if I attach the adapter right after an unsuccessful try to operate from battery. Even if I remove the batteries (after adapter connection).
It's like it is "crashed" before it's even running. Which means, I have to pull all power sources to be able to perform the resuscitating power up via adaptor.
A normal power manager reset on the Wallstreet is this:
1. If the computer is on, turn it off.
2. Simultaneously press Shift-Fn (function)-Ctrl >(control)-Power.
3. Wait 5 seconds.
4. Press the Power button to restart the PowerBook >computer.
A successful reset will briefly flash the sleep light plus >spin up the fan for a second. If a reset does not solve the >startup and sleep issues, then you will have to look >elsewhere.
I can see the sleep LED and I do hear the fan, however, this didn't help in most cases. After perfoming this action (in a freeze situation), I usually only got rattling noises out of the speakers or screen flashes when trying to power up.
Be sure the powerbook only freezes when closing the display to sleep it.
Well, I noticed it sometimes also freezes when left idle directly after start up (and power save is activated). Later, it comes right back again.
- Is the sleep light blinking before you open the display?
Yes.
- When the display is opened, does the sleep light continue to blink? (It should.)
Yes.
- When you press the power button, do you hear a 'buzz' or some similar noise? If you do, you may have another issue to explore.
No. I usually only hear speaker noise when trying to power up from battery. But oddly enough, the lenght of the sleep light blinks changes when power button is hold down in "frozen sleep".
I would also go to the System Folder > Preferences folder and drag the Energy Saver Preferences to the Trash, close all windows, then restart...a new preference file will be created on restart. You can reset the Energy Saver to your like, then test sleep.
Done.
-Does sleep/wake always work when NOT closing the display? Try this after resetting the power manager and trashing the pref file mentioned below.
If I initiate sleep, yes. If it suspends automatically, well, usually. But not always (see above).

Problems with Main Stage Assignments

Hi
I have set up my assignments in Main Stage 3.0 which was working a treat. Then, for no apparent reason, the assignments are changing themselves.
For instance, i have a button on my controller to change patch, and (half way through a gig!) I pressed this button and it plays a note on the keyboard instead.
My master volume decides it doesn't want to be controlled by the slider assigned to it. So I go into layout mode and reassign again, works for a bit, and then loses its assignment.
I would be very grateful if anyone had a clue as to why this is happening.
Thanks

Hi dondedondon,
What is your controller? Can it be because at some point you choose another midi channel in your controller?

Locking issue with BAPI_GOODSMVT_CREATE in userexit_save_document

Hello All,
I am performing a separate goods movement for one of the materials in the delivery userexit_save_document during PGI. I have an issue. We might have multiple users trying to PGI deliveries and thereby performing the goods movement for the same material through the BAPI in the userexit_save_document.
How do I prevent the locking issue when say two users go through the BAPI for goods movement for the same material data at the same time.
Any answer in this regards is highly appreciated.
Thanks,
Mathangi

Thanks Rich... this make work for me, but one question -
Do you know if this function releases all lock objects for the user system wide or only for the current session? My concern is that if it is system wide, then I could be releasing lock objects for other sessions unintentionally. For example, if there are multiple RFC calls in parallel for the same function and same user then I could be destroying lock entries that I shouldn't be! I am hoping that it removes lock entries only for the current session...
any ideas?
Regards,
Lee
> I've used this BAPI in many of my programs, and
> always after the call, I code.....
>
>
>
> commit work and wait.
> call function 'DEQUEUE_ALL'.
>
>
>
> The DEQUEUE_ALL show release any/all locks.
>
>
> Regards,
> Rich Heilman

Serious mouse issues with GTK

my mouse and touchpad for my laptop have always worked without any sort of problem. i recently switched to openbox from gnome and it's been a wonderful experience so far. i tried cleaning out unnecessary gnome stuff and installed KDE to toy with it a little. needless to say shortly afterwards i ditched KDE and switched back to openbox, only to discover my mouse being screwed. i can move the cursor around and such but after a few seconds of running my ability to click and right-click is gone. i tried re-installing gnome completely hoping it might effect it and logged into a gnome session instead but the problem is persisting here as well. if i am using my mouse in a window, i cannot select anything on the panels with it whatsoever without repeatedly right clicking in the window close to the panel and then clicking the panel. and whenever i have the panel selected i can interact with it fine but cannot switch over to any windows. it's making me believe there's something going on with the mouse thinking it's "stuck" on the panel or window so clicking outside of it is rendered useless. i really don't know, i've tried searching online and such for any help on the topic but could not find anything and this is my final resort before going completely mad. any help would be greatly appreciated.
EDIT: i've tried toying with settings in gnome in regards to the mouse and stuff, basically just doing anything i possibly can and while using a window from the control panel for the mouse and clicking within it i started opening a ton of control panel items (appearance, etc.) leading me to believe it's definitely an issue of the mouse being stuck in a window or something.
Last edited by hustletrees (2010-07-01 04:11:28)

Your mouse is handled by xorg, so you need to make sure it's configured correctly. "mouse issues with GTK" simply doesn't make any sense.
My guess is that somewhere in the middle of changing WM/DE, you also did a system upgrade (a good thing) without reading Arch news (a bad thing), so you now have xorg 1.8 and you need to change your config accordingly.

Serious performance issues with no solution in sight

I hate to be in such desperate need of help, but these forums have been extraordinarily helpful before, so I'm hoping someone will be able to help me with this series of problems.
I honestly don't know how to describe the problem beyond that it seems like the computer is coming apart.
The problem started about a week and a half, maybe two weeks, ago. I was having problems with Safari at first. Every time I used it, I would get the spinning ball, and it would take several minutes to open. If Safari was opened, the computer seemed to just lock up. No other applications could be opened, and no folders could be used. On top of that, whenever that spinning ball appeared, a series of clicking sounds could be heard coming from the upper left hand portion of the laptop (not the screen). The only way I could make it stop was to force quit (and even that was a luck of the draw issue).
I took the computer in to be checked out, but their scans and tests showed the same results as mine: nothing is wrong. The problem has since spread beyond Safari, which I ended up erasing from my computer. That same rhythmic clicking happens whenever the spinning ball appears. I have tried to find some kind of pattern to the sound/spinning ball, but have thus far been unsuccessful.
It has happened when using iTunes, saving with appleworks, having AOL instant messenger open, using Firefox, using quicktime. Whenever it happens, my system basically locks up and renders all applications useless. Force quitting is the only way I can get things going again, and even then it can take several minutes for me to even be able to force quit.
Also, software updates quit before I can download them.
I apologize for the long post, but I want to try and provide as much information as possible.
To me this sounds like a failing hard drive, and that is what the tech thought, but the tests just show nothing is wrong, and I cannot comprehend why.
My many thanks in advance for any help you can provide.

Hi Samuel,
I will agree that louder than normal clicking is a sign of something wrong with the hard drive. But you might just be hearing the hard drive working normally, it just might be doing it a lot more.
If you haven't tried a permissions repair, try one. It's worth a try, and I have known it to improve the performance of my Macs to some extent.
Also, if you have access to it, Try DiskWarrior. DiskWarrior is a program that will take your hard drive and rebuild the directory for it, clearing up errors and improving overall performance.
If you've got the means to do this, try reformatting your system. It's a lot of work, I'll admit, but perhaps something got corrupted and it could be messing up your performance.
Another thing you can try is to boot OS X from some sort of external hard drive (if you happen to have a friend who happens to own an external hard drive with OS X on it... wait, am I the only one??? darn.) and see if the problem exists when running off the other drive. If you don't happen to have such a hard drive (I mean, everyone's got a spare external hard drive with OS X installed on it, don't they?) you can simply boot a friend's Mac in FireWire target disk mode (boot the computer while holding T key), connect the 2 computers, and boot your system from the friend's hard drive (by holding the option key at startup). Of course, if none of your friends own Macs, you need to find better friends!
Basically, though, if your computer successfully boots from one of these other systems and doesn't exhibit these symptoms, then it's something with your hard drive. Try first to reformat (or at least re-install OS X), and if that doesn't work, you'll have to do a repair.
If you have to resort to calling tech support, I'll bet you $10,000 that they're going to ask you to reset the PMU and/or the PRAM on your system. Your computer could have dirt on it, and they'd have you reset the PRAM and the PMU.

Weird File Locking Issue with Excel 2013

We are experiencing a strange issue whereby we are frequently unable to save Excel files; whilst working on a document a user will select Save As, change the name of the document and attempt to save, a 0KB file is created in the location and an error returned
to the user stating that the file is in use by another user. At this point it is normally possible to save but on occasion this has also failed. It is possible to duplicate the issue on multiple machines.
The user has Full control over the destination directory, both share & NTFS.
File Server is running Windows Server Essentials 2012R2.
The Users desktops are running Windows 7 sp1, all available Windows Updates have been applied.
They have an Office 2013 Small Business Premium subscription, two of the users have a full msi based installation of Office and one the Click-to-Run version.
They use Eset Endpoint Antivirus and Eset File Security on the server, the problem can be duplicated with both client & server antivirus disabled.
Have disabled power saving on client & server network cards.
Does anyone have any suggestions on how to troubleshoot this?

Hi,
As far as I know, if one user had opened or edited one file in File Server, the other users only could be open the file read-only. It could not be saved or other behavior.I would suggest the following:
Turn off the Preview Pane, Details Pane and pop ups that show information about file and desktop items.
This is a problem that has been reported to affect Windows 7 clients only, not Windows XP. The problem here may have something to do with the Windows Explorer in Windows 7. We are currently investigating this further and will post more information as it
is available.
In a Windows Explorer window, do the following:
1. Right click on the Start Button.
2. Click 'Open Windows Explorer'.
3. At the top left click Organize > Layout
4. Uncheck Details Pane and Preview Pane.
5. On a Windows menu, click on Tools > Folder Options. In the box that opens up, click on the View tab. Scroll down the list to
“Show pop-up description for folder and desktop items” and clear the checkbox and then click OK.
http://blogs.technet.com/b/the_microsoft_excel_support_team_blog/archive/2012/05/14/the-definitive-locked-file-post.aspx
BTW, I recommend you
use a shared workbook to collaborate in Excel.
Regards,
George Zhao
TechNet Community Support

BAPI_GOODSMVT_CREATE lock issue with no access to ABAP!

Hello everyone,
I have written a class in vb .NET that uses the BAPI_GOODSMVT_CREATE to post goods issues. I have done numerous tests myself which all were successful. However, when a colleague wanted to test my class he suddenly got the following error "The plant data of the material <XXXX> is locked by the user <XXXX>". The user specified is the standard background user we use for RFCs. So basically the user is blocking himself.
This issue seems to be quite common as Google turns up with numerous results. They either end up with people being desperate and giving up or finding solutions in ABAP. However, my team has no access to ABAP since SAP-programming has all been outsourced to India. Getting any changes done in ABAP will be a long and tedious progress for which we simply do not have the time.
Is there anyway to resolve this issue on our side? Maybe through other RFCs or changes in how we handle the BAPI? I am quite desperate as this problem occurred shortly before we wanted to go live and now it is not sure we can even do anything on our side.

Hi Tom,
If you want to call DEQUEUE_ALL from vb.net then tell your ABAP counterpart to create a new remote enabled function module and he can subsequently make a call to DEQUEUE_ALL in the custom developed function module through ABAP. You can then call the newly created custom function module using its calling parameter.
Also, if required he can expose that newly custom created function module as a webservice that you can call from vb.net.
I hope its clear to you now about how can you access it from vb.net.
Regards,
Sachin

Serious performance issue with LV 7.1 Development Environment

I'm posting this issue to the forums prior to submitting a bug report to ensure that the problems I'm having are reproducible. To reproduce this bug, you're going to have to be an advanced user with a large project (hundreds to thousands of VIs) as the performance problem is related to the number of VIs loaded.
The issue is the increasingly poor performance of the LabVIEW 7.1 Development Environment as the number of VIs in memory increases. The actions affected include switching between front panel and diagram, saving a VI, copy and paste, clicking a menu, and the mysterious time spent (compiling? editing the runtime menu? changing the toolbar state?) between pressing the run button and when the code actually starts executing. Scrolling and, interestingly, copying via a control-drag are not affected. Running time of entirely on-diagram code does not seem to be affected.
These problems are quite severe and significantly decrease my productivity as a programmer. Since they are development environment UI issues, it's been difficult for me to find a good example VI; the best I can do is the attached "LV Speed Test.vi". It doesn't test the issues that affect me most, but it seems to suffer from the same problem.
This simple VI just shows and hides the menu bar 100 times in a tight for loop. When it is the only VI loaded, it executes in about 350 msec on my machine. (2.4 GHz P-IV/640 MB RAM/Win2k). However, when I load a single project-encompassing VI (let's call it the "giant") that references a total of about 900 user and VI-lib subVIs, the test routine takes almost a minute and half to run...about 240 times slower! I've tried this on my laptop with similar results.
The problem appears to be related to the *number* of VIs loaded and not the memory utilization. For example, if I close the "giant", and create a new VI ("memhog") that does nothing but initialize a length 20,000,000 array of doubles and stores it in an uninitialized shift register, LabView's overall memory usage (as shown in the task manager) jumps enormously, but LV Speed Test executes in about 450 msec...only slightly slower than with a fresh copy of Labview.
The problem seems to be related to excessive context switching. The Windows task manager shows over a thirteen hundred page faults occur when "LV Speed Test" is run with the "giant" in the background, versus zero or none when run by itself or when "memhog" has used up 160+MB of space.
The problem only seems to affect the frontmost window. (Unfortunately, that's where we LV programmers spend all of our time!) If you start "LV Speed Test" and then put "giant" in the foreground "LV Speed Test" runs much faster. In fact, if you use the VI server to put the "giant" VI in the foreground programmatically at the start of "LV Speed Test", execution time drops back to 450 msec, and there are no page faults!
These results show the issue is not related to video drivers or the Windows virtual memory system. My suspicion is that there is a faulty routine in LV 7.1 that is traversing the entire VI hierarchy every time certain events are thrown in the foreground window. It could be due to a problem with the Windows event tracking system, but this seems less likely.
I have been programming LV for about 7 years and switched from LV 6.1 to 7.1 about four months ago. I know NI engineers have put thousands of hours developing and testing LV 7.1, but honestly I find myself wishing I had never upgraded from using LV 6.1. (To whomever thought "hide trailing zeros" should be the default for floating point controls...what were you thinking?!)
I know each new version of LabView causes old-timers like me to grouse that things were better back in the days when we etched our block diagrams on stone tablets, etc., and honestly I'm not going to go back. I am committed to LabView 7.1. I just wish it were not so slow on my big projects!
Attachments:
LV_Speed_Test.vi ‏22 KB

Hi,
I can confirm this behavior. Setting the execution system to "user
interface" helps a bit, but there is still a big difference.
I get a feeling it has something to do with window messages, perhaps
WM_PAINT or something, that is handled differently if a VI is not
frontmost... But what do I know...
Don't know if it should be called a bug, but it sure is something that could
be optimized.
Regards,
Wiebe.
"Rob Calhoun" wrote in message
news:[email protected]...
> I'm posting this issue to the forums prior to submitting a bug report
> to ensure that the problems I'm having are reproducible. To reproduce
> this bug, you're going to have to be an advanced user with a large
> project (hundreds to thousands of VIs) as the performance problem is
> related to the number of VIs loaded.
>
> The issue is the increasingly poor performance of the LabVIEW 7.1
> Development Environment as the number of VIs in memory increases. The
> actions affected include switching between front panel and diagram,
> saving a VI, copy and paste, clicking a menu, and the mysterious time
> spent (compiling? editing the runtime menu? changing the toolbar
> state?) between pressing the run button and when the code actually
> starts executing. Scrolling and, interestingly, copying via a
> control-drag are not affected. Running time of entirely on-diagram
> code does not seem to be affected.
>
> These problems are quite severe and significantly decrease my
> productivity as a programmer. Since they are development environment
> UI issues, it's been difficult for me to find a good example VI; the
> best I can do is the attached "LV Speed Test.vi". It doesn't test the
> issues that affect me most, but it seems to suffer from the same
> problem.
>
> This simple VI just shows and hides the menu bar 100 times in a tight
> for loop. When it is the only VI loaded, it executes in about 350 msec
> on my machine. (2.4 GHz P-IV/640 MB RAM/Win2k). However, when I load a
> single project-encompassing VI (let's call it the "giant") that
> references a total of about 900 user and VI-lib subVIs, the test
> routine takes almost a minute and half to run...about 240 times
> slower! I've tried this on my laptop with similar results.
>
> The problem appears to be related to the *number* of VIs loaded and
> not the memory utilization. For example, if I close the "giant", and
> create a new VI ("memhog") that does nothing but initialize a length
> 20,000,000 array of doubles and stores it in an uninitialized shift
> register, LabView's overall memory usage (as shown in the task
> manager) jumps enormously, but LV Speed Test executes in about 450
> msec...only slightly slower than with a fresh copy of Labview.
>
> The problem seems to be related to excessive context switching. The
> Windows task manager shows over a thirteen hundred page faults occur
> when "LV Speed Test" is run with the "giant" in the background, versus
> zero or none when run by itself or when "memhog" has used up 160+MB of
> space.
>
> The problem only seems to affect the frontmost window. (Unfortunately,
> that's where we LV programmers spend all of our time!) If you start
> "LV Speed Test" and then put "giant" in the foreground "LV Speed Test"
> runs much faster. In fact, if you use the VI server to put the "giant"
> VI in the foreground programmatically at the start of "LV Speed Test",
> execution time drops back to 450 msec, and there are no page faults!
>
> These results show the issue is not related to video drivers or the
> Windows virtual memory system. My suspicion is that there is a faulty
> routine in LV 7.1 that is traversing the entire VI hierarchy every
> time certain events are thrown in the foreground window. It could be
> due to a problem with the Windows event tracking system, but this
> seems less likely.
>
> I have been programming LV for about 7 years and switched from LV 6.1
> to 7.1 about four months ago. I know NI engineers have put thousands
> of hours developing and testing LV 7.1, but honestly I find myself
> wishing I had never upgraded from using LV 6.1. (To whomever thought
> "hide trailing zeros" should be the default for floating point
> controls...what were you thinking?!)
>
> I know each new version of LabView causes old-timers like me to grouse
> that things were better back in the days when we etched our block
> diagrams on stone tablets, etc., and honestly I'm not going to go
> back. I am committed to LabView 7.1. I just wish it were not so slow
> on my big projects!

Serious locking issues with Main Stage 3

Similar Messages

Maybe you are looking for