MSI DR8-A: "Could not perform end of Disc-at-Once"

I'm using Nero Burning ROM 6; writing a data DVD to Memorex 4x DVD+R Media.
I receive the following errors at the end of the burn process:
Invalid Field in Command
Could not perform end of Disc-at-Once
Nero doesn't seem to allow me to change the write method to something other than Disc-at-Once.
Device Manager shows: "ATAPI DVD RW 8XMax"
Had no trouble using HD-BURN with my Memorex CD-R's
Any suggestions?

the link you provided lists the DR8-A as a "supported" drive... it's the 4th one from the top... DVD+/-R/RW8XMAX
and i've had no problem burning CD-R's with my MSI drive... i've come to the theory that i'm having issues burning to DVD+Rs because I'm using Memorex DVD+Rs... which are not on MSI's list of supported media for the DR8-A... I've got some Ritek discs on order, and will report back my findings when they arrive.
I'm also going to download the most recent updates for Nero 6 for shits and giggles.
My current version of Nero is 6.0.0.0, and the most recent update is version 6.3.1.6
also, in my first post, i said that i had no problems burning to Memorex CD-Rs... but they are actually Maxell CD-Rs...

Similar Messages

  • Win 8.1 sfc /scannow returns Windows Resource Protection could not perform the requested operation.

    I am running Windows 8.1 Pro.
    I have been experiencing problems that lead me to believe the my component store is corrupted.
    When I run sfc /scannow sfc immediately comes back with "Windows Resource Protection could not perform the required operation.
    Here are the entries in the CBS file
     TI: --- Initializing Trusted Installer ---
    2014-01-21 10:45:59, Info                  CBS    TI: Last boot time: 2014-01-21 10:28:05.492
    2014-01-21 10:45:59, Info                  CBS    Starting TrustedInstaller initialization.
    2014-01-21 10:45:59, Info                  CBS    Ending TrustedInstaller initialization.
    2014-01-21 10:45:59, Info                  CBS    Starting the TrustedInstaller main loop.
    2014-01-21 10:45:59, Info                  CBS    TrustedInstaller service starts successfully.
    2014-01-21 10:45:59, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart
    2014-01-21 10:45:59, Info                  CBS    Startup processing thread terminated normally
    2014-01-21 10:45:59, Info                  CBS    Starting TiWorker initialization.
    2014-01-21 10:45:59, Info                  CBS    Ending TiWorker initialization.
    2014-01-21 10:45:59, Info                  CBS    Starting the TiWorker main loop.
    2014-01-21 10:45:59, Info                  CBS    TiWorker starts successfully.
    2014-01-21 10:45:59, Info                  CBS    TiWorker: Client requests SFP repair object.
    2014-01-21 10:45:59, Info                  CBS    Universal Time is: 2014-01-21 16:45:59.014
    2014-01-21 10:45:59, Info                  CBS    Open of SC_BOOT_SERVICING_DONE event failed 2
    2014-01-21 10:45:59, Info                  CBS    Loaded Servicing Stack v6.3.9600.16470 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.16470_none_fa2491fd9b3cfcb2\cbscore.dll
    2014-01-21 10:45:59, Info                  CSI   
    00000001@2014/1/21:16:45:59.016 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffa54fd5929 @0x7ffa55266bda @0x7ffa55269a06 @0x7ff74300d25f @0x7ff74300dc17 @0x7ffa800d2385)
    2014-01-21 10:45:59, Info                  CBS    SQM: Initializing online with Windows opt-in: False
    2014-01-21 10:45:59, Info                  CBS    SQM: Cleaning up report files older than 10 days.
    2014-01-21 10:45:59, Info                  CBS    SQM: Requesting upload of all unsent reports.
    2014-01-21 10:45:59, Info                  CBS    SQM: Failed to start upload with file pattern: C:\WINDOWS\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005
    - E_FAIL]
    2014-01-21 10:45:59, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
    2014-01-21 10:45:59, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\WINDOWS\servicing\sqm\*_all.sqm, flags: 0x6
    2014-01-21 10:45:59, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
    2014-01-21 10:45:59, Info                  CBS    NonStart: Set pending store consistency check.
    2014-01-21 10:45:59, Info                  CSI   
    00000002@2014/1/21:16:45:59.020 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffa54fd5929 @0x7ffa652e7fc0 @0x7ffa652e80f2 @0x7ff74300c9a5 @0x7ff74300dc2e @0x7ffa800d2385)
    2014-01-21 10:45:59, Info                  CSI    00000003 No store version format found; DLL store format 0.0.0.6
    2014-01-21 10:45:59, Error                 CSI   
    00000004@2014/1/21:16:45:59.027 (F) base\wcp\componentstore\storelayout.cpp(3854): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function ComponentStore::CRawStoreLayout::OpenCanonicalDataKey expression:
    (null)
    [gle=0x80004005]
    2014-01-21 10:45:59, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.
    2014-01-21 10:45:59, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20140121102547.cab to WER report.
    2014-01-21 10:45:59, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20140114224141.cab to WER report.
    2014-01-21 10:45:59, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20140104132548.cab to WER report.
    2014-01-21 10:45:59, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20131220204514.cab to WER report.
    2014-01-21 10:45:59, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20131215075547.cab to WER report.
    2014-01-21 10:45:59, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
    2014-01-21 10:45:59, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2014-01-21 10:45:59, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2014-01-21 10:45:59, Info                  CBS    Failed to get CSI system store [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
    2014-01-21 10:45:59, Info                  CBS    CSI store consistency check fails. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
    2014-01-21 10:45:59, Info                  CBS    Failed to load component store [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
    2014-01-21 10:45:59, Info                  CSI    00000005 No store version format found; DLL store format 0.0.0.6
    2014-01-21 10:45:59, Error                 CSI   
    00000006@2014/1/21:16:45:59.051 (F) base\wcp\componentstore\storelayout.cpp(3854): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function ComponentStore::CRawStoreLayout::OpenCanonicalDataKey expression:
    (null)
    [gle=0x80004005]
    2014-01-21 10:45:59, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.
    2014-01-21 10:45:59, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20140121102547.cab to WER report.
    2014-01-21 10:45:59, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20140114224141.cab to WER report.
    2014-01-21 10:45:59, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20140104132548.cab to WER report.
    2014-01-21 10:45:59, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20131220204514.cab to WER report.
    2014-01-21 10:45:59, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20131215075547.cab to WER report.
    2014-01-21 10:45:59, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
    2014-01-21 10:45:59, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2014-01-21 10:45:59, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2014-01-21 10:47:59, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
    2014-01-21 10:47:59, Info                  CBS    TiWorker signaled for shutdown, going to exit.
    2014-01-21 10:47:59, Info                  CBS    Ending the TiWorker main loop.
    2014-01-21 10:47:59, Info                  CBS    Ending the TrustedInstaller main loop.
    2014-01-21 10:47:59, Info                  CBS    Starting TiWorker finalization.
    2014-01-21 10:47:59, Info                  CBS    Starting TrustedInstaller finalization.
    2014-01-21 10:47:59, Info                  CBS    Ending TrustedInstaller finalization.
    2014-01-21 10:47:59, Info                  CBS    Ending TiWorker finalization.
    Is there a way to rebuild the component store?
    Thanks,
    Glen

    Hey Glen,
    This log shows the exact same error that is mentioned in the comments of
    this blog post, and the response is:
    joscon [Microsoft]
    joscon [Microsoft]
    Thanks.  Unfortunately, this isn't good news.  The CanonicalData key is missing.
    2013-08-05 11:08:32, Error                 CSI    00000004@2013/8/5:09:08:32.471 (F) base\wcp\componentstore\storelayout.cpp(3617): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function ComponentStore::CRawStoreLayout::OpenCanonicalDataKey
    expression: (null)
    [gle=0x80004005]
    Unfortunately, its a small, but unrecreatable subset of data.  If this is missing, servicing is broken on the machine and the system will need to be restored from backup or PBR.
    So you will need to try a refresh or a re-install of Windows, unfortunately.
    Hope this helps,
    David
    Windows Outreach Team - IT Pro
    The Springboard Series on TechNet

  • Windows Resource Protection could not perform the requested operation.

    A close friend's machine was blue screening on boot so he had me take a look at it.  The error in the BSOD indicated Windows was having trouble reading from the drive.  Although the drive wasn't clicking, based on what I was seeing, it seemed pretty
    clear the drive was on its way out.  I ran chkdsk, several times, and it found plenty of bad sectors but wasn't able to really fix anything.  Fortunately I was able to
    clone the drive using gparted
    run chkdsk
    fix the master boot record, boot sector and boot configuration data store
    run chkdsk again
    Now all is well
    Upon booting I noticed the system was dreadfully out of date: Firefox, Java, Reader, Flash - the works - so I updated all that.  I also noticed it was missing something like 50-70  Windows updates so I had to straight that right away.  It
    managed to install 15-20 before failing with 80070057.  This to me isn't too uncommon so I rebooted thinking it wouldn't choke next time. Much to my chagrin, any subsequent attempts fail with error 80070057.  I even tried installing just a few updates
    at a time, even just 1, and the error persists.  My assumption is that one or more files are maybe damaged and need to be fixed.
    I ran sfc /scannow and it gets to about 27%, then fails with "Windows Resource Protection could not perform the requested operation."  I did the following:
    backed up the existing CBS log
    ran sfc /scannow again
    watched the log in powershell via Get-Content C:\Windows\Logs\CBS\CBS.log -Wait
    It started out strong
    PS C:\Windows\Logs\CBS> Get-Content C:\Windows\Logs\CBS\CBS.log -Wait
    2014-03-06 18:48:33, Info CBS Loaded Servicing Stack v6.0.6002.18005 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6
    002.18005_none_676975d87cc9b6e6\cbscore.dll
    2014-03-06 18:48:33, Info CSI 00000001@2014/3/6:23:48:33.027 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7fef0cf8c85 @0x7feff3f53ae @0x7feff3c3ed1
    @0xffa949a8 @0xffa930c9 @0xffa93578)
    2014-03-06 18:48:33, Info CSI 00000002@2014/3/6:23:48:33.045 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7fef0cf8c85 @0x7feff4386cf @0x7feff4125d9
    @0x7feff3c3feb @0xffa949a8 @0xffa930c9)
    2014-03-06 18:48:33, Info CSI 00000003@2014/3/6:23:48:33.048 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7fef0cf8c85 @0x7feff21838d @0x7feff2184ba
    @0xffa94207 @0xffa93125 @0xffa93578)
    2014-03-06 18:48:33, Info CBS NonStart: Checking to ensure startup processing was not required.
    2014-03-06 18:48:33, Info CSI 00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDispo
    sition = @0xb8fad0
    2014-03-06 18:48:33, Info CBS NonStart: Success, startup processing not required as expected.
    2014-03-06 18:48:33, Info CSI 00000005 CSI Store 4751600 (0x00000000004880f0) initialized
    2014-03-06 18:48:38, Info CSI 00000006 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:38, Info CSI 00000007 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:39, Info CSI 00000008 Repair results created:
    POQ 0 starts:
    POQ 0 ends.
    2014-03-06 18:48:39, Info CSI 00000009 [SR] Verify complete
    2014-03-06 18:48:39, Info CSI 0000000a [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:39, Info CSI 0000000b [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:40, Info CSI 0000000c Repair results created:
    POQ 1 starts:
    POQ 1 ends.
    2014-03-06 18:48:40, Info CSI 0000000d [SR] Verify complete
    2014-03-06 18:48:40, Info CSI 0000000e [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:40, Info CSI 0000000f [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:41, Info CSI 00000010 Repair results created:
    POQ 2 starts:
    POQ 2 ends.
    2014-03-06 18:48:41, Info CSI 00000011 [SR] Verify complete
    2014-03-06 18:48:41, Info CSI 00000012 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:41, Info CSI 00000013 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:41, Info CSI 00000014 Repair results created:
    POQ 3 starts:..... and so on
    Until it hit a problem
    POQ 34 ends.
    2014-03-06 18:49:08, Info CSI 00000091 [SR] Verify complete
    2014-03-06 18:49:08, Info CSI 00000092 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:49:08, Info CSI 00000093 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:49:09, Info CSI 00000094 Repair results created:
    POQ 35 starts:
    POQ 35 ends.
    2014-03-06 18:49:09, Info CSI 00000095 [SR] Verify complete
    2014-03-06 18:49:09, Info CSI 00000096 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:49:09, Info CSI 00000097 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:49:10, Info CSI 00000098 Repair results created:
    POQ 36 starts:
    POQ 36 ends.
    2014-03-06 18:49:10, Info CSI 00000099 [SR] Verify complete
    2014-03-06 18:49:11, Info CSI 0000009a [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:49:11, Info CSI 0000009b [SR] Beginning Verify and Repair transaction
    2014-03-06 18:49:12, Error CSI 0000009c@2014/3/6:23:49:12.802 (F) d:\longhorn\base\wcp\primitiveinstallers\filehierarchy.cpp(1939): Error STATUS_INVALID_PARAMETER originated in fun
    ction FileInstaller::CFileInstallerHierarchy::PortFileInformationBetweenCdfs expression: TmpBlob.Length == sizeof(LUACDF_FILE_ENTRY)
    [gle=0x80004005]
    2014-03-06 18:49:16, Error CSI 0000009d (F) STATUS_INVALID_PARAMETER #2119209# from CFileInstaller::CommitChanges(...)[gle=0xd000000d]
    2014-03-06 18:49:16, Error CSI 0000009e (F) STATUS_INVALID_PARAMETER #2119208# from PrimitiveInstaller::CCoordinator::FinalizeChanges(...)[gle=0xd000000d]
    2014-03-06 18:58:33, Info CBS Scavenge: Package store indicates there is no component to scavenge, skipping.
    I searched for "[SR]" but I didn't see anything of great interest
    C:\Windows\system32>findstr /c:"[SR]" %windir%\logs\cbs\cbs.log
    2014-03-06 18:48:38, Info CSI 00000006 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:38, Info CSI 00000007 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:39, Info CSI 00000009 [SR] Verify complete
    2014-03-06 18:48:39, Info CSI 0000000a [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:39, Info CSI 0000000b [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:40, Info CSI 0000000d [SR] Verify complete
    2014-03-06 18:48:40, Info CSI 0000000e [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:40, Info CSI 0000000f [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:41, Info CSI 00000011 [SR] Verify complete
    2014-03-06 18:48:41, Info CSI 00000012 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:41, Info CSI 00000013 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:41, Info CSI 00000015 [SR] Verify complete
    2014-03-06 18:48:42, Info CSI 00000016 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:42, Info CSI 00000017 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:42, Info CSI 00000019 [SR] Verify complete
    2014-03-06 18:48:42, Info CSI 0000001a [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:42, Info CSI 0000001b [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:44, Info CSI 0000001d [SR] Verify complete
    2014-03-06 18:48:44, Info CSI 0000001e [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:44, Info CSI 0000001f [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:45, Info CSI 00000021 [SR] Verify complete
    2014-03-06 18:48:45, Info CSI 00000022 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:45, Info CSI 00000023 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:45, Info CSI 00000025 [SR] Verify complete
    2014-03-06 18:48:46, Info CSI 00000026 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:46, Info CSI 00000027 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:46, Info CSI 00000029 [SR] Verify complete
    2014-03-06 18:48:47, Info CSI 0000002a [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:47, Info CSI 0000002b [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:47, Info CSI 0000002d [SR] Verify complete
    2014-03-06 18:48:48, Info CSI 0000002e [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:48, Info CSI 0000002f [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:48, Info CSI 00000031 [SR] Verify complete
    2014-03-06 18:48:48, Info CSI 00000032 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:48, Info CSI 00000033 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:49, Info CSI 00000035 [SR] Verify complete
    2014-03-06 18:48:49, Info CSI 00000036 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:49, Info CSI 00000037 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:50, Info CSI 00000039 [SR] Verify complete
    2014-03-06 18:48:50, Info CSI 0000003a [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:50, Info CSI 0000003b [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:50, Info CSI 0000003d [SR] Verify complete
    2014-03-06 18:48:51, Info CSI 0000003e [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:51, Info CSI 0000003f [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:51, Info CSI 00000041 [SR] Verify complete
    2014-03-06 18:48:51, Info CSI 00000042 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:51, Info CSI 00000043 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:52, Info CSI 00000045 [SR] Verify complete
    2014-03-06 18:48:52, Info CSI 00000046 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:52, Info CSI 00000047 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:52, Info CSI 00000049 [SR] Verify complete
    2014-03-06 18:48:53, Info CSI 0000004a [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:53, Info CSI 0000004b [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:53, Info CSI 0000004d [SR] Verify complete
    2014-03-06 18:48:54, Info CSI 0000004e [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:54, Info CSI 0000004f [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:54, Info CSI 00000051 [SR] Verify complete
    2014-03-06 18:48:54, Info CSI 00000052 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:54, Info CSI 00000053 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:55, Info CSI 00000055 [SR] Verify complete
    2014-03-06 18:48:55, Info CSI 00000056 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:55, Info CSI 00000057 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:55, Info CSI 00000059 [SR] Verify complete
    2014-03-06 18:48:56, Info CSI 0000005a [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:56, Info CSI 0000005b [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:56, Info CSI 0000005d [SR] Verify complete
    2014-03-06 18:48:56, Info CSI 0000005e [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:56, Info CSI 0000005f [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:57, Info CSI 00000061 [SR] Verify complete
    2014-03-06 18:48:57, Info CSI 00000062 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:57, Info CSI 00000063 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:48:58, Info CSI 00000065 [SR] Verify complete
    2014-03-06 18:48:58, Info CSI 00000066 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:48:58, Info CSI 00000067 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:49:00, Info CSI 00000069 [SR] Verify complete
    2014-03-06 18:49:00, Info CSI 0000006a [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:49:00, Info CSI 0000006b [SR] Beginning Verify and Repair transaction
    2014-03-06 18:49:00, Info CSI 0000006d [SR] Verify complete
    2014-03-06 18:49:01, Info CSI 0000006e [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:49:01, Info CSI 0000006f [SR] Beginning Verify and Repair transaction
    2014-03-06 18:49:01, Info CSI 00000071 [SR] Verify complete
    2014-03-06 18:49:02, Info CSI 00000072 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:49:02, Info CSI 00000073 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:49:02, Info CSI 00000075 [SR] Verify complete
    2014-03-06 18:49:02, Info CSI 00000076 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:49:02, Info CSI 00000077 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:49:03, Info CSI 00000079 [SR] Verify complete
    2014-03-06 18:49:03, Info CSI 0000007a [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:49:03, Info CSI 0000007b [SR] Beginning Verify and Repair transaction
    2014-03-06 18:49:04, Info CSI 0000007d [SR] Verify complete
    2014-03-06 18:49:04, Info CSI 0000007e [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:49:04, Info CSI 0000007f [SR] Beginning Verify and Repair transaction
    2014-03-06 18:49:05, Info CSI 00000081 [SR] Verify complete
    2014-03-06 18:49:05, Info CSI 00000082 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:49:05, Info CSI 00000083 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:49:06, Info CSI 00000085 [SR] Verify complete
    2014-03-06 18:49:06, Info CSI 00000086 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:49:06, Info CSI 00000087 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:49:06, Info CSI 00000089 [SR] Verify complete
    2014-03-06 18:49:07, Info CSI 0000008a [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:49:07, Info CSI 0000008b [SR] Beginning Verify and Repair transaction
    2014-03-06 18:49:07, Info CSI 0000008d [SR] Verify complete
    2014-03-06 18:49:08, Info CSI 0000008e [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:49:08, Info CSI 0000008f [SR] Beginning Verify and Repair transaction
    2014-03-06 18:49:08, Info CSI 00000091 [SR] Verify complete
    2014-03-06 18:49:08, Info CSI 00000092 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:49:08, Info CSI 00000093 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:49:09, Info CSI 00000095 [SR] Verify complete
    2014-03-06 18:49:09, Info CSI 00000096 [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:49:09, Info CSI 00000097 [SR] Beginning Verify and Repair transaction
    2014-03-06 18:49:10, Info CSI 00000099 [SR] Verify complete
    2014-03-06 18:49:11, Info CSI 0000009a [SR] Verifying 100 (0x0000000000000064) components
    2014-03-06 18:49:11, Info CSI 0000009b [SR] Beginning Verify and Repair transaction
    C:\Windows\system32>
    I've run into sfc issues in the past, and in one instance, booting the OS install DVD, and running sfc /scannow /offbootdir=c:\ /offwindir=c:\windows did fix the issue.  But I have to ask
    Is there no way to do that while in Windows?  Can't I mount some WIM and do it that way instead of booting the DVD?
    Is that the right course of action, or is/are there some other options I should explore?
    Thanks for your time & guidance.

    Hi,
    In my opinion, if you want  SFC to use a sourcepath to repair your system, you can just use in-place upgrade to do this:
    How to Perform an In-Place Upgrade on Windows Vista, Windows 7, Windows Server 2008 & Windows Server 2008 R2
    http://support.microsoft.com/kb/2255099
    If you have any feedback on our support, please click
    here
    Alex Zhao
    TechNet Community Support
    Thanks for taking the time to reply and for this suggestion.
    The in-place upgrade is a wonderful potential solution, but the process requires the source media.  Most systems these days don't include the OS or recovery CD's because the manufacturers want you to pay for them.  And most consumers aren't spending
    the $50-$70 dollars to get the media, which complicates things in situations like this.  So while they've purchased a machine and have a valid Microsoft COA sticker on the box, they can't do anything.
    Also, to make matters worse, I posted this in the wrong forum as this is a Vista Home Premium PC.  [My sincere apologies for that. Mods please feel free to move/reclassify]  I do have a Vista Home Premium DVD, but its the 32-bit version, not 64-bit,
    which is what this system is.  So unless I can locate a Visa Home Premium 64-bit DVD, or they upgrade to Windows 7 or 8 (which they probably should do anyway), we're sunk.

  • Weblogic upgrade 9.2 - 10.2: Could not perform unpadding: invalid pad byte

    While upgrading a domain from 9.2 to 10.2, I get the following error on running upgrade.sh:
    -bash-3.00$ ./upgrade.sh
    Warning: Cannot convert string "-monotype-arial-regular-r-normal--*-140-*-*-p-*-iso8859-1" to type FontStruct
    Calling Wizard framework for upgrade: args2: [-mode=gui, -file=wcf/plugin_gui_wizard.xml, -log=/app/bea/bea_10.2/user_projects/upgrade_logs/domain_04292008_152323_1, -p:plugin:plugin.executionPlan.file=resources/portal-upgrade.xml, -p:plugin:I18N_PLUGIN=weblogic/upgrade/i18n_upgrade, -p:plugin:TARGET_VERSION=10.0.1.0]
    weblogic.upgrade.domain.directoryselection.DomainDirectorySelectionPlugIn.validatePlatformDomain: Property set to skip platform domain validation. Skipping...
    <apr 29, 2008 3:23:56 PM CEST> <INFO> <Upgrade> <BEA-800000> <If not present, set the source WebLogic Configuration to:9.0>
    <apr 29, 2008 3:23:56 PM CEST> <INFO> <Upgrade> <BEA-800000> <If not present, set the source WebLogic Configuration to:9.0>
    <apr 29, 2008 3:23:56 PM CEST> <INFO> <Upgrade> <BEA-800000> <Domain directory selected: /app/bea_domains/portal>
    <apr 29, 2008 3:23:56 PM CEST> <INFO> <Upgrade> <BEA-800000> <Domain directory selected: /app/bea_domains/portal>
    <apr 29, 2008 3:24:16 PM CEST> <FATAL> <Upgrade> <BEA-800000> <Execute Exception ... weblogic.descriptor.DescriptorException: Unmarshaller failed>
    com.bea.plateng.plugin.PlugInException: Execute Exception ... weblogic.descriptor.DescriptorException: Unmarshaller failed
    at weblogic.upgrade.domain.directoryselection.DomainDirectorySelectionPlugIn.execute(DomainDirectorySelectionPlugIn.java:261)
    at com.bea.plateng.wizard.plugin.silent.tasks.ExecutePlugInTask.execute(ExecutePlugInTask.java:76)
    at com.bea.plateng.wizard.silent.tasks.AbstractSilentTask.run(AbstractSilentTask.java:28)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: weblogic.descriptor.DescriptorException: Unmarshaller failed
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
    at weblogic.management.provider.internal.DescriptorManagerHelper.loadDescriptor(DescriptorManagerHelper.java:58)
    at weblogic.upgrade.domain.directoryselection.DomainDirectorySelectionPlugIn.parseNewStyleConfig(DomainDirectorySelectionPlugIn.java:416)
    at weblogic.upgrade.domain.directoryselection.DomainDirectorySelectionPlugIn.execute(DomainDirectorySelectionPlugIn.java:226)
    ... 3 more
    Caused by: com.bea.xml.XmlException: weblogic.management.ManagementRuntimeException: weblogic.descriptor.DescriptorException: Unmarshaller failed: com.bea.xml.XmlException: java.lang.AssertionError: java.lang.reflect.InvocationTargetException
    at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:54)
    at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:483)
    Caused by: weblogic.security.internal.encryption.EncryptionServiceException: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
    at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:78)
    at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:94)
    at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:87)
    ... 55 more
    Caused by: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
    at com.rsa.jsafe.JA_PKCS5Padding.a(Unknown Source)
    at com.rsa.jsafe.JG_BlockCipher.decryptFinal(Unknown Source)
    at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:68)
    ... 57 more
    Before running upgrade.sh, all applications were undeployed from the domain and I've verified that config.xml is valid with no refs to previously installed apps.
    I've also removed refs to custom security providers in config.xml, but stil the same.
    Can anyone please help?
    Edited by mirzaei at 04/29/2008 7:18 AM

    Fixed.
    The xml-file for one of the jdbc-resources defined in config.xml was missing from DOMAIN_HOME/conf/jdbc. Adding the file fixed the problem.
    Edited by mirzaei at 04/29/2008 11:07 AM

  • Printed page could not be ended

    Hi all
    A client just had this issue
    She just created a AR invoice and it gave me a message u2026u2026. Printed page could not be ended.
    She went back to see if it was added and now there are 2 invoice nou2019s are 502780 and 502781?
    and its exactly the same..the customer, items, total,s etc.
    It seems very strange.
    I didn't see anything on the forums thats exactly like that
    Any help will be appreciated.
    Thanks
    Jerusha

    Hi guys,
    I am helping Jerusha at this client, maybe I can give some extra info which may help.
    The add-on in question does not affect the sales invoice in any way, so I doubt it is that.
    It is set to automatic printing for A/R Invoices in the Print Preferences, could it be something to do with that?
    Thanks
    Best Regards

  • Page could not be ended error

    Good afternoon. Iu2019ve got a user that gets the following error when he tries to print both an invoice and quote. u201CPage could not be ended.u201D
    Unfortunately there is no error code or number at the end of the message.
    Iu2019ve asked him to reboot his own PC but with no success.
    The user connects to the SAP server remotely, and the printer is locally connected to the PC.
    Any assistance or help will be appreciated.
    Thanks
    Regards

    Hi,
    You can check the Note No. : 1438804 and see whether the scenario is same or not.
    Also, you can check the following thread :
    The printed page could not be ended
    Kind Regards,
    Jitin
    SAP Business One Forum Team

  • The printed page could not be ended

    One of our customers are running 8.8 PL06. When a user try to print multiple checks at once, they get The printed page could not be ended. If they print one at a time it works fine. I looked into forum and help but no luck. Is it a bug on this patch? If so, i can advise customer to upgrade to 8.81. Please advise.

    How,
    It could be due to bug. However, first make sure the page setting is correct.
    Thanks,
    Gordon

  • ERROR com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.

              Hi,
              I am trying to setup cluster environment with weblogic7.0. I have two managed
              servers in my cluster. The first one I am able start without any problem(The first
              server and admin is on the same UNIX m/c). When I am trying to start the second
              server from different m/c(this is another UNIX m/c) it is giving the following
              error. I am not using default security realm.
              If anybody come across this error before,please reply me.
              Thanks
              Venkat
              com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad
              byte.
              at com.rsa.jsafe.JA_PKCS5Padding.performUnpadding(JA_PKCS5Padding.java:111)
              at com.rsa.jsafe.JG_BlockCipher.decryptFinal(JG_BlockCipher.java:1092)
              at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:67)
              at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:93)
              at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:53)
              at weblogic.management.commo.CommoModelMBean.getAttribute(CommoModelMBean.java:319)
              at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1183)
              at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
              at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:844)
              at weblogic.management.commo.CommoProxy.invoke(CommoProxy.java:330)
              at $Proxy42.getCredential(Unknown Source)
              at weblogic.security.providers.authentication.LDAPAtnDelegate.<init>(LDAPAtnDelegate.java:452)
              at weblogic.security.providers.authentication.LDAPAuthenticationProviderImpl.initialize(LDAPAuthenticationProviderImpl.java:67)
              at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:1820)
              at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:151)
              at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              at weblogic.Server.main(Server.java:32)
              --------------- nested within: ------------------
              weblogic.security.internal.encryption.EncryptionServiceException - with nested
              exception:
              [com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad
              byte.]
              at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:77)
              at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:93)
              at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:53)
              at weblogic.management.commo.CommoModelMBean.getAttribute(CommoModelMBean.java:319)
              at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1183)
              at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
              at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:844)
              at weblogic.management.commo.CommoProxy.invoke(CommoProxy.java:330)
              at $Proxy42.getCredential(Unknown Source)
              at weblogic.security.providers.authentication.LDAPAtnDelegate.<init>(LDAPAtnDelegate.java:452)
              at weblogic.security.providers.authentication.LDAPAuthenticationProviderImpl.initialize(LDAPAuthenticationProviderImpl.java:67)
              at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:1820)
              at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:151)
              at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              at weblogic.Server.main(Server.java:32)
              --------------- nested within: ------------------
              javax.management.RuntimeOperationsException: RuntimeException thrown by the getAttribute
              method of the DynamicMBean for the attribute Credential
              at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1185)
              at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
              at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:844)
              at weblogic.management.commo.CommoProxy.invoke(CommoProxy.java:330)
              at $Proxy42.getCredential(Unknown Source)
              at weblogic.security.providers.authentication.LDAPAtnDelegate.<init>(LDAPAtnDelegate.java:452)
              at weblogic.security.providers.authentication.LDAPAuthenticationProviderImpl.initialize(LDAPAuthenticationProviderImpl.java:67)
              at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:1820)
              at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:151)
              at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              at weblogic.Server.main(Server.java:32)
              <Dec 7, 2002 8:57:33 PM EST> <Critical> <WebLogicServer> <000364> <Server failed
              during initialization. Exception:weblogic.security.service.SecurityServiceRuntimeException:
              Problem instantiating Authentication Providerjavax.management.RuntimeOperationsException:
              RuntimeException thrown by the getAttribute method of the DynamicMBean for the
              attribute Credential
              weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
              Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
              thrown by the getAttribute method of the DynamicMBean for the attribute Credential
              at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:198)
              at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              at weblogic.Server.main(Server.java:32)
              >
              <Dec 7, 2002 8:57:33 PM EST> <Emergency> <WebLogicServer> <000342> <Unable to
              initialize the server: Fatal initialization exception
              Throwable: weblogic.security.service.SecurityServiceRuntimeException: Problem
              instantiating Authentication Providerjavax.management.RuntimeOperationsException:
              RuntimeException thrown by the getAttribute method of the DynamicMBean for the
              attribute Credential
              weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
              Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
              thrown by the getAttribute method of the DynamicMBean for the attribute Credential
              at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:198)
              at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              at weblogic.Server.main(Server.java:32)
              >
              The WebLogic Server did not start up properly.
              Exception raised:
              weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
              Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
              thrown by the getAttribute method of the DynamicMBean for the attribute Credential
              at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:198)
              at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              at weblogic.Server.main(Server.java:32)
              Reason: Fatal initialization exception
              Throwable: weblogic.security.service.SecurityServiceRuntimeException: Problem
              instantiating Authentication Providerjavax.management.RuntimeOperationsException:
              RuntimeException thrown by the getAttribute method of the DynamicMBean for the
              attribute Credential
              weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
              Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
              thrown by the getAttribute method of the DynamicMBean for the attribute Credential
              at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:198)
              at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              at weblogic.Server.main(Server.java:32)
              

    Venkat,
              I assume you are using symmetric ciphers. If soo make sure you
              generate the key for the admin server and copy that to all the managed
              servers in the cluster before you start each of the managed servers. I
              think you are generating keys for each server seperately (which might
              be the reason for the errors you got).
              Hope this helps.
              -Kiran
              "Venkat" <[email protected]> wrote in message news:<[email protected]>...
              > Hi,
              >
              > I am trying to setup cluster environment with weblogic7.0. I have two managed
              > servers in my cluster. The first one I am able start without any problem(The first
              > server and admin is on the same UNIX m/c). When I am trying to start the second
              > server from different m/c(this is another UNIX m/c) it is giving the following
              > error. I am not using default security realm.
              > If anybody come across this error before,please reply me.
              >
              > Thanks
              > Venkat
              >
              > com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad
              > byte.
              > at com.rsa.jsafe.JA_PKCS5Padding.performUnpadding(JA_PKCS5Padding.java:111)
              > at com.rsa.jsafe.JG_BlockCipher.decryptFinal(JG_BlockCipher.java:1092)
              > at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:67)
              > at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:93)
              > at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:53)
              > at weblogic.management.commo.CommoModelMBean.getAttribute(CommoModelMBean.java:319)
              > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1183)
              > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
              > at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:844)
              > at weblogic.management.commo.CommoProxy.invoke(CommoProxy.java:330)
              > at $Proxy42.getCredential(Unknown Source)
              > at weblogic.security.providers.authentication.LDAPAtnDelegate.<init>(LDAPAtnDelegate.java:452)
              > at weblogic.security.providers.authentication.LDAPAuthenticationProviderImpl.initialize(LDAPAuthenticationProviderImpl.java:67)
              > at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:1820)
              > at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:151)
              > at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              > at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              > at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              > at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              > at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              > at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              > at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              > at weblogic.Server.main(Server.java:32)
              > --------------- nested within: ------------------
              > weblogic.security.internal.encryption.EncryptionServiceException - with nested
              > exception:
              > [com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad
              > byte.]
              > at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:77)
              > at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:93)
              > at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:53)
              > at weblogic.management.commo.CommoModelMBean.getAttribute(CommoModelMBean.java:319)
              > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1183)
              > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
              > at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:844)
              > at weblogic.management.commo.CommoProxy.invoke(CommoProxy.java:330)
              > at $Proxy42.getCredential(Unknown Source)
              > at weblogic.security.providers.authentication.LDAPAtnDelegate.<init>(LDAPAtnDelegate.java:452)
              > at weblogic.security.providers.authentication.LDAPAuthenticationProviderImpl.initialize(LDAPAuthenticationProviderImpl.java:67)
              > at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:1820)
              > at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:151)
              > at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              > at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              > at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              > at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              > at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              > at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              > at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              > at weblogic.Server.main(Server.java:32)
              > --------------- nested within: ------------------
              > javax.management.RuntimeOperationsException: RuntimeException thrown by the getAttribute
              > method of the DynamicMBean for the attribute Credential
              > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1185)
              > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
              > at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:844)
              > at weblogic.management.commo.CommoProxy.invoke(CommoProxy.java:330)
              > at $Proxy42.getCredential(Unknown Source)
              > at weblogic.security.providers.authentication.LDAPAtnDelegate.<init>(LDAPAtnDelegate.java:452)
              > at weblogic.security.providers.authentication.LDAPAuthenticationProviderImpl.initialize(LDAPAuthenticationProviderImpl.java:67)
              > at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:1820)
              > at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:151)
              > at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              > at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              > at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              > at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              > at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              > at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              > at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              > at weblogic.Server.main(Server.java:32)
              > <Dec 7, 2002 8:57:33 PM EST> <Critical> <WebLogicServer> <000364> <Server failed
              > during initialization. Exception:weblogic.security.service.SecurityServiceRuntimeException:
              > Problem instantiating Authentication Providerjavax.management.RuntimeOperationsException:
              > RuntimeException thrown by the getAttribute method of the DynamicMBean for the
              > attribute Credential
              > weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
              > Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
              > thrown by the getAttribute method of the DynamicMBean for the attribute Credential
              > at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:198)
              > at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              > at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              > at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              > at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              > at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              > at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              > at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              > at weblogic.Server.main(Server.java:32)
              > >
              > <Dec 7, 2002 8:57:33 PM EST> <Emergency> <WebLogicServer> <000342> <Unable to
              > initialize the server: Fatal initialization exception
              > Throwable: weblogic.security.service.SecurityServiceRuntimeException: Problem
              > instantiating Authentication Providerjavax.management.RuntimeOperationsException:
              > RuntimeException thrown by the getAttribute method of the DynamicMBean for the
              > attribute Credential
              > weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
              > Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
              > thrown by the getAttribute method of the DynamicMBean for the attribute Credential
              > at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:198)
              > at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              > at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              > at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              > at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              > at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              > at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              > at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              > at weblogic.Server.main(Server.java:32)
              > >
              > ***************************************************************************
              > The WebLogic Server did not start up properly.
              > Exception raised:
              > weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
              > Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
              > thrown by the getAttribute method of the DynamicMBean for the attribute Credential
              > at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:198)
              > at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              > at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              > at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              > at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              > at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              > at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              > at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              > at weblogic.Server.main(Server.java:32)
              > Reason: Fatal initialization exception
              > Throwable: weblogic.security.service.SecurityServiceRuntimeException: Problem
              > instantiating Authentication Providerjavax.management.RuntimeOperationsException:
              > RuntimeException thrown by the getAttribute method of the DynamicMBean for the
              > attribute Credential
              > weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
              > Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
              > thrown by the getAttribute method of the DynamicMBean for the attribute Credential
              > at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:198)
              > at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              > at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              > at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              > at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              > at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              > at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              > at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              > at weblogic.Server.main(Server.java:32)
              

  • DM Package error-Could not perform write (Not_Transactional)

    Hi!
    Has anyone received the error message "Could not perform write (Not_Transactional), when trying to load a basic import transaction data manager package? I have checked the Infocube status and it's set to u201CReal-Time Data Target Can BE Loaded With Data; Planning Not Allowedu201D. Any help would be appreciated. Thanks.

    Hi Dzmitry,
    Thanks for your suggestion. I tried to change the status and I received the following error message which would not allow me to change the status. Any other thoughts?
    "Request APO_RD6ZZQMEQGBIUB8QFGSS0YZ4KP(000000002: is yellow or red in Infocube /CPMB/H61H5TU; cannot switch to planning"
    Thanks for your help.
    Nakisha

  • Com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid

    Hi all,
    While running(deploying to default server) ADF application in defalt server I am getting error.
    com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
         at com.rsa.jsafe.c.a(Unknown Source)
         at com.rsa.jsafe.JSAFE_SymmetricCipher.decryptFinal(Unknown Source)
         at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:124)
         at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:184)
         at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
         Truncated. see log file for complete stacktrace
    Caused By: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
         at com.rsa.jsafe.c.a(Unknown Source)
         at com.rsa.jsafe.JSAFE_SymmetricCipher.decryptFinal(Unknown Source)
         at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:124)
         at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:184)
         at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
    could anyone pls suggest me the solution.?
    thanks
    santosh

    Santhosh,
    did you try Google for com.rsa.jsafe.jsafe_paddingexception weblogic ? Why not? I typed it in and found a bunch of hits, including this one
    http://weblogic-wonders.com/weblogic/2010/11/04/com-rsa-jsafe-jsafe_paddingexception-could-not-perform-unpadding-invalid-pad-byte/
    Frank

  • Could not perform unpadding: invalid pad byte.

    Hello All
    In my config file I have 2 references to connection pool files.. In the files I have the following tag.
    <password-encrypted>{3DES}I8OqBHafh35fn6iVd6YXxw==</password-encrypted>
    When I try to run my connection pools are not getting initalized and the following error is displayed
    Could not perform unpadding: invalid pad byte.
    From my limitied knowledge I would just liek to change this to clear text or reencrypt the password. Can anyone help or send a link to an article that would help?
    I am running weblogic 9.2
    Thanks

    You can use the encrypt utility to reencrypt the password.
    http://edocs.bea.com/wls/docs90/admin_ref/utils.html#1209592
    D Walt wrote:
    Hello All
    In my config file I have 2 references to connection pool files.. In the files I have the following tag.
    <password-encrypted>{3DES}I8OqBHafh35fn6iVd6YXxw==</password-encrypted>
    When I try to run my connection pools are not getting initalized and the following error is displayed
    Could not perform unpadding: invalid pad byte.
    From my limitied knowledge I would just liek to change this to clear text or reencrypt the password. Can anyone help or send a link to an article that would help?
    I am running weblogic 9.2
    Thanks

  • Acrobat could not perform recognition (OCR) on this page because this page contains renderable text

    I have a pdf file, which was OCRed by some other software, I am not satisfied with its accuracy, and would like to run adobe acrobat to OCR it again.
    But Adobe says "Acrobat could not perform recognition (OCR) on this page because this page contains renderable text" for each page of the file.
    How can I do to re-OCR the file? Thanks!

    CtDave,
    I am having a similar problem and tried your suggestion but I still get the same message. Any other thoughts or fixes? The difference in my file is I used to be able to edit the text in the PDF file. For the last few months I am no longer able to edit this file.

  • Role Upload - Could not perform action

    Gurus,
    I am attempting to upload a sampling of R/3 ECC 6.0 roles into the portal (EP6). I have the system connection defined and testing successfully. I unfortunately can not execute the upload function. After defining the selections that I wish to upload, in this case a role, I receive the red exclamation mark followed by "Could not perform action. Check the role migration log for additional information"
    I also have not been able to locate this migration log. I have searched here and sap's help portal for the location of this log but to no avail. Any assistance will be greatly appreciated.

    Hi Mike,
    usually you are able do drill down this information further more.
    If you do not know which file to check look in the defaultTrace.<no>.log for more information. There will be a hint to dive in much deeper.
    On the page where you get this message there is a tab "Log Viewer" please have a look at this to get more information.
    Best regards,
    Michael

  • VISA: (Hex 0xBFFF003E) Could not perform operation because of I/O error

    Hello
    I'm trying to communicate with a device which have to be tested with my application. So I send it a command to initiate the device to send me back some values. This values are sended continously with a baud rate of 57600.
    I create a VI to test this communication but I always get the error:
    VISA:  (Hex 0xBFFF003E) Could not perform operation because of I/O error
    I have googled for this thread, but all the described solutions didn't solve my problem (ex. Set Buffer Size to 48, Various Byte Count Values for the VISA Read function, etc.).
    Note: the VI works properly in the LabView 6.1! I have tested. I also tried to receive the Data with a Termial programm (works fine). But another COM Port (on an USB Serial converter) shows me the same Error.
    I just updated to Visa 3.4.1, but no success
    LabView 8.0.1

    Yeah it works
    of course buffer to 4096 and mask to 48
    I added a Flush I/O buffer (mask 16) before reading from Visa (problem was to read data).
    And suddenly it works fine.
    I can't reproduce where the error exactly was. Could it be possible that the RX buffer was already full
    at the time I would to read from Visa or at the time the COM port received data? There are some questions to find out:
    how does LV handle the buffers? will the buffers be cleared if LV starts? when does LV flushes the
    buffers?
    thx

  • Could not perform Write (Inherited Error)

    hi
    Can anyone let me know what is this error and how to solve this.
    Could not perform Write (Inherited Error)
    this got  this error after I started DM Package in BPC NW at Load the flat file to the server.
    regards
    ark

    Hi Ark,
    To check member access profile where access to your dimension has been given,
    Go to User(Your user name)>Check which member access profile is assigned then GO to->member Access profile>Modify Member access profile>all the applivcations are listed there.select Your Application>You find dimesnions->Look for Access i.e.Read or Write access.
    Try this..
    Regards,
    Naresh.K

Maybe you are looking for

  • Zen touch - Light stays on when off and other probl

    Hey, recently my zen has been doing some weird stuff ie when i look for music by selecting genre, it'll automatically start to play any song on the player on shuffle mode. Also, last night when i switched the player off, the blue light was still on a

  • A unified Junk mailbox in Mail?

    Just wondering if it is possible to create a unified mailbox for Junk folders. It's strange that you can assign them from Mailbox menu -> Use this folder for -> Junk, which would normally work if you had just one account, but I have two...

  • Sort by Last column

    Hello I want to sort in descending order by sales and 2005      Calyear                         2002     2003   2004     2005 Material1     2          5566     400 Material2          5     5     300 Material3                    200 Material4     700 

  • How can I download PDF export again wiped from my computer?

    I have paid for PDF Export and it has disappeared from my computer. How can I download it again?

  • Question re Mail

    How do I get mail which was sent from my iPad to also appear in the sent list in Mail on my Mac? I thought everything was supposed to sync, but only received mail is synced between all my devices. I've looked in all the prefs (including on me.com) an