Error from libf4f.dll: failed to swap file

We did a live stream last night using bitrates of 282 and 482, and the video was terrible, constant buffering on client players. Now looking back at the recorded video it looks corrupted audio and video out of place, video is pixelated and stuck. The encoder has over 2mb of upstream bandwidth for encoding so it's not the problem. The problem is FMS interactive server. We are using version 4.5.0, I've setup another instance usinf FMS 4.5.3 will this resolve the issue? According to the FMS 4.5.3 release notes this error is a known problem. How can we stream video like this?
Our server logs in event viewer show a ton of FMS(Core) error msgs about
"error from libf4f.dll: failed to swap file C:\FMS\applications\livepkgr\streams\_definst_\*****"
How can we resolve this issue? The FMS is useless in this state.

Client is streaming from a remote location (a hotel with PLENTY of bandwidth, 50MBs I think) back to the FMS on our VM server.  This is the only stream on the going thru the FMS box at that time.  The video output from the TriCaster goes to a canopas box through BNC. Then in the back there's a firewire that plugs into the "streaming" laptop. That laptop is streaming out with Flash Encoder and hardwired into a router.  That router is plugged into the internet provided at the hotel.  The stream averages anywhere from 200-250 viewers/connections.  We are delivering stream to viewers via RTMP/Flowplayer front-end for desktop users and using the HTTP streaming link for mobile users.  Client is publishing stream at 350 kpbs via Adobe Live Media Encoder.
Does that help?

