Obeserver dll version mismatch -8003

hello,
i created a Company object and want to connect to the SAP BO Database but we always get the following error:
Obeserver dll version mismatch -8003
Please help for gods sake..!!!!!

Hi Amit,
Try the following steps:
1.  Locate the Temp folder by going to Start -> Run and type %temp%.
2.  Locate the SM_OBS_DLL folder here and delete it.
3.  Uninstall the DI API from Add/Remove Programs.
4.  Reboot your PC
5.  Install the DI API from your current patch. (Download patch, extract it and then browse to Packages\DI API and run setup.exe)
6. Run the Upgrader Common again (From the same patch as above - very important!). Browse to Packages\Upgrader Common and run setup.exe. This will update the SBO-COMMON to this patch level again. You will not lose any data.
The error you see is usually due to a mismatch between your SBO-COMMON and the DI API that is attempting to connect to it. By taking the above steps, you ensure the same patch level is in use.
Regards,
Niall
SAP Business One Forums Team

Similar Messages

  • Obeserver dll version mismatch

    This problem is with a version 2007 application that uses the DIAPI and not the UIAPI.
    On the test system the application connects to the SAPB1 DB and runs perfectly. However, on a different system it fails to connect to the company object and gives the error "obeserver dll version mismatch".
    The two systems seem to be the same as far as versions of OS, SQL Server and SAPB1 are concerned.
    Does any one know what obeserver.dll is and what needs to be done to get the right version.
    Thanks for any help.

    Hi Mel,
    The OBServerDLL.dll file is part of the DI API and is found in the user's SM_OBS_DLL folder in their temp directory. The first thing I would try is to delete this folder and then log in to SBO on that machine:
    On the affected machine
    1) Log out of SBO (other users on other machines can continue)
    2) Choose Start--Run and then type %temp% and click Ok
    3) You should now see a Windows Explorer window with the user's temp directory showing.
    4) Find and delete the SM_OBS_DLL folder
    5) Start SBO and test
    When the user logs back in to SBO and starts any addon that uses the DI API (or runs a third-party application that uses the DI API) then the SM_OBS_DLL folder will be rebuilt and the dll will have the correct version.
    Kind Regards,
    Owen

  • Observer Dll Version Mismatch

    Hi,
    I have a project, which works fine for a client in SAP 2007 PL30.
    I'm trying to connect the same project (in debug mode) to another client, who is in 2007A SP00 PL15.
    But, I'm getting the error - Observer DLL version mismatch, when I'm trying to connect.
    oCompany.SetSboLoginContext(ocookiecontext)
    If oCompany.Connect <> 0 Then
    'Error
    I guess it is something to do with the version of SAPBOUICOM.Dll, SAPBOBSCOM.DLL in my application.
    I tried using both as 2007, also I tried using DI as 2005 and UI as 2007.
    Nothing is working.
    Please help me with this.
    Thanks.
    -Geetha

    Hi Geetha 
    To solve this issue please do the following:
    1.  Go to Start -> Run and type in %temp%.
    2.  Locate the folder SM_OBS_DLL .
    3.  Delete this folder (if you cannot delete it rename it)
    When you connect again the correct version of the ObserverdLL will be
    downloaded from the SBOCommon Database.
    Regards,
    Syn Qin
    SAP Business One Forums Team

  • Observer.dll version Mismatch with DI API when connecting to company

    Please help!
      I recently upgraded to patch 47 from 45, I entered the company through the di api, and I got an error that said something about external component threw an exception, I closed my program and tried to enter again, now I'm getting this Observer.dll Mismatch, when trying to connect to the company.
    I saw another post, and verified the DI API dll SAPbobsCOM with THE SCAB table in SBO-COMMON, and both are 800181.
    Iam using the SAPbobsCOM dll that its under C:\Program Files\SAP\SAP Business One\DI API\2007, although I have to say, I was using another dll from the examples folder in the SDK, when I started getting the error I changed to the one above. Ive tried deleting the SBO-COMMON database and then executing the upgrade patch 47 to rebuild, but Im getting the same error.
    More Info: I took a look at this temp folder:
    C:\Documents and Settings\username\Local Settings\Temp\SM_OBS_DLL\800148
    Ive noticed that the version is diferent, but where does it come from?
    Thank you!
    Edited by: Josu00E9 Inu00E9s Cantu00FA Arrambide on Mar 31, 2009 7:51 PM
    Edited by: Josu00E9 Inu00E9s Cantu00FA Arrambide on Mar 31, 2009 8:02 PM

    My Bad, I was connecting to the wrong server.

  • Error -8003 u201CObeserver dll version mismatchu201D.

    I have an SBO installation sitting on a server called SVR.  The SBO version is 2005 PL44 sitting on SQL 2000 to reflect one of our current customers.   On my laptop I have a VS2005 C# DI-API project that attempts to connect to the companies on SVR.  I also run an SBO installation on my laptop (SBO version 2005 PL50).
    I get the error -8003 u201CObeserver dll version mismatchu201D.
    To try and resolve this I made sure that:
      1. the reference in my C# DI-API project was to a valid SAPbobsCOM2005.dll (i.e. a PL44 version)
      2. I removed %TEMP%/ SM_OBS_DLL so that it would refresh with the Observer.dll from the SVR machine (I think it downloads from SBO_Common on SVR)
      3. I stopped the licensing manager service (set it to manual) on my laptop and rebooted just so I could clear any in process references to my PL50 version.
    I then retried to connect and got the same error. 
    I checked the OBServerDLL.dll that went back into the %TEMP%\SM_OBS_DLL directory and the version was PL44.
    I canu2019t understand why; if I am referencing a PL44 SAPbobsCOM2005.dll in my DI-API C# project, and the Observer.dll that gets loaded from the SVR machine is a PL44 version that I get a version mismatch.
    Does anyone know the reason or can anymore explain the architecture concerning the versioning so I can resolve my issue?
    Thanks

    Thanks Jitin,
    Very helpful but I still have the problem.  I tried the folowing as the link suggested...
    1. Locate the Temp folder by going to Start -> Run and type %temp%.
    2. Locate the SM_OBS_DLL folder here and delete it.
    3. Uninstall the DI API from Add/Remove Programs.
    4. Reboot your PC
    5. Install the DI API from your current patch. (Download patch, extract it and then browse to Packages\DI API and run setup.exe)
    6. Run the Upgrader Common again (From the same patch as above - very important!). Browse to Packages\Upgrader Common and run setup.exe. This will update the SBO-COMMON to this patch level again. You will not lose any data.
    ... which makes a lot of sense - and I would have thought would have solved my problem.  A colleague in the office CAN connect using the same DIAPI application.  He is running a laptop with Version 2007 on it.  Perhaps the major difference in versions is working to his advantage.@^%#$!
    I would like to understand the architecture so I can methodically troubleshhot the process. 
    I have a Backward and Forward compatibility guide that shows the OBServer.dll getting downloaded from the Server and into process memory - but it's a bit lighton detail.
    Are there any more comprehensive documents that can be accessed from SAP or from other sources.  I've been trawling the internet but no cigar as yet...
    Thanks

  • DMM Version Mismatch Error

    I am running a TestStand sequence which makes a call to niDMM_init. Most times this works correctly, but intermittently I get error -1074117853 (every week or so, the function is may be called 50 times between failures)
    "Error, Version mismatch error! Please verify the installation of all NI-DMM components. You may need a newer version of NI-DMM"
    There are a large number of developers here who *may* be using different versions of NI-DMM on theor development machines to what is installed on the Test Rigs. This was my first thought - that perhaps there were some incompatibilities in DLL Ordinals between the various versions of NI-DMM. However, rebooting the rig and running the same sequence again allows it to work. Surely if this was the case - the problem would exist every time?
    Sadly I cant attach the sequence here (since the niDMM_init function is buried inside a code module and a sub dll inside that - but I have traced it through and it is the niDMM_init function returing the error).
    What I need to know is:
    Is there a problem with developing on one driver version and then running with another?
    If all the developers use the same versions of the drivers or at least compile the software with the same version - will this go away?
    Why is the problem intermittent?

    My mistake - posted to the wrong board. Have reposted in DMMs

  • Dblibrary version mismatch error in db02

    Hi SAP Experts,
    I have a problem with My MSSQL cluster system. i get an alerts in my db02 that
    There are different versions of dbmssslib.dll in use
    There are different versions of ODBC32.dll in use
    There are different versions of sqlncli10.dll in use
    I found only one file dbmssslib.dll at kernal directory of CI. I can check version, but i do not understand from where the system compares and says there is a version mismatch? any idea?
    Thanks and Regards
    Syam

    Hi Vineeth,
    Thanks for the direction. Our patch is SAP_BASIS 710. The note is valid for below SAP_BASIS 700 , sp15. I have allocated the point .
    I am checking in all kernal directories for version of the dblibrary files mentioned. We have also traced that CI contains two kernal directories  . One for Intel and other for AMD. CI has got intel processor but appservers got AMD processors.
    Thanks and Regards
    Syam

  • Error -8012 Company version mismatch ?

    Hi.
    When trying to connect using the Company object, the DI API returns "-8012 Company version mismatch"
    Does anybody know what it means, or even better  - know what causes this error?

    Hi Jan,
    Seen your message looks like your DI API is not in the same version as your company is. What Patch Level have you got in your company? You can see it when you choose the company.
    And you can see the DI API version where you have installed it (something like "SAP ManageSAP Business One DI APIDI API 67Object"). Look for the SAPbobsCOM67.dll file and its version in the properties window.
    Regards,
    Ibai Peñ

  • SAP-WXT DLLMajor version mismatch

    Hello:
    I am receiving the following error when using Oracle UPK:
    04/22/13 13:45:34     SAP-WXT DLL     Major version mismatch
    I have SAP GUI 7.30 installed. Will this cause any issues in the development of a UPK Topic?
    Please advise
    Regards,
    Nick

    You can find the latest supported versions of SAP on the UPK Target Applications Technical Specifications, which can be found here: http://www.oracle.com/us/products/applications/user-productivity-kit/upk-target-apps-techspecs-11-101-1728350.pdf
    Best regards,
    Marc

  • Application Error - Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385

    Hi,
    we have one Visual C++ application and this application also using few external dlls. while exiting from application, getting following error. This
    is happened in Windows 7.
    Please help us to resolve this issue.
    Log Name:     
    Application
    Source:       
    Application Error
    Date:         
    28/07/2010 11:44:16 AM
    Event ID:     
    1000
    Task Category: (100)
    Level:        
    Error
    Keywords:     
    Classic
    User:         
    N/A
    Computer:     
    CRIWKS12.crillylaw.local
    Description:
    Faulting application name: WinTest.exe, version: 2.7.1.0, time stamp: 0x4b78d5b8
    Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdaae
    Exception code: 0x0eedfade
    Fault offset: 0x00009617
    Faulting process id: 0x10b8
    Faulting application start time: 0x01cb2df647dfd847
    Faulting application path: C:\Program Files\xxx\xxx\xxx\ WinTest.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: a17377fd-99e9-11df-8941-90fba60d7539
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-07-28T01:44:16.000000000Z" />
    <EventRecordID>3773</EventRecordID>
    <Channel>Application</Channel>
    <Computer>CRIWKS12.crillylaw.local</Computer>
    <Security />
    </System>
    <EventData>
    <Data> WinTest.exe</Data>
    <Data>2.7.1.0</Data>
    <Data>4b78d5b8</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.1.7600.16385</Data>
    <Data>4a5bdaae</Data>
    <Data>0eedfade</Data>
    <Data>00009617</Data>
    <Data>10b8</Data>
    <Data>01cb2df647dfd847</Data>
    <Data>C:\Program Files\xxx\xxx\xxx\ WinTest.exe</Data>
    <Data>C:\Windows\system32\KERNELBASE.dll</Data>
    <Data>a17377fd-99e9-11df-8941-90fba60d7539</Data>
    </EventData>
    </Event>
    PS. I apologise for not being able to provide the application's name.

    Hi Jesse ,
    I am pasting the entire module where the code fails:
    /// <summary>
    /// Pool the job execution status
    /// </summary>
    private void PoolJobExecutionStatus()
    int waitIndex = 0;
    while (true)
    try
    lock (this.lockingObject)
    this.ReOpenRegistryConnection();
    currentJob = SR.Job.Load(this.currentJobId, this.poolingConnection);
    JobStatusEventArgs jobStatusArg = (currentJob.Status == SR.JobStatus.Aborted) ?
    new JobStatusEventArgs(currentJob.Name, currentJob.Status, currentJob.ErrorMessage) :
    new JobStatusEventArgs(currentJob.Name, currentJob.Status);
    this.dispatcher.BeginInvoke(new EventHandler<JobStatusEventArgs>(RaiseUpdateStatus), DispatcherPriority.Normal, new object[] { this, jobStatusArg });
    if (currentJob.Status == JobStatus.Aborted || currentJob.Status == JobStatus.Completed)
    this.PoolJobThread.Abort();
    break;
    catch (ThreadAbortException)
    catch (ConnectionFailure ex)
    TridentErrorHandler.HandleUIException(ex);
    // If reconnection fails more than the max reconnection value then exit.
    if (this.connectionAttempts >= this.maxConnectionAttempts)
    break;
    this.connectionAttempts++;
    catch (BackendStorageException ex)
    TridentErrorHandler.HandleUIException(ex);
    // If reconnection fails 5 times then exit.
    if (this.connectionAttempts >= this.maxConnectionAttempts)
    break;
    this.connectionAttempts++;
    catch (Exception ex)
    TridentErrorHandler.HandleUIException(ex);
    break;
    try
    Thread.Sleep(500);
    // If job is in waiting state, every 3 min show the user retry message.
    // (waitIndex == 360) Specifes 3 min.
    if (currentJob.Status == JobStatus.Waiting && waitIndex == 360)
    waitIndex = 0;
    JobStatusEventArgs jobStatusArg = new JobStatusEventArgs(this.currentJob.Name, this.currentJob.Status, TridentResourceManager.GetString("JobTerminatedByUserMessage"));
    this.dispatcher.BeginInvoke(new EventHandler<JobStatusEventArgs>(RaiseUpdateStatus), DispatcherPriority.Normal, new object[] { this, jobStatusArg });
    catch (Exception ex)
    TridentErrorHandler.HandleUIException(ex);
    waitIndex++;
    public void StartDataProductService(Guid jobId, Connection poolConnection)
    this.currentJobId = jobId;
    this.poolingConnection = poolConnection;
    this.ClearTempData();
    this.HaltService();
    this.PoolJobThread = new Thread(this.PoolJobExecutionStatus);
    this.PoolJobThread.Start();
    Hope this helps
    Regards,
    Rahul

  • Faulting module name: cslibu-3-0.dll, version: 13.0.9.1312

    I developed a C# (Visual Studio) application in .NET Framework 4.0 in conjunction with SAP Crystal Reports Support Pack 9 msi
    The target platform on which reports creating problem is Windows 7 32-bit
    When I generate a report it is generating perfectly but when I try to generate the report again, the application crashes and the following error is logged in the Event Viewer:
    Faulting application name: TrackingApp.exe, version: 1.0.0.0, time stamp: 0x537a1687
    Faulting module name: cslibu-3-0.dll, version: 13.0.9.1312, time stamp: 0x53393fe8
    Exception code: 0xc0000005
    Fault offset: 0x00039a28
    Faulting process id: 0xf00
    Faulting application start time: 0x01cf7376d8df092d
    Faulting application path: C:\Program Files\Tracking System\Tracking System\TrackingApp.exe
    Faulting module path: C:\Program Files\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\cslibu-3-0.dll
    Report Id: 24b4faea-df6a-11e3-8422-d067e51beb2a
    What should be the possible error. My report generation code is written in try catch block but it did not generate any exception but
    crashes my application
    Thanks in anticipation
    Regards
    Adeel Arshad

    Hi Adeel,
    Need more info.
    - What do you mean by generate the report? view, print, export?
    - Does this happen with single, a few or all reports?
    - If the issue is with some reports, what is different ion these reports as compare to other reports?
    - If all reports, could you reproduce the issue with a blank report? and with a report which has a single DB field?
    - Bhushan
    Senior Engineer
    SAP Active Global Support
    Follow us on Twitter
    Got Enhancement ideas? Try the SAP Idea Place
    Getting started and moving ahead with Crystal Reports .NET applications.

  • I have lightroom 5 and  after I just tried to upload my wacom tablet 3 on laptop and, it's not compatable.  The only thing a window box keeps apearing when I open lightroom it say tablet version mismatched.

    I have lightroom 5 and  after I just tried to upload my wacom tablet 3 on laptop and, it's not compatable. I've tried to remove the Wacom program.   Awindow box keeps apearing when I open lightroom it say tablet version mismatched and it completely closes my lightroom on me.  What do I do???  I need my lightroom

    Hi,
    /Users/sarahschadek/Desktop/Safari.app/Contents/MacOS/Safari
    Move the Safari app from the Desktop to the Applications folder.
    Restart your Mac.
    That's why you see this:
    When I try to do the updates my computer says it has ready it goes through like it is downloading them then at the end it says some of the files could not be saved to "/" files.
    After your restart your Mac, click the Apple  menu (top left in your screen) then click:  Software Update ...
    Carolyn  

  • [Solved] sqlite3: SQLite header and source version mismatch

    Is anyone else getting this error?
    $ sqlite3
    SQLite header and source version mismatch
    2009-09-11 14:05:07 b084828a771ec40be85f07c590ca99de4f6c24ee
    2012-03-20 11:35:50 00bb9c9ce4f465e6ac321ced2a9d0062dc364669
    I just performed a full system upgrade
    $ pacman -Syyu
    I tried re-installing:
    $ pacman -Rdd sqlite3
    $ pacman -S sqlite3
    I tried updating the shared library links (as suggested by a post):
    $ ldconfig
    None of the above steps helped...
    $ pacman -Qs sqlite3
    local/sqlite3 3.7.11-1
    A C library that implements an SQL database engine
    $ uname -a
    Linux mdt3 3.2.13-1-ARCH #1 SMP PREEMPT Sat Mar 24 09:10:39 CET 2012 x86_64 AMD Opteron(tm) Processor 6128 AuthenticAMD GNU/Linux
    Last edited by rWarrior (2012-04-25 21:03:38)

    Hi,
    I've got the same problem...
    SQLite header and source version mismatch
    2011-06-23 19:49:22 4374b7e83ea0a3fbc3691f9c0c936272862f32f2
    2012-03-20 11:35:50 00bb9c9ce4f465e6ac321ced2a9d0062dc364669
    Can u tell me how to fix it? This occured when I've unpacked sqlite-autoconf-3071100.tar.gz, entered into unpacked directory with terminal and used commands:
    ./configure
    make
    sudo make install
    sqlite3
    As u've said before the problem is with libsqlite3.so... So i've searched it in File System. And the result is:
    One file with name libsqlite3.so - /usr/local/lib
    Two files with name libsqlite3.so.0 One is here - /usr/local/lib and another here - /usr/lib/i386-linux-gnu
    Two files with name libsqlite3.so.0.8.6 One is here - /usr/local/lib and another here - /usr/lib/i386-linux-gnu
    So... can u tell me which one to delete (in which folder)? What to do next? I am newbie... so if it's possible tell in little steps.
    Thanks in advance.
    Best wishes,
    Teddy.
    Last edited by TeddyRO (2012-04-27 19:57:18)

  • Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e21213c

    Hi,
    Good day!
    I'm having this issue when I just installed an application. I have been searching this kernelbase.dll thing but none of them have fix or any workaround. Hopefully with the great technical guys here can help me with this issue.
    The server is windows 2008 R2
    From the event viewer I got this
    Faulting application name: Tlc.LogManager.Svc.exe, version: 7.0.1.5108, time stamp: 0x51d1ee27
    Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e21213c
    Exception code: 0xe0434352
    Fault offset: 0x000000000000cacd
    Faulting process id: 0x1130
    Faulting application start time: 0x01cf6dbd862da5b1
    Faulting application path: D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Svc.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: fefb5c84-d9b0-11e3-9578-5ef3fcdc0b9f
    Application: Tlc.LogManager.Svc.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.ArgumentNullException
    Stack:
       at Tlc.CapCollector.Common.CapPersistentStateManager..ctor(Tlc.Interfaces.BusinessObjects.IAssetBusinessObject, Tlc.PersistentState.IPersistentStateStore, Tlc.Interfaces.ApplicationLog.IApplicationLog, Int32, Tlc.CapCollector.AgentDiscovery.CapAgentAutoDiscovery)
       at Tlc.LogManager.Lib.ascMan.OnMessageBusStart(Tlc.Interfaces.MessageBus.IMessageBus, Tlc.Interfaces.ApplicationLog.IApplicationLog, Tlc.Interfaces.ApplicationLog.IApplicationLog, Tlc.Interfaces.ApplicationLog.IApplicationLog)
       at Tlc.MessageBus.ActiveMQMessageBus.Start()
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Threading.ThreadHelper.ThreadStart()
    Fault bucket , type 0
    Event Name: CLR20r3
    Response: Not available
    Cab Id: 0
    Problem signature:
    P1: tlc.logmanager.svc.exe
    P2: 7.0.1.5108
    P3: 51d1ee27
    P4: Tlc.CapCollector
    P5: 7.0.1.5108
    P6: 51d1edf4
    P7: f2
    P8: 34
    P9: System.ArgumentNullException
    P10:
    Attached files:
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_tlc.logmanager.s_4d5cd055f698b9b7d9e989629dd2eb52d0be2b_1a6a145b
    Analysis symbol:
    Rechecking for solution: 0
    Report Id: fefb5c84-d9b0-11e3-9578-5ef3fcdc0b9f
    Version=1
    EventType=CLR20r3
    EventTime=130443543988233973
    ReportType=2
    Consent=1
    ReportIdentifier=8c35a7c6-d9a9-11e3-9578-5ef3fcdc0b9f
    IntegratorReportIdentifier=8c35a7c5-d9a9-11e3-9578-5ef3fcdc0b9f
    Response.type=4
    Sig[0].Name=Problem Signature 01
    Sig[0].Value=tlc.logmanager.svc.exe
    Sig[1].Name=Problem Signature 02
    Sig[1].Value=7.0.1.5108
    Sig[2].Name=Problem Signature 03
    Sig[2].Value=51d1ee27
    Sig[3].Name=Problem Signature 04
    Sig[3].Value=Tlc.CapCollector
    Sig[4].Name=Problem Signature 05
    Sig[4].Value=7.0.1.5108
    Sig[5].Name=Problem Signature 06
    Sig[5].Value=51d1edf4
    Sig[6].Name=Problem Signature 07
    Sig[6].Value=f2
    Sig[7].Name=Problem Signature 08
    Sig[7].Value=34
    Sig[8].Name=Problem Signature 09
    Sig[8].Value=System.ArgumentNullException
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.272.7
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=18441
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=3ada
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=3adac3ca3b54f3f7659e16fb4fdadcbe
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=b033
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=b0336032f99007ec98baa22debc5fb25
    UI[2]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Svc.exe
    UI[3]=Tlc.LogManager.Svc has stopped working
    UI[4]=Windows can check online for a solution to the problem.
    UI[5]=Check online for a solution (recommended)
    UI[6]=Check for a solution later (recommended)
    UI[7]=Close
    UI[8]=Tlc.LogManager.Svc stopped working and was closed
    UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
    UI[10]=&Close
    LoadedModule[0]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Svc.exe
    LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
    LoadedModule[3]=C:\Windows\system32\KERNEL32.dll
    LoadedModule[4]=C:\Windows\system32\KERNELBASE.dll
    LoadedModule[5]=C:\Windows\system32\ADVAPI32.dll
    LoadedModule[6]=C:\Windows\system32\msvcrt.dll
    LoadedModule[7]=C:\Windows\SYSTEM32\sechost.dll
    LoadedModule[8]=C:\Windows\system32\RPCRT4.dll
    LoadedModule[9]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
    LoadedModule[10]=C:\Windows\system32\SHLWAPI.dll
    LoadedModule[11]=C:\Windows\system32\GDI32.dll
    LoadedModule[12]=C:\Windows\system32\USER32.dll
    LoadedModule[13]=C:\Windows\system32\LPK.dll
    LoadedModule[14]=C:\Windows\system32\USP10.dll
    LoadedModule[15]=C:\Windows\system32\IMM32.DLL
    LoadedModule[16]=C:\Windows\system32\MSCTF.dll
    LoadedModule[17]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
    LoadedModule[18]=C:\Windows\system32\MSVCR100_CLR0400.dll
    LoadedModule[19]=C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\bc19222db4406c472d9aa1f8b6e0f470\mscorlib.ni.dll
    LoadedModule[20]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\nlssorting.dll
    LoadedModule[21]=C:\Windows\system32\ole32.dll
    LoadedModule[22]=C:\Windows\system32\CRYPTBASE.dll
    LoadedModule[23]=C:\Windows\system32\CRYPTSP.dll
    LoadedModule[24]=C:\Windows\system32\rsaenh.dll
    LoadedModule[25]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System\0f8f78b729ce16dd078f5d5f734a1110\System.ni.dll
    LoadedModule[26]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.ServiceProce#\7b167f31f23d4aed19dfa65ad3d29480\System.ServiceProcess.ni.dll
    LoadedModule[27]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
    LoadedModule[28]=C:\Windows\system32\OLEAUT32.dll
    LoadedModule[29]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.Zip.v5.1.dll
    LoadedModule[30]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.GZip.v5.1.dll
    LoadedModule[31]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.Tar.v5.1.dll
    LoadedModule[32]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.Compression.Formats.v5.1.dll
    LoadedModule[33]=C:\Windows\system32\VERSION.dll
    LoadedModule[34]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Common.dll
    LoadedModule[35]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.FileSystem.v5.1.dll
    LoadedModule[36]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.Compression.v5.1.dll
    LoadedModule[37]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Lib.dll
    LoadedModule[38]=C:\Windows\assembly\GAC_MSIL\VistaDB.4\4.1.0.0__dfc935afe2125461\VistaDB.4.dll
    LoadedModule[39]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Interfaces.dll
    LoadedModule[40]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Enums.dll
    LoadedModule[41]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Core\7a93c267da35a5f16b6fa5a10482eb4e\System.Core.ni.dll
    LoadedModule[42]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Data\5a47dfd0b200a502a4d5d27ee99bcc3c\System.Data.ni.dll
    LoadedModule[43]=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll
    LoadedModule[44]=C:\Windows\system32\WS2_32.dll
    LoadedModule[45]=C:\Windows\system32\NSI.dll
    LoadedModule[46]=C:\Windows\system32\CRYPT32.dll
    LoadedModule[47]=C:\Windows\system32\MSASN1.dll
    LoadedModule[48]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml\5d9f385419332f14eaf937556199856f\System.Xml.ni.dll
    LoadedModule[49]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Dal.LogManager.Client.dll
    LoadedModule[50]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Data.Service#\5ac492f703d6d741140f7cd45ef3c746\System.Data.Services.Client.ni.dll
    LoadedModule[51]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Dal.LogManager.Local.dll
    LoadedModule[52]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Data.Entity\c41b30de7215a62c8ca5bfe6e04ea763\System.Data.Entity.ni.dll
    LoadedModule[53]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.DataAccess.Config.dll
    LoadedModule[54]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Log.dll
    LoadedModule[55]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Utils.dll
    LoadedModule[56]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogMessageClassifier.dll
    LoadedModule[57]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Wintellect.PowerCollections.dll
    LoadedModule[58]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\nsoftware.IPWorks.dll
    LoadedModule[59]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Configuration\11581b5eba4b3ff58441c638ab66c742\System.Configuration.ni.dll
    LoadedModule[60]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Web\7e5af1fdbcffeab8daffc7633f9c337a\System.Web.ni.dll
    LoadedModule[61]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Drawing\1266d26c7b7843d308e2705cb8239d55\System.Drawing.ni.dll
    LoadedModule[62]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\f0acb5c0e7dc2c42c6c61f3aa1278338\System.Windows.Forms.ni.dll
    LoadedModule[63]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.CommonAssemblyInfo.dll
    LoadedModule[64]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_2b24536c71ed437a\gdiplus.dll
    LoadedModule[65]=C:\Windows\system32\WindowsCodecs.dll
    LoadedModule[66]=C:\Windows\system32\shell32.dll
    LoadedModule[67]=C:\Windows\system32\profapi.dll
    LoadedModule[68]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\webengine4.dll
    LoadedModule[69]=C:\Windows\system32\USERENV.dll
    LoadedModule[70]=C:\Windows\system32\PSAPI.DLL
    LoadedModule[71]=C:\Windows\system32\urlmon.dll
    LoadedModule[72]=C:\Windows\system32\WININET.dll
    LoadedModule[73]=C:\Windows\system32\iertutil.dll
    LoadedModule[74]=C:\Windows\system32\SspiCli.dll
    LoadedModule[75]=C:\Windows\system32\shfolder.dll
    LoadedModule[76]=C:\Windows\system32\bcrypt.dll
    LoadedModule[77]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Configuratio#\c080a9ed31f78466f2400bba623af2f8\System.Configuration.Install.ni.dll
    LoadedModule[78]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Web.Services\6cd002594b56953e9c210581e7f3f3cd\System.Web.Services.ni.dll
    LoadedModule[79]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.PersistentState.dll
    LoadedModule[80]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Mitre.CommonEventExpression.dll
    LoadedModule[81]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.ClientServer.Communications.dll
    LoadedModule[82]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Numerics\215d813343ba0950ad6e148e2098018b\System.Numerics.ni.dll
    LoadedModule[83]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Management\da51604aa808b94c181181b37c727078\System.Management.ni.dll
    LoadedModule[84]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.VisualBas#\af08f116e2c31d2c65bd492804fb2fef\Microsoft.VisualBasic.ni.dll
    LoadedModule[85]=C:\Windows\system32\RpcRtRemote.dll
    LoadedModule[86]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\wminet_utils.dll
    LoadedModule[87]=C:\Windows\system32\CLBCatQ.DLL
    LoadedModule[88]=C:\Windows\system32\wbem\wmiutils.dll
    LoadedModule[89]=C:\Windows\system32\wbemcomn.dll
    LoadedModule[90]=C:\Windows\system32\wbem\wbemprox.dll
    LoadedModule[91]=C:\Windows\system32\wbem\wbemsvc.dll
    LoadedModule[92]=C:\Windows\system32\wbem\fastprox.dll
    LoadedModule[93]=C:\Windows\system32\NTDSAPI.dll
    LoadedModule[94]=C:\Windows\system32\mswsock.dll
    LoadedModule[95]=C:\Windows\System32\wshtcpip.dll
    LoadedModule[96]=C:\Windows\System32\wship6.dll
    LoadedModule[97]=C:\Windows\system32\DNSAPI.dll
    LoadedModule[98]=C:\Windows\system32\IPHLPAPI.DLL
    LoadedModule[99]=C:\Windows\system32\WINNSI.DLL
    LoadedModule[100]=C:\Windows\system32\rasadhlp.dll
    LoadedModule[101]=C:\Windows\System32\fwpuclnt.dll
    LoadedModule[102]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Devart.Data.MySql.dll
    LoadedModule[103]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Transactions\122cea70c5d0d591f9af1f4316848fd1\System.Transactions.ni.dll
    LoadedModule[104]=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll
    LoadedModule[105]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Devart.Data.dll
    LoadedModule[106]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\nsoftware.IPWorksSSL.dll
    LoadedModule[107]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Data.OracleC#\850abdea1c65b88ba24a77f0191caea8\System.Data.OracleClient.ni.dll
    LoadedModule[108]=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data.OracleClient\v4.0_4.0.0.0__b77a5c561934e089\System.Data.OracleClient.dll
    LoadedModule[109]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml.Linq\9d14b7bc969452800c0456286309d41d\System.Xml.Linq.ni.dll
    LoadedModule[110]=C:\Windows\assembly\GAC_MSIL\VistaDB.Entities.4\4.1.0.0__dfc935afe2125461\VistaDB.Entities.4.dll
    LoadedModule[111]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.EnterpriseSe#\48264d6ad04173a3a82cc06b70c5cd28\System.EnterpriseServices.ni.dll
    LoadedModule[112]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.EnterpriseSe#\48264d6ad04173a3a82cc06b70c5cd28\System.EnterpriseServices.Wrapper.dll
    LoadedModule[113]=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.Wrapper.dll
    LoadedModule[114]=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Data.Entity\v4.0_4.0.0.0__b77a5c561934e089\System.Data.Entity.dll
    LoadedModule[115]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Runtime.Seri#\08fba6b56d838ad48b4451c82e5728d4\System.Runtime.Serialization.ni.dll
    LoadedModule[116]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.RuleEngine.dll
    LoadedModule[117]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.EventForwarder.dll
    LoadedModule[118]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Lucene.Net.dll
    LoadedModule[119]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.ServiceModel\d072039db89cac96d9e0b1ae9b3a94f4\System.ServiceModel.ni.dll
    LoadedModule[120]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.ServiceModel#\43f892698b9de4d752c13cc2d91ff16d\System.ServiceModel.Web.ni.dll
    LoadedModule[121]=C:\Windows\assembly\NativeImages_v4.0.30319_64\SMDiagnostics\ac74a156499a8303d5788ab299881d5d\SMDiagnostics.ni.dll
    LoadedModule[122]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Runtime.Dura#\2f02efd9ddb7417ffd5c06cfe6e865ca\System.Runtime.DurableInstancing.ni.dll
    LoadedModule[123]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.IdentityModel\33ac21194152cf9a89b82d9cd38b398d\System.IdentityModel.ni.dll
    LoadedModule[124]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xaml\535e182d16212c61bc8b22e0309d3362\System.Xaml.ni.dll
    LoadedModule[125]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Data.Services\84226b67f4623bd3b0dde9aa00c5c88d\System.Data.Services.ni.dll
    LoadedModule[126]=C:\Windows\system32\pcwum.DLL
    LoadedModule[127]=C:\Windows\system32\httpapi.dll
    LoadedModule[128]=C:\Windows\system32\cryptnet.dll
    LoadedModule[129]=C:\Windows\system32\WLDAP32.dll
    LoadedModule[130]=C:\Windows\system32\SensApi.dll
    LoadedModule[131]=C:\Windows\system32\dsrole.dll
    LoadedModule[132]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.MessageBus.dll
    LoadedModule[133]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Apache.NMS.dll
    LoadedModule[134]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Google.ProtocolBuffers.dll
    LoadedModule[135]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\nsoftware.IPWorksSSH.dll
    LoadedModule[136]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Reports.dll
    LoadedModule[137]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\SecureBlackbox.dll
    LoadedModule[138]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.GenericDbLogCollector.dll
    LoadedModule[139]=C:\Windows\system32\ntmarta.dll
    LoadedModule[140]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\perfcounter.dll
    LoadedModule[141]=C:\Windows\system32\pdh.dll
    LoadedModule[142]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\nsoftware.System.dll
    LoadedModule[143]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\diasymreader.dll
    LoadedModule[144]=C:\Windows\system32\aspnet_counters.dll
    LoadedModule[145]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_perf.dll
    LoadedModule[146]=C:\Windows\system32\Secur32.dll
    LoadedModule[147]=C:\Windows\system32\CFGMGR32.dll
    LoadedModule[148]=C:\Windows\system32\security.dll
    LoadedModule[149]=C:\Windows\system32\credssp.dll
    LoadedModule[150]=C:\Windows\system32\schannel.DLL
    LoadedModule[151]=C:\Windows\system32\ncrypt.dll
    LoadedModule[152]=C:\Windows\system32\bcryptprimitives.dll
    LoadedModule[153]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\nsoftware.IPWorksSSNMP.dll
    LoadedModule[154]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Apache.NMS.ActiveMQ.dll
    LoadedModule[155]=C:\Windows\system32\NLAapi.dll
    LoadedModule[156]=C:\Windows\system32\napinsp.dll
    LoadedModule[157]=C:\Windows\System32\winrnr.dll
    LoadedModule[158]=C:\Windows\system32\rasman.dll
    LoadedModule[159]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.CapCollector.dll
    LoadedModule[160]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.CapIDL.dll
    LoadedModule[161]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Dto.dll
    FriendlyEventName=Stopped working
    ConsentKey=CLR20r3
    AppName=Tlc.LogManager.Svc
    AppPath=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Svc.exe

    Hi Ross Rene,
    Sorry for the delay.
    Please make sure the App is compatible with the .Net framework installed, please check the .net version.
    Best Regards,
    Anna

  • Dispatcher not starting up ::Shared library version mismatch

    Hi,
    System is SAP ECC 6.0, AIX and Oracle 10g.
    We upgraded the Kernel Level from 201 to Level 221.
    <hostname>/root$ su - <sid>adm
    [YOU HAVE NEW MAIL]
    .profile[30]: 1:  not found.
    <hostname>:sidadm> disp+work
    disp+work information
    kernel release                700
    kernel make variant           700_REL
    compiled on                   AIX 2 5 005DD9CD4C00
    compiled for                  64 BIT
    compilation mode              UNICODE
    compile time                  Aug 23 2009 20:51:38
    update level                  0
    patch number                  221
    source id                     0.221
    supported environment
    database (SAP, table SVERS)   700
    operating system
    AIX 1 5
    AIX 2 5
    AIX 3 5
    After upgrading the kernel dispatcher is not starting. Kindly find the below error:
    sysno      10
    sid        SID
    systemid   324 (IBM RS/6000 with AIX)
    relno      7000
    patchlevel 0
    patchno    221
    intno      20050900
    make:      single threaded, Unicode, 64 bit, optimized
    pid        778402
    Wed Nov 25 12:20:08 2009
    kernel runs with dp version 243000(ext=110000) (@(#) DPLIB-INT-VERSION-243000-UC)
    length of sys_adm_ext is 576 bytes
    SWITCH TRC-HIDE on ***
    ***LOG Q00=> DpSapEnvInit, DPStart (10 778402) [dpxxdisp.c   1287]
    DwSLCheckVersion: shared library version mismatch:
            shared lib "dw_xml.so" version 201 <-> kernel version 221
            shared lib "dw_xtc.so" version 201 <-> kernel version 221
            shared lib "dw_stl.so" version 201 <-> kernel version 221
            shared lib "dw_gui.so" version 201 <-> kernel version 221
            shared lib "dw_mdm.so" version 201 <-> kernel version 221
    DP_FATAL_ERROR => Version mismatch of dw shared libraries detected. See dev_disp trace for details.
    Set environment variable SAP_NO_SLIB_CHECK=1 to disable version checking.
    DISPATCHER EMERGENCY SHUTDOWN ***
    NiWait: sleep (5000ms) ...
    NiISelect: timeout 5000ms
    NiISelect: maximum fd=1
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Wed Nov 25 12:20:13 2009
    NiISelect: TIMEOUT occured (5000ms)
    ERROR => DpHalt: my PID is not the dispatcher's (778402/0) [dpxxdisp.c   10510]
    Kindly look into the issue. Looking forward for your reply.
    Thanks,
    Soumya

    Soumya Saha wrote:
    ERROR => DpHalt: my PID is not the dispatcher's (778402/0) http://dpxxdisp.c 10510
    The system appears to think that the dispatcher process may already be running. Stop all the SAP processes and run cleanipc to clear out the shared memory. I've seen this on AIX before where the shared memory will prevent SAP from starting back up and clearing these resolved the issue.
    Hope that is helpful.
    J. Haynes

Maybe you are looking for

  • BT Home Hub 3 and Android 4.2.1 WI-FI issue

    Hi, i'm seeing a really annoying issue on my nexus 4 running android 4.2.1. The wireless works perfectly when i am connected at home to the HH3. Everytime i leave the house and go out of the home hubs range, when i return, the BT HH3 shows as "Not in

  • Darwin/BSD problem: won't go back into OS X

    I've seen a number of people have had this problem, but there aren't nearly as many solutions. This is how it happened: I went to my computer, my firefox immediately crashed and then would not open, so I restarted and got a prompt screen saying "Darw

  • IPhoto not launching email when sending photos

    After I select photos to email in iPhoto, I hit the email icon and a new email screen doesnt pop up anymore. It used to launch it correctly w/ the photos attached but it has stopped. Does anyone have any suggestions?

  • Security error when opening a Webi file I saved.

    Here's a strange one - I can log in and see  universes and create queries and save them. When I try to open a query that I saved, I get the message "An error occured while checking the document security.(WIS30902)." This happens even if I chose "Save

  • Unable to download LR4 fully

    Unable to download LR4 fully.  After almost full download (751MB reached) message appears Lightroom_4_LS11.exe couldnt be downloaded. When trying 'Retry' a message partial download appears.  File is saved as 'Lightroom_4_LS11.exe.d507jlj.partial'.  H