Similar Messages

  • Adobe Media Server 5.0.1 Get getting this error Fri 09:22:33 AM: Error from libf4f.dll:

    I need to get this figured i think this is what is causing buffering all time, Windows 2008 R2.
    Fri 09:26:22 AM: Error from libf4f.dll: [Utils] [livestream1] Error in updating bootstrap information in C:\Program Files\Adobe\Adobe Media Server 5\applications\livepkgr\streams\college\livestream1/livestream1.bootstrap
    Fri 09:26:23 AM: Error from libf4f.dll: [Utils] [livestream3] Failed to swap in file 'C:\Program Files\Adobe\Adobe Media Server 5\applications\livepkgr\streams\college\livestream3/livestream3.bootstrap'
    Fri 09:26:23 AM: Error from libf4f.dll: [Utils] [livestream3] Error in updating bootstrap information in C:\Program Files\Adobe\Adobe Media Server 5\applications\livepkgr\streams\college\livestream3/livestream3.bootstrap
    Fri 09:26:28 AM: Error from libf4f.dll: [Utils] [livestream3] Failed to swap in file 'C:\Program Files\Adobe\Adobe Media Server 5\applications\livepkgr\streams\college\livestream3/livestream3.bootstrap'
    Fri 09:26:28 AM: Error from libf4f.dll: [Utils] [livestream3] Error in updating bootstrap information in C:\Program Files\Adobe\Adobe Media Server 5\applications\livepkgr\streams\college\livestream3/livestream3.bootstrap
    Fri 09:26:31 AM: Error from libf4f.dll: [Utils] [livestream3] Failed to swap in file 'C:\Program Files\Adobe\Adobe Media Server 5\applications\livepkgr\streams\college\livestream3/livestream3.bootstrap'

    Client is streaming from a remote location (a hotel with PLENTY of bandwidth, 50MBs I think) back to the FMS on our VM server.  This is the only stream on the going thru the FMS box at that time.  The video output from the TriCaster goes to a canopas box through BNC. Then in the back there's a firewire that plugs into the "streaming" laptop. That laptop is streaming out with Flash Encoder and hardwired into a router.  That router is plugged into the internet provided at the hotel.  The stream averages anywhere from 200-250 viewers/connections.  We are delivering stream to viewers via RTMP/Flowplayer front-end for desktop users and using the HTTP streaming link for mobile users.  Client is publishing stream at 350 kpbs via Adobe Live Media Encoder.
    Does that help?

  • Error from libf4f.dll: C.

    We are trying to stream HTTP live streaming with the live packager and flash access. We have followed the steps on the site for both the streaming and setting up the tomcat servers. Everything works fine until we are pushing to the FMS and get following error message in the log file core.00.log
    #Version: 1.0
    #Start-Date: 2011-02-22 16:47:11
    #Software: Adobe Flash Media Server 4.0.0 r1121 x64
    #Date: 2011-02-22
    #Fields: date   time                    x-pid                   x-status             x-ctx                   x-comment
    2011-02-22       16:47:11            6796                    (i)2581237        Starting admin app on core (6796).                  -
    2011-02-22       16:47:11            6796                    (i)2631174        Listener started ( _defaultRoot_ ) : 192.168.42.34:19351 (rtmfp-core)/v4            -
    2011-02-22       16:47:11            6796                    (i)2631174        Listener started ( _defaultRoot_ ) : 127.0.0.1:19351 (rtmfp-core)/v4            -
    2011-02-22       16:47:11            6796                    (i)2631509        Public rtmfp-core addresses for listener _defaultRoot_ are: 192.168.42.34:19351;127.0.0.1:19351              -
    2011-02-22       16:47:11            6796                    (i)2581246        Core (6796) sending register cmd to edge.  -
    2011-02-22       16:48:03            6796                    (e)2611178       Error from libf4f.dll: C.             -
    2011-02-22       16:48:03            6796                    (e)2611423       Failed to record livestream2 (Unknown Error).                       -
    2011-02-22       16:48:03            6796                    (e)2611178       Error from libf4f.dll: C.             -
    2011-02-22       16:48:03            6796                    (e)2611423       Failed to record livestream3 (Unknown Error).                       -
    2011-02-22       16:48:03            6796                    (e)2611178       Error from libf4f.dll: C.             -
    2011-02-22       16:48:03            6796                    (e)2611423       Failed to record livestream1 (Unknown Error).                       -
    We have tried on two different FMS on two different machines. We still get the same error
    It works fine when we just stream HTTP live without flash access.
    It is really hard for us to debug when we only get “unknown error”
    Thanks
    Samuel Oest

    Hi Samuel,
    I've submitted a customer-reported bug regarding this issue.  Our Technical Support Staff will be contacting you soon.
    cheers,
    /Eric.

  • Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit

    My core.log file keeps showing these errors everytime I start to stream. My streams are not viewable on PC's and only viewable on iOS devices.
    Is there something wrong with the libf4f.dll file? I'm using FMS 4.5 on Windows 2003 Server.
    2011-12-28    15:44:09    4020    (e)2611178    Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit.    -
    2011-12-28    15:44:09    4020    (e)2611423    Failed to record bbc2011-BBC73 (Unknown Error).    -
    2011-12-28    16:02:00    4020    (e)2611178    Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit.    -
    2011-12-28    16:02:00    4020    (e)2611423    Failed to record bbc2011-BBC71 (Unknown Error).    -
    2011-12-28    16:57:12    4020    (e)2611363    Server detected a backward timestamp from 5006873 to 0 in file: C:\FMSHOME\applications\livepkgr\streams\_definst_\bbc2011
    2011-12-28    17:18:21    4020    (e)2611178    Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit.    -
    2011-12-28    17:18:21    4020    (e)2611423    Failed to record bbc2011-BBC83 (Unknown Error).    -
    2011-12-28    17:36:12    4020    (e)2611178    Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit.    -
    2011-12-28    17:36:12    4020    (e)2611423    Failed to record bbc2011-BBC81 (Unknown Error).    -
    2011-12-28    18:38:09    4020    (e)2611363    Server detected a backward timestamp from 5420086 to 0 in file: C:\FMSHOME\applications\livepkgr\streams\_definst_\bbc2011-BBC82    -
    2011-12-28    19:12:44    4020    (e)2611178    Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit.    -
    2011-12-28    19:12:44    4020    (e)2611423    Failed to record bbc2011-BBC92 (Unknown Error).    -
    2011-12-28    19:23:38    4020    (e)2611178    Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit.    -
    2011-12-28    19:23:38    4020    (e)2611423    Failed to record bbc2011-BBC91 (Unknown Error).    -
    2011-12-28    20:41:50    4020    (e)2611363    Server detected a backward timestamp from 6390123 to 0 in file: C:\FMSHOME\applications\livepkgr\streams\_definst_\bbc2011-BBC93    -
    2011-12-28    21:12:05    4020    (e)2611178    Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit.    -
    2011-12-28    21:12:05    4020    (e)2611423    Failed to record bbc2011-BBC102 (Unknown Error).    -
    2011-12-28    22:49:23    4020    (i)2581247    Core (4020) disconnected from edge.    -
    2011-12-28    22:49:23    4020    (i)2581233    Core (4020) disconnecting from admin: 200.    -
    Thanks,
    Dave

    There is a concept of Absolute Time Code which enables the encoders to publish the livestream based on absolute system time rather than starting the messages from timestamp 0 everytime you append to a recording.
    I suspect you encoder is starting everytime from 0 timestamp but since the server already has recording till some time - say x, for the server these are backward timestamps and hence the continous warnings.
    Also to safeguard FMS against such conditions and cause memory crashes, we only allow messages with backward timestamps to accumulate in the process queue upto a limit and then the recording is stopped. Thats why you are observing the errors - 
    "Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit.    - 
    2011-12-28    19:23:38    4020    (e)2611423    Failed to record bbc2011-BBC91 (Unknown Error).    -"
    Try to check your encoder settings for stream synchronization or ATC settings and enable them.

  • Error from libf4f.dll

    Below are the error messages I am getting when I try to use Flash Media Live Encoder 3.2. I'm trying to set it up to stream to iOS devices.
    I'm following the guide here: http://www.adobe.com/devnet/flashmediaserver/articles/single-live-video-stream-http-flash- ios.html
    Tue 12:14:34 PM: Error from libf4f.dll: [Fragmenter] [livestream] error trackType does not match codec type
    Tue 12:14:34 PM: Error from libf4f.dll: [Fragmenter] [livestream] Error Invalid message
    Tue 12:14:34 PM: Error from libf4f.dll: [Utils] [livestream] Error when pushing messages to Fragmenter : 5406 Invalid message
    Tue 12:14:34 PM: Error from libf4f.dll: f4fAdaptor::record failed. Error: Invalid message.
    Tue 12:14:34 PM: Failed to record livestream.

    Your settings are perfectly fine. Can you do as follows
    1. Stop the publishing,
    2. Delete all your streams folder of "livepkgr'.
    3. Stop the FMS.
    4. Close FMLE.Enable ATC at FMLE end (<rootinstall>\Flash Media Live Encoder 3.2\Conf - Config.xml)    
    <streamsynchronization>
                                  <!-- "true" to enable this feature, "false" to disable.                                                  -->
                                  <enable>true</enable>
    5. Restart FMLE.
    6. Restart FMS.
    7. Start Publishing again and see if things are working fine.

  • Error from ejbc: Compiler failed executable.exec

    Hi all,
    I am using weblogic server 8.1 and encounter an error when I build my project, could anyone give me a helping hand? Thank you.
    This is my Configuration:
    Application Type: Empty Application
    Project Type: EJB Project
    Project Name: LibraryEJBProject
    DataSource: LibraryDataSource using cgPool
    Table: Library_Book under Schemas\Weblogic\Tables of pointbase server
    EJB name: BookBean.EJB under LibraryEJBProject\book
    When I right click LibraryEJBProject and click build, the following error comes out:
    ======================================================
    Build project LibraryEJBProject started.
    BUILD STARTED
    build:
    Created dir: C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build
    check-env:
    WARNING: Checking to see if there is anything new to build...
    Created dir: C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_ejb_crc
    no-ejbgen:
    run-build:
    clean-modules:
    removed module 'LibraryEJBProject.jar'
    WARNING: Running EJBGen...
    Loading source file C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\/wlw_LibraryEJBProject_build/../wlw_ejb_crc//ejbgentemp/Book\BookBean.java...
    Constructing Javadoc information...
    EJBGen 2.16
    [Info:] Creating C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\/wlw_LibraryEJBProject_build/../wlw_ejb_crc//ejbgentemp\Book\Book.java
    [Info:] Creating C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\/wlw_LibraryEJBProject_build/../wlw_ejb_crc//ejbgentemp\Book\BookHome.java
    [Info:] Creating C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\/wlw_LibraryEJBProject_build/../wlw_ejb_crc//ejbgentemp\META-INF\ejb-jar.xml
    [Info:] null [Bean] MAKE CLASS NAME G:BookHome P:Book N:BookHome
    [Info:] null [Bean] MAKE CLASS NAME G:Book P:Book N:Book
    [Info:] Creating C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\/wlw_LibraryEJBProject_build/../wlw_ejb_crc//ejbgentemp\META-INF\weblogic-ejb-jar.xml
    [Info:] Creating C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\/wlw_LibraryEJBProject_build/../wlw_ejb_crc//ejbgentemp\META-INF\weblogic-cmp-rdbms-jar.xml
    [Info:] Creating C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\/wlw_LibraryEJBProject_build/../wlw_ejb_crc//ejbgentemp\ejbgen-build.xml
    post-ejbgen:
    clean-ejbc:
    Copying 7 files to C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build
    WARNING: EJBGen ok. Compiling...
    runjavac:
    Compiling 3 source files to C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build
    WARNING: All files compiled. Running ejbc...
    <Dec 3, 2004 12:18:44 PM CST> <Warning> <EJB> <BEA-010212> <The EJB 'Book(Jar: C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build)' contains at least one method without an explicit transaction attribute setting. The default transaction attribute of Supports will be used for the following methods: local-home[createQuery(), remove(java.lang.Object), findByPrimaryKey(java.lang.Integer), create(java.lang.Integer)] local[getBookID(), getIsbn(), getName(), setPublisher(java.lang.String), getPublisher(), setAuthor(java.lang.String), setBookID(java.lang.Integer), remove(), setIsbn(java.lang.String), getAuthor(), setName(java.lang.String)] >
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:76: cannot resolve symbol
    symbol : class BookBean
    location: interface Book.Book
    public final class Book_5wlu3i__WebLogic_CMP_RDBMS extends Book.BookBean
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:760: cannot resolve symbol
    symbol : class Book_5wlu3i_Intf
    location: interface Book.Book
    Book.Book_5wlu3i_Intf beanIntf)
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i_Intf.java:39: cannot resolve symbol
    symbol : class Book_5wlu3i_Intf
    location: interface Book.Book
    (java.sql.ResultSet rs, java.lang.Integer offset, Object __WL_pk, Book.Book_5wlu3i_Intf var)
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i_ELOImpl.java:15: cannot resolve symbol
    symbol : class Book
    location: interface Book.Book
    implements Book.Book, weblogic.utils.PlatformConstants, java.io.Serializable
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i_LocalHomeImpl.java:13: cannot resolve symbol
    symbol : class BookHome
    location: interface Book.Book
    implements Book.BookHome, weblogic.utils.PlatformConstants
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i_LocalHomeImpl.java:76: cannot resolve symbol
    symbol : class Book
    location: interface Book.Book
    public Book.Book create (java.lang.Integer arg0)
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i_LocalHomeImpl.java:101: cannot resolve symbol
    symbol : class Book
    location: interface Book.Book
    public Book.Book findByPrimaryKey(java.lang.Integer arg0)
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:244: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.setEntityContext(arg0);
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:257: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.unsetEntityContext();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:269: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbActivate();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:490: cannot resolve symbol
    symbol : class Book_5wlu3i__WebLogic_CMP_RDBMS
    location: interface Book.Book
    Book.Book_5wlu3i__WebLogic_CMP_RDBMS __WL_bean = null;
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:566: cannot resolve symbol
    symbol : class Book_5wlu3i__WebLogic_CMP_RDBMS
    location: interface Book.Book
    __WL_bean = (Book.Book_5wlu3i__WebLogic_CMP_RDBMS)__WL_pm.getBeanFromRS(__WL_pk, __WL_rsInfo);
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:763: cannot resolve symbol
    symbol : class Book_5wlu3i__WebLogic_CMP_RDBMS
    location: interface Book.Book
    Book.Book_5wlu3i__WebLogic_CMP_RDBMS __WL_bean = (Book.Book_5wlu3i__WebLogic_CMP_RDBMS)beanIntf;
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:763: cannot resolve symbol
    symbol : class Book_5wlu3i__WebLogic_CMP_RDBMS
    location: interface Book.Book
    Book.Book_5wlu3i__WebLogic_CMP_RDBMS __WL_bean = (Book.Book_5wlu3i__WebLogic_CMP_RDBMS)beanIntf;
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:922: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbLoad();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:936: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbStore();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:950: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbRemove();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1051: cannot resolve symbol
    symbol : class Book_5wlu3i__WebLogic_CMP_RDBMS
    location: interface Book.Book
    case 0: __WL_loadGroup0FromRS(rs, offset, __WL_pk, (Book.Book_5wlu3i__WebLogic_CMP_RDBMS)eb); break;
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1167: reference to + is ambiguous, both method +(java.lang.String,java.lang.String) in and method +(java.lang.String,int) in match
    if(__WL_verbose) Debug.say("setting("+this+") 'author' using column " __WL_num ". Value is " + this.author);
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1178: reference to + is ambiguous, both method +(java.lang.String,java.lang.String) in and method +(java.lang.String,int) in match
    if(__WL_verbose) Debug.say("setting("+this+") 'isbn' using column " __WL_num ". Value is " + this.isbn);
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1189: reference to + is ambiguous, both method +(java.lang.String,java.lang.String) in and method +(java.lang.String,int) in match
    if(__WL_verbose) Debug.say("setting("+this+") 'name' using column " __WL_num ". Value is " + this.name);
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1200: reference to + is ambiguous, both method +(java.lang.String,java.lang.String) in and method +(java.lang.String,int) in match
    if(__WL_verbose) Debug.say("setting("+this+") 'publisher' using column " __WL_num ". Value is " + this.publisher);
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1663: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbCreate( arg0);
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1702: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbPostCreate( arg0);
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1847: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbRemove();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1907: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbLoad();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1938: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbStore();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:2072: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbPassivate();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i_LocalHomeImpl.java:80: cannot resolve symbol
    symbol : class Book
    location: interface Book.Book
    return (Book.Book) super.create(md_ejbCreate_I,
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i_LocalHomeImpl.java:105: cannot resolve symbol
    symbol : class Book
    location: interface Book.Book
    return (Book.Book)
    ^
    30 errors
    ERROR: ERROR: Error from ejbc: Compiler failed executable.exec
    ERROR: ERROR: ejbc couldn't invoke compiler
    BUILD FAILED
    ERROR: ERROR: Error from ejbc: Compiler failed executable.exec
    ERROR: ERROR: ejbc couldn't invoke compiler
    ======================================================
    What would be the cause of the error, would it be related to the way I create the datasource and the table? Or other causes, please help. Thank you.
    Regards,
    Nicholas Lok

    It's difficult to tell solely by the messages. One there seems to be a problem finding a base class. One thing that I notice is that the package seems to contain 'book' with a lower case 'b' as in:
    EJB name: BookBean.EJB under LibraryEJBProject\book
    Whereas all the error messages are saying that they are having trouble finding something with a package name like 'Book' with a capital 'B'.
    Perhaps that is the problem, the package has to be consistently 'book' or 'Book' and can't be both.
    Hope I'm right and hope this helps.
    thorick

  • IBM T60 Laptop Error Message (vrlogon.dll failed toload)

    Hello:
    After uninstlaling HP Drivers, I rebooted the the laptop and I get the following error message "the logon user interface dll vr logon.dll failed to load ...contact your system admin or replace dll or restore.
    Any suggestions to fix this problem?

    Try the following user tip:
    Troubleshooting issues with iTunes for Windows updates

  • Recurring rendering error "an output module failed. The file may be damaged or corrupted"

    From today onwards I've been getting this error whenever I'm exporting to Quicktime mov (at least H264 and DXV). I've been reading a lot about it and it seems to be an ongoing issue, related to the QT32 server (whatever that is). I haven't been able to find a satisfactory solution yet. One thing's for sure, it's messing up my workflow.
    Some additional info:
    System:      Mac
    OS:             10.9.2 (Mavericks)
    Adobe:        Adobe CC
    Quicktime:  Version 10.3
    One other weird thing is, whenever I quit and restart AE, it renders fine once. After that it breaks.
    Hope you can help!

    AE version:     CC 12.2.1.5
    Updates:        Yes, everything is updated to the last version.
    Mac OS:         10.9.2 (Mavericks)
    Hardware:       Processor:   2.8 Ghz Intel Core 2 duo
                            Memory:      8Gb 1067 MHz DDR3
                            Graphics:     NVIDIA GeForce 9600M GT 512Mb
                            #Cores:        2
                            Harddisk:     Samsung 840 EVO 500GB
                            External HD's:     None
    Drivers:            CUDA: Installed the most recent version 3 weeks ago, tried finding the
                            version.. Sorry I'm a real nOOb when it comes to this stuff
    3dparty hardware:     None
    Source footage:        See previous post
    Error message:    
    I can replicate the error again and again. I can predict that it will work fine the first render, second time it breaks.
    I've done this a million times in CS5, and it worked fine in the CC trial. As soon as I went to 'full', it broke.
    I REALLY hope this is sufficient information!
    Tnx for taking the time to help me out

  • Error message"Copying music failed.  The file name was invalid or too long"

    That's the message I get; no other details. I don't know which file. Or whether it's more than one file. How can I know/find out which file (and what a valid filename would be)? Grrrr...
    itunes managed to copy around 12 gigs before this happened, so I don't know what got copied and what didn't.
    Please help! I need to rebuild my playlists by Friday!
    Thanks so much in advance!!!
    Greg

    BUMP
    Yes, I just get that message. I don't see how I could investigate this problem.
    I didn't mention that this happened when I was consolidating my library, not copying files to another computer.
    In other words, I'm using a "normal" itunes procedure, itunes won't complete it, and won't tell me exactly why or how to figure out how to fix it...
    Is there at least some easy way to tell which files were successfully copied to my itunes music folder so I can work on moving the uncopied files?
    Can anybody help me?

  • Getting "querypanel.dll failed to register" on Windows 7 32 bit machine

    Trying to move from CR 2008 SP2 to CR 2008 SP3.
    For the CR 2008 SP2 version of our application, which runs our Crystal .rpt files, we used Visual Studio 2005.  we then created a Visual Studio .msi file, using the merge module (CRRuntime_12_2), to install this application on a target machine that had .NET Framework 2.0 and VC++ Redistributable 2005 SP1 installed. If these two latter prerequisites were not installed, our install would fail because the CEReportSource.dll could not be registered.
    After installing CR SP3 on my development machine, we created a new Visual Studio project, again using Visual Studio 2005. I used CRRuntime_12_3 as the merge module and everything else was the same.
    I was getting this same error message "CEReportSource.dll failed to register" when I attempt to install the SP3 version of the app on the very same machine on which I previously successfully installed the SP2 version. I found an answer in these forums to install Microsoft Visual C++ 2005 SP1 update. Even this did not help. When I installed  MS VC++  2008 Redistributable - x86 9.0.30729.17, finally the problem of "CEReportSource.dll failed to register"  went away on XP and Vista machines.
    Now I am trying to install my program on Windos 7 32 bit machine and I get "querypanel.dll failed to register".
    Q1. By installing S VC++  2008 Redistributable - x86 9.0.30729.17, the problem of "CEReportSource.dll failed to register" did not occur. Is this the right thing to do. I am not sure why VC++ 2005 SP1 did not fix the issue.
    Q2.What do we need in order to prevent "querypanel.dll failed to register" error on Windows 7 32 bit machine.
    Thanks for your time.

    Moved to .NET SDK forum.
    Search here, lots of info on distribution. Likely caused by MS updated the C++ runtime to include security updates. Go to MS's site and download the latest C++ distribution package with enhanced security.
    If you use the CR MSI package rather than the Merge Modules it should work.
    Thank you
    Don
    Edited by: Don Williams on Nov 9, 2010 2:16 PM

  • Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"

    I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
    Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
    I tried all the things below;
    * I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
    * I'm deleting all the keys related with Sql Server from Regedit.
    * Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
    Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
    * My firewall is already closed. And i have not any antivirus software.
    * I gave the permission for port 1433 on firewall.
    Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.

    Here's the ERRORLOG file which i found under the folder;
    Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
    2014-09-27 03:39:40.15 Server      Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) 
    Apr  2 2010 15:48:46 
    Copyright (c) Microsoft Corporation
    Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
    2014-09-27 03:39:40.15 Server      (c) Microsoft Corporation.
    2014-09-27 03:39:40.15 Server      All rights reserved.
    2014-09-27 03:39:40.15 Server      Server process ID is 5768.
    2014-09-27 03:39:40.15 Server      System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
    2014-09-27 03:39:40.15 Server      Authentication mode is MIXED.
    2014-09-27 03:39:40.15 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2014-09-27 03:39:40.15 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2014-09-27 03:39:40.15 Server      Command Line Startup Parameters:
    -m SqlSetup
    -f
    -Q
    -q Turkish_CI_AS
    -T 4022
    -T 4010
    -T 3659
    -T 3610
    2014-09-27 03:39:40.18 Server      Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically.  After
    the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
    2014-09-27 03:39:40.18 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-09-27 03:39:40.18 Server      Detected 4 CPUs. This is an informational message; no user action is required.
    2014-09-27 03:39:40.31 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2014-09-27 03:39:40.32 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2014-09-27 03:39:40.43 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
    only. No user action is required.
    2014-09-27 03:39:40.45 Server      Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
    is required.
    2014-09-27 03:39:40.45 spid7s      Warning ******************
    2014-09-27 03:39:40.45 spid7s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2014-09-27 03:39:40.46 spid7s      Starting up database 'master'.
    2014-09-27 03:39:40.52 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2014-09-27 03:39:40.58 spid7s      SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
    2014-09-27 03:39:40.59 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:40.59 spid7s      Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
    2014-09-27 03:39:40.59 spid7s      Starting up database 'mssqlsystemresource'.
    2014-09-27 03:39:40.61 spid7s      The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
    2014-09-27 03:39:40.94 spid7s      Password policy update was successful.
    2014-09-27 03:39:40.94 spid8s      Starting up database 'model'.
    2014-09-27 03:39:40.95 spid7s      Server name is 'CAGATAY'. This is an informational message only. No user action is required.
    2014-09-27 03:39:41.21 spid8s      Clearing tempdb database.
    2014-09-27 03:39:41.21 spid10s     A new instance of the full-text filter daemon host process has been successfully started.
    2014-09-27 03:39:41.24 Server      A self-generated certificate was successfully loaded for encryption.
    2014-09-27 03:39:41.24 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    2014-09-27 03:39:41.24 Server      Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag
    7806. This is an informational message only. No user action is required.
    2014-09-27 03:39:41.28 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
    to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    2014-09-27 03:39:41.28 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2014-09-27 03:39:41.70 spid8s      Starting up database 'tempdb'.
    2014-09-27 03:39:41.86 spid7s      Warning ******************
    2014-09-27 03:39:41.86 spid7s      Attempting to change default collation to Turkish_CI_AS.
    2014-09-27 03:39:41.92 spid7s       index restored for master.syspriorities.
    2014-09-27 03:39:41.95 spid7s       index restored for master.sysbrickfiles.
    2014-09-27 03:39:41.96 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:41.96 spid7s       index restored for master.sysowners.
    2014-09-27 03:39:42.13 spid7s       index restored for master.sysdbreg.
    2014-09-27 03:39:42.16 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.16 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.16 spid7s       index restored for master.sysschobjs.
    2014-09-27 03:39:42.17 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.17 spid7s       index restored for master.syscolpars.
    2014-09-27 03:39:42.17 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysxlgns.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysxsrvs.
    2014-09-27 03:39:42.18 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysnsobjs.
    2014-09-27 03:39:42.18 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.syscerts.
    2014-09-27 03:39:42.19 spid7s       index restored for master.sysrmtlgns.
    2014-09-27 03:39:42.19 spid7s       index restored for master.sysxprops.
    2014-09-27 03:39:42.19 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.19 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.31 spid7s       index restored for master.sysscalartypes.
    2014-09-27 03:39:42.31 spid7s       index restored for master.sysidxstats.
    2014-09-27 03:39:42.31 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysendpts.
    2014-09-27 03:39:42.32 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysclsobjs.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysremsvcbinds.
    2014-09-27 03:39:42.32 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysrts.
    2014-09-27 03:39:42.33 spid7s       index restored for master.sysasymkeys.
    2014-09-27 03:39:42.33 spid7s       index restored for master.syssqlguides.
    2014-09-27 03:39:42.44 spid7s       index restored for master.syssoftobjrefs.
    2014-09-27 03:39:42.47 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.48 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.49 spid7s       index restored for master.spt_values.
    2014-09-27 03:39:42.49 spid7s       index restored for master.MSreplication_options.
    2014-09-27 03:39:42.56 spid7s       index restored for tempdb.syspriorities.
    2014-09-27 03:39:42.56 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s       index restored for tempdb.sysowners.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s       index restored for tempdb.sysschobjs.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.59 spid7s       index restored for tempdb.syscolpars.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysnsobjs.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.syscerts.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysxprops.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysscalartypes.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysidxstats.
    2014-09-27 03:39:42.61 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysclsobjs.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysremsvcbinds.
    2014-09-27 03:39:42.61 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysrts.
    2014-09-27 03:39:42.62 spid7s       index restored for tempdb.sysasymkeys.
    2014-09-27 03:39:42.69 spid7s       index restored for tempdb.syssqlguides.
    2014-09-27 03:39:42.69 spid7s       index restored for tempdb.syssoftobjrefs.
    2014-09-27 03:39:42.75 spid7s       index restored for model.syspriorities.
    2014-09-27 03:39:42.75 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.75 spid7s       index restored for model.sysowners.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.76 spid7s       index restored for model.sysschobjs.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.syscolpars.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysnsobjs.
    2014-09-27 03:39:43.00 spid7s       index restored for model.syscerts.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysxprops.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysscalartypes.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysidxstats.
    2014-09-27 03:39:43.01 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysclsobjs.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysremsvcbinds.
    2014-09-27 03:39:43.01 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysrts.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysasymkeys.
    2014-09-27 03:39:43.01 spid7s       index restored for model.syssqlguides.
    2014-09-27 03:39:43.01 spid7s       index restored for model.syssoftobjrefs.
    2014-09-27 03:39:43.02 spid7s      Starting up database 'msdb'.
    2014-09-27 03:39:43.82 spid7s       index restored for msdb.syspriorities.
    2014-09-27 03:39:43.85 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.93 spid7s       index restored for msdb.sysowners.
    2014-09-27 03:39:43.99 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.09 spid7s       index restored for msdb.sysschobjs.
    2014-09-27 03:39:44.12 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.20 spid7s       index restored for msdb.syscolpars.
    2014-09-27 03:39:44.20 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.20 spid7s       index restored for msdb.sysnsobjs.
    2014-09-27 03:39:44.20 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.25 spid7s       index restored for msdb.syscerts.
    2014-09-27 03:39:44.25 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.26 spid7s       index restored for msdb.sysxprops.
    2014-09-27 03:39:44.26 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.26 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.27 spid7s       index restored for msdb.sysscalartypes.
    2014-09-27 03:39:44.37 spid7s       index restored for msdb.sysidxstats.
    2014-09-27 03:39:44.41 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysclsobjs.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysremsvcbinds.
    2014-09-27 03:39:44.42 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysrts.
    2014-09-27 03:39:44.54 spid7s       index restored for msdb.sysasymkeys.
    2014-09-27 03:39:44.54 spid7s       index restored for msdb.syssqlguides.
    2014-09-27 03:39:44.59 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.74 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.85 spid7s       index restored for msdb.syssoftobjrefs.
    2014-09-27 03:39:44.89 spid7s       index restored for msdb.syspolicy_policies_internal.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.sysproxies.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.syscollector_execution_stats_internal.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.syssubsystems.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.log_shipping_primary_secondaries.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.sysdownloadlist.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.log_shipping_monitor_primary.
    2014-09-27 03:39:44.92 spid7s       index restored for msdb.sysoriginatingservers.
    2014-09-27 03:39:44.93 spid7s       index restored for msdb.log_shipping_monitor_history_detail.
    2014-09-27 03:39:44.95 spid7s       index restored for msdb.log_shipping_monitor_error_detail.
    2014-09-27 03:39:44.95 spid7s       index restored for msdb.log_shipping_secondary.
    2014-09-27 03:39:44.97 spid7s       index restored for msdb.log_shipping_secondary_databases.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.log_shipping_monitor_secondary.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysjobs.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysutility_ucp_mi_database_health_internal.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.syscollector_blobs_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysjobsteps.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.logmarkhistory.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_mi_session_statistics_internal.
    2014-09-27 03:39:45.12 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.12 spid7s       index restored for msdb.sysdtscategories.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.syspolicy_target_sets_internal.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysschedules.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysdac_instances_internal.
    2014-09-27 03:39:45.33 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.50 spid7s       index restored for msdb.sysssispackages.
    2014-09-27 03:39:45.51 spid7s       index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
    2014-09-27 03:39:45.51 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.52 spid7s       index restored for msdb.sysssispackagefolders.
    2014-09-27 03:39:45.52 spid7s       index restored for msdb.sysdac_history_internal.
    2014-09-27 03:39:45.53 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.syscategories.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.systargetservers.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.systargetservergroups.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.syspolicy_policy_category_subscriptions_internal.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.sysalerts.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.sysoperators.
    2014-09-27 03:39:45.63 spid7s       index restored for msdb.syspolicy_system_health_state_internal.
    2014-09-27 03:39:45.63 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.63 spid7s       index restored for msdb.syscollector_config_store_internal.
    2014-09-27 03:39:45.65 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.65 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.65 spid7s       index restored for msdb.sysmanagement_shared_server_groups_internal.
    2014-09-27 03:39:45.66 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.sysmanagement_shared_registered_servers_internal.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.syscachedcredentials.
    2014-09-27 03:39:45.79 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.79 spid7s       index restored for msdb.syscollector_collection_sets_internal.
    2014-09-27 03:39:45.79 spid7s       index restored for msdb.sysutility_ucp_dac_health_internal.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.MSdbms.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.MSdbms_datatype.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.sysmail_profile.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.sysutility_ucp_managed_instances_internal.
    2014-09-27 03:39:45.83 spid7s       index restored for msdb.syspolicy_management_facets.
    2014-09-27 03:39:45.84 spid7s       index restored for msdb.sysutility_ucp_mi_health_internal.
    2014-09-27 03:39:45.86 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.86 spid7s       index restored for msdb.syscollector_collector_types_internal.
    2014-09-27 03:39:45.86 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.86 spid7s       index restored for msdb.syspolicy_configuration_internal.
    2014-09-27 03:39:45.87 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.87 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.syspolicy_facet_events.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.sysmail_account.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.syspolicy_conditions_internal.
    2014-09-27 03:39:45.88 spid7s       index restored for msdb.sysutility_ucp_health_policies_internal.
    2014-09-27 03:39:45.88 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.88 spid7s       index restored for msdb.syscollector_collection_items_internal.
    2014-09-27 03:39:45.90 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.00 spid7s       index restored for msdb.sysmail_servertype.
    2014-09-27 03:39:46.00 spid7s       index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
    2014-09-27 03:39:46.02 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
    2014-09-27 03:39:46.03 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_configuration_internal.
    2014-09-27 03:39:46.03 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.sysmail_server.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.syspolicy_policy_categories_internal.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.syspolicy_object_sets_internal.
    2014-09-27 03:39:46.04 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.sysmail_configuration.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.sysdbmaintplan_databases.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.log_shipping_primary_databases.
    2014-09-27 03:39:46.39 spid7s      The default collation was successfully changed.
    2014-09-27 03:39:46.39 spid7s      Recovery is complete. This is an informational message only. No user action is required.
    2014-09-27 03:39:47.17 spid51      Changed database context to 'master'.
    2014-09-27 03:39:47.18 spid51      Changed language setting to us_english.
    2014-09-27 03:39:47.72 spid51      Setting database option RECOVERY to FULL for database model.
    2014-09-27 03:39:47.84 spid51      Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.84 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:47.98 spid51      Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:47.98 spid51      Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:48.27 spid51      Error: 15007, Severity: 16, State: 1.
    2014-09-27 03:39:48.27 spid51      '' is not a valid login or you do not have permission.
    2014-09-27 03:51:25.13 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:51:25.13 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:51:32.67 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:51:32.67 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:51:42.11 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:51:42.11 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:52:42.07 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:52:42.07 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:53:01.23 Logon       Error: 18461, Severity: 14, State: 1.
    2014-09-27 03:53:01.23 Logon       Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
    2014-09-27 03:53:17.57 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:53:17.57 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:53:32.54 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:53:32.54 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:04.29 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:54:04.29 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:10.36 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:54:10.36 Logon       Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:47.18 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:54:47.18 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    Resolve the error, please refer to the following links.
    Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
    could not register the SPN Kerberos:
    http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html  
    Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server

  • Loadlibrary ("olkexpress5.dll") failed - The specified module could not be found.

    About a month ago, the Desk Manager app stopped recognizing that my blackberry was connected via usb so I decided to remove/reinstall the Blackberry Desktop 4.3 software. Now, everytime I install the software I receive the following message during the installation:Errors 1904.Module C:\Program Files\Research In Motion\Blackberry\IS71 Connectors\OE Connector\OLKExpress5.dll failed to register.  HRESULT-2147024770.  Contact your support personnel. If I try to manually register the file it fails with the following error "Loadlibrary ("olkexpress5.dll") failed - The specified module could not be found." My the desktop manager currently will recognize my blackberry as long as I don't disconnect the blackberry before first powering off the laptop.  Any one have any ideas regarding this issue?

    Perform clean uninstall of BlackBerry Desktop Software.
    Check for instruction: http://www.blackberry.com/btsc/KB02206
    After that  go to here: http://na.blackberry.com/eng/services/desktop/
    and download the latest (v4.7) BlackBerry Desktop Software.
    I recommend to download  BlackBerry Desktop Software without Media Manager.
    Media manager is not necessary to transfer files to the device and vice versa.
    Check this link: HOWTO : use your blackberry as a USB device

  • MacVim - Persistent UI failed to open file file

    Hi,
    I have recently installed MacVim. Now, every time i start MacVim from the Terminal, I have this error message :
    Persistent UI failed to open file file://localhost/Users/Me/Library/Saved%20Application%20State/org.vim.MacVim.sa vedState/window_2.data: No such file or directory (2)
    I saw that the file file://localhost/Users/Me/Library/Saved%20Application%20State wad locked.
    How can I solve this problem?
    Any help would be appreciated. Thanks.

    <BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by zhai ping ([email protected]):
    I have uploaded the word documents by sql loader,but some documents succeeded,some failed
    why?
    1.create table
    create table wordtable(
    title varchar2(256) primary key ,
    content blob);
    2.load.ctl
    load data
    INFILE 'load.dat'
    INTO TABLE wordtable
    APPEND
    FIELDS TERMINATED BY ','
    (title,
    ext_fname FILLER CHAR(80),
    content LOBFILE(ext_fname) TERMINATED BY EOF)
    3.load.dat
    ND551,./doc/001.doc,
    ND552,./doc/002.doc,
    ND553,./doc/003.doc,
    ND554,./doc/004.doc,
    ND555,./doc/005.doc,
    ND556,./doc/006.doc,
    4.Use sqlloader to load the documents
    sqlldr userid=test/test control=load.ctl log=load.log
    <HR></BLOCKQUOTE>
    null

  • Copying music failed. The file name was invalid or too long.

    I went to consolidate my music, but when it got about 2/3 of the way through, it stopped with the error message, "Copying music failed. The file name was invalid or too long." I don't know which file it is referring to. How do I find this out?
    I needed to cosolidate so I could backup the entire library to DVD. Now I'm left with two partially complete libraries with many duplicates.

    To find out which file it was, look at where you were
    copying them too and see which was the last file
    copied - and then go back to your source, and go to
    the next one - it should be that one.
    I just wanted to add that I had the same issue (failure to finish copying and "invalid or too long" error msg) and at first didn't see how looking for the last file copied would work since iTunes is copying into folders.
    Duh.
    Reverse sort by date modified (newest folder at the top of the list) then drill down to the folder containing the files being copied. Voila. There was the (missing) culprit, and I knew which file to rename in the source folder.
    Thanks for the kick in the brain pan.
    Sony VAIO PCG-V505ACP Windows XP Pro

  • ORA-02068: following severe error from ....

    Hi,
    we have a dataguard setup for 10g databases on AIX platform as below.
    host1(TALON) host2(CATALINA)
    TICSPROD (PRIMARY ) TICSPROD(STANDBY)
    PLSPROD (STANDBY) PLSPROD (PRIMARY)
    We have decided to recreate PLSPROD STANDBY(because of some setup issues) this weekend and last night we just disabled the PLSPROD STANDBY.Means now only PLSPROD PRIMARY is working.
    Last night, suddenly in the PRIMARY TICSPROD alert log file we see the below error.Is it because of the dataguard issue or any other issue.Please help as we have no clue how to resolve this.
    ORA-02050: transaction 4.34.2844973 rolled back, some remote DBs may be in-doubt
    ORA-02068: following severe error from PLSPROD
    ORA-03113: end-of-file on communication channel

    We have decided to recreate PLSPROD STANDBY(because of some setup issues) this weekend and last night we just disabled the PLSPROD STANDBY.Means now only PLSPROD PRIMARY is working.
    Last night, suddenly in the PRIMARY TICSPROD alert log file we see the below error.Is it because of the dataguard issue or any other issue.Please help as we have no clue how to resolve this.
    ORA-02050: transaction 4.34.2844973 rolled back, some remote DBs may be in-doubt
    ORA-02068: following severe error from PLSPROD
    ORA-03113: end-of-file on communication channel
    What are the parameters of standby
    post
    show parameter dest_2
    show parameter state_2ORA-02050:
         transaction string rolled back, some remote DBs may be in-doubt
    Cause:      network or remote failure in 2PC.
    Action:      Notify operations; remote DBs will automatically re-sync when the failure is repaired.
    defer the destination state 2 also refer the below link
    http://www.orafaq.com/forum/t/67115/2/

Maybe you are looking for