Troubleshooting error 99

I was given a used 30D, by my brother who could not get it to work. The original owner didn't know that it wasn't working but it hadn't been used in some time.
- It took one photo with flash for me, and then nothing. I bought and charged a new battery.
- I get error 99 but the message doesn't always show. I now get no shutter action at all.
- All the display and setting functions appear to work.
- When I turn it on, the red light for the chip blinks once.
- Battery reads 7.61V
- I've cleaned the contacts on the battery and in the battery compartment, using alcohol on a wooden stick.
- I also tried a different card. Didn't seem particularly logical but didn't know what else to try!
Because it did take one photo at one time, I've been guessing that everything potentially works but that something isn't getting the voltage that it needs.
Any suggestions?

Before getting deeper into repairs... Have you tried replacing the date/time battery? It's a small, silver battery in a slide out compartment inside the main batteyr compartment of the camera. Those batteries normally have a service life of roughly 5 years, and are relatively cheap, common and widely avalable, and easy to replace. I don't know that a failed date/time battery would cause an Err 99. Usually the only symptom of one is that the camera loses the date/time setting each time you turn it off and back on. Most Canon I've used will shoot fine, even without a date/time battery installed... so this is only a remote possibility, with the problem you're seeing. Have you tried the camera with a different lens? It could be that the fault lies in the lens... Perhaps there's a short or one of it's components is failing and drawing too much power. There are several electromechanical servos and/or motors in most lenses, driving the aperture, focus and IS, if it's a stabilized lens. There are "flex connectors" in most lenses, too, that can crack with age and use, then short out. You didn't mention what lens is on the camera. I've seen certain older third party lenses cause errors and lock up cameras, too. For example, I have an older Sigma 28-75mm that works fine on Elan 7 and EOS-3 film cameras and 10D DSLR, but the moment it tries to focus will immediatly cause any later model Canon body to lock up and throw off an error code. It's probably an issue with the firmware of the lens. Old Sigma are the most common at fault, but some old Tamron seem to do it too. Sometimes the manufacturer will update the lens... but sometimes not. This particular 28-75 is a cheap version and not possible to fix. Have you inspected the memory card socket? Look closely for bent, broken or otherwise damaged pins down in there. Those can cause short circuits in the camera, too. If none of the above helps, but the camera powers on normally (only goes to Err 99 when the shutter is pressed), you also might try "rebooting" the camera. This is much like rebooting a computer. To do this, first turn the camera off, then remove all the batteries (including the small date/time batt), then turn the camera back on and press the shutter release button once. Nothing will appear to happen. The shutter won't actually fire. This is only being done to drain any remaining power from the circuits. Next turn the camera off, reinstall the batteries, turn it back on and then navigate the menu to the date/time. If you got a proper reboot, those should need to be reset. (Other menu and custom function settings may have reverted to factory defaults, too. So check those before starting to shoot with the camera again.) If able to turn the camera on and access it in the menu, you also might want to update (if needed) or reinstall the firmware. A fresh copy of the firmware can be downloaded from the Canon website. It's not difficult, but does have to be done properly, so very carefully follow the instructions you'll find at the Canon website. Neither a reboot nor an update/reinstall of firmware will solve every problem. But, sometimes they do and they are free to try and easy to do yourself. If all else fails, you'll have to find someone who works on 30D to find out if it's worth repairing. Not sure if the Canon Service Dept. still supports the 30D... But, if not, there are some good third party repairers out there, too. I've heard a lot of positibe things about http://www.discountcamerarepair.com/home.html on another forum. There are likely others.... some of which may be close to you (Discount is in Denver, CO). ***********
Alan Myers
San Jose, Calif., USA
"Walk softly and carry a big lens."
GEAR: 5DII, 7D(x2), 50D(x3), some other cameras, various lenses & accessories
FLICKR & EXPOSUREMANAGER  

Similar Messages

  • JPA - TroubleShooting - Error in Datatypes used in Creating Tables

    h1. JPA - TroubleShooting - Error in Datatypes used in Creating Tables
    h2. Error Description
    The error appears when JPA is trying to automatically
    generate tables from Entities. It uses types it shouldn't because they aren't
    supported by the Database Engine. If you examine the createDDL.jdbc file you
    are going to find not supported data types. You could run the statements that
    are listed there directly to your Database Engine and find out that they don`t
    run generating syntax errors like the error posted below.
    h3. Query example (statement)
    CREATE TABLE SEQUENCE (SEQ_NAME VARCHAR(50), SEQ_COUNT NUMBER(19))h3. PostgreSQL Error whent trying to execute the statment
    CREATE TABLE SEQUENCE (SEQ_NAME VARCHAR(50),
    SEQ_COUNT NUMBER(19))": org.postgresql.util.PSQLException: ERROR: syntax
    error near "("
    h3. MSSQL 2000 Error when trying to execute the statement:
    [CREATE - 0 row(s), 0.578 secs] [Error Code: 2715, SQL State: HY000] [Microsoft][SQLServer 2000 Driver for
    JDBC][SQLServer]Column or parameter #1: Cannot find data type NUMBER
    h3. FireBird Error when trying to execute the statment
    Dynamic SQL Error
    SQL error code = -104
    Token unknown - line 1, char 62
    Statement: CREATE TABLE SEQUENCE (SEQ_NAME VARCHAR(50),
    SEQ_COUNT NUMBER(19))
    h2. TroubleShooting
    Looks like it wants "NUMERIC", not "NUMBER".
    [http://www.postgresql.org/docs/8.1/interactive/datatype.html#DATATYPE-NUMERIC]
    I had this problem using Firebird. I found out it had to do
    with the database jdbc driver. I tried using a different database engine, like
    Microsoft SQL Server 2000 with the corresponding driver and it worked as it
    should. I suspect the JDBC driver has to supply in some way the datatypes it
    supports to JPA TopLink Library.
    Edited by: juanemc2 on Apr 1, 2008 7:39 AM

    In Hibernate you can supply the "dialect" to use for SQL generation. I assume TopLink to have a similar functionality.
    This is not a generic JPA issue, but rather something with the specific implementation you're using.
    Or rather it is a generic SQL issue, caused by different database engines using slightly (or not so slightly) different SQL syntax which causes problems when generating SQL automatically.

  • TS3694 how to troubleshoot error code 1015?

    how to troubleshoot error code 1015?...i iwant to update my iphone 3g 8gb to 4.2 ios then suddenly error 1015 just pop up...

    Easy. That error means that your phone is jailbroken. You will have to go elswhere to get help.

  • Exchange CI Troubleshooter error

    Hi all,
    On my Exchange 2010 SP3, I can see several errors "CI Troubleshooter error" indicates that "Get-ExchangeServer is not recognize as cmdlet". This server is monitored by SCOM 2012 R2.
    I found on TechNet it's because "This error occurs when the Exchange Cmdlets snap-in has not been added to the PowerShell instance".
    My question : how could I resolve this issue ?
    Thank you.
    Have a good day.
    FXE

    Hi,
    When you run Get-ExchangeServer command on the server, what is the result?
    Have you followed the link below:
    Before You Import the Exchange 2010 Monitoring Management Pack
    https://technet.microsoft.com/en-us/library/ee758051%28v=exchg.140%29.aspx
    Regards,
    Yan Li
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Windows 7 Troubleshooting Error - 0x8E5E0247

    When I try to troubleshoot my network I keep getting a message:
    An error occurred while troubleshooting:
    A problem is preventing the troubleshooter from starting
    PACKAGE ID: Unknown
    Path: C:\Windows\diagnostics\system\networking
    Error Code: 0x8E5E0247
    Source: Engine
    User: .....
    Context: Restricted
    Can anyone help me with fixing this issue. I am using an ASUS G51J 64 bit machine that came pre-installed with Windows 7 Home Premium.

    Ox8E5E0247
    Do you have a question?
    If so, please repost your query in the more appropriate Windows Community forums here...
    http://answers.microsoft.com/en-us/windows/forum/windows_7-networking
    Karl
    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
    My Blog: Unlock PowerShell
    My Book:
    Windows PowerShell 2.0 Bible
    My E-mail: -join ('6F6C646B61726C406F75746C6F6F6B2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

  • Hard drive replacement with recovery disc problems - Windows Troubleshooter Error 0x8E5E0247

    I have a 2009 Satellite A505 laptop
    64-bit Operating System with Windows 7 Home Premium, 4 gigs of RAM, and Intel Duo CPU, 2.20GHz
    The original Toshiba 500 GB Hard drive finally gave up the ghost and I replaced it yesterday with a WD Scorpio Blue HD Model WDBABC500ANC-NRSN (SATA 8 MB :Mo Cache 5400 RPM)
    Easy, straight forward replacement.  No problems.
    I got out my Recovery Discs which I created using the Toshiba recovery disc utility back in 2009. As I remember, at the time, the process of creating these discs was easy, and it was the first thing I did after registering my computer.
    The process created 5 discs, which the last, number 5, is the Applications and Drivers.  I have done this process before on other computers (Gateway and Toshiba) and it is usually pretty straight forward and problem free.
    Not so this time, and have to wonder about the Toshiba Recovery Discs that were created!  Why aren't these working correctly?
    I followed the normal process to boot the new Hard Disc on the DVD Recovery Disc 1, and everything seemed to work normally.  I followed every "next" prompt, and installed each new Disc 2, and 3 as prompted.
    After Disc 3, it said it was finished, and then went throught the Toshiba unpacking and the Windows installation process with multiple re-starts and Window start ups.  Again, everything seemed normal, except I wondered why I never received a prompt for Dsc 4 which was unused in the recovery process.  Is that normal? 
    During the Toshiba automatic unpacking and installation process, where various drivers were being installed, Windows errors began returning that said something like this, "Windows requires a digitally Signed driver, and the driver is unavailalbe and could not be activated in Windows 7 . Programs relying on them may not work. "  
    The problem drivers included the Realtek RTL8191 SE Wireless Lan 802.11n PCWE, the Richo pcle memory stick, Realtek High Definition Audio, Video Controller, Richo PCLe SD/MMC Host Conroller. and a few others....
    I did not touch the keybroad or intervere in anyway, and let the installation process proceed until everything was installed.  I then went through the first Windows start up process where you set the region, time and create the USER ID, set the adminstrator rights and even got the Toshiba Registration prompt.
    When finished, I noticed that the sound was not working, nor was the Wireless Network Connection, and when I attempted the usual Windows network Trouble Shooting process, it returned a Windows Error which said "A problem is preventing the troubleshooter from starting"  
    I then viewed the error details.  They said...
    Package ID:  Unknown
    Path:           C:\windows\diagnostics\system\networking
    Error Code:  0x8E5E0247
    USER:          mvh-PC\mvh
    Context:      Restricted
    I then went to MS Windows 7 Troubleshooting forum on the internet using another computer. 
    I followed all the 'cmd' processes for "supposedly" solving these problems by running System File Checker [SFC] scan on the computer which was supposed to replace the missing or corrupt files.
    Well, no joy.  The issue presists.
    After some problems accessing the CBS log, I was able to view it, and it provides no useful information as to why the errors where unable to be corrected.  
    I tried following everything on this MS How to Use File Checker document:
    In my CBS file I got a lot of SQM  "Failed to start" and "Failed to read" and "Failed to upload" and CSI "Repair results created"....
    but did not get any "Cannot repair member file" type of messages to use the 'cmd'
    takeown /f Path_And_File_Name function 
    I then started over.  Rebooted the computer again, starting with Recovery Disc 1 and several hours later was back to the same problem.  Geeze
    I have checked all the various Device drivers that are shown as not working in the Device Manager.  I have tried uninstalling them all, and then re-installing them both automatically during Windows 7 start up, and also from the Recovery Disc 5 which had the original drivers.  Nothing works.
    When I clicked on "Connect to the Internet" on the Windows Control Panel, I am returned a prompt that says "Windows did not detect any networking hardware" and so,even with a direct Ethernet connection to my cable modum, I was unable to download any Windows updates or new drivers to see if that fixes anything.
    I am stumped. 
    Any suggestions out there?  I don't want to waste a lot of money paying for more technical help for an aging laptob.  If this is beyond a simple fix, then I think I will just go and buy a new cheap computer from Asus having wasted the ~$70 bucks for the hard drive for this one.  
    It shouldn't be this hard, should it?  
    I have considered buying new recovery discs directlly from Toshiba, but if the process that came with the computer can't create correct discs that work the first time, what promise do I have that another $29.95 won't just be a waste of money too?
    Thanks for any helpful hints about what I may be missing or overlooking.   
    Regards
    Marvin Van Horn
    Solved!
    Go to Solution.

    Jerry...
    I think we can close this one out as 95% solved.  I did get the Intel (R) Rapid Storage Technology loaded after installing the Intel (R) Chipset Software Installation Utility.   The instrustions were not the simpliest for the novice, and it took me a while to figure out if my system was running in RAID or ACHI mode.  I decided that it was ACHI, so could proceed, even though I did NOT find this information in the Device Manager where they said I should have...
    Also, it was a little confusing on the Intel site which file to download.  I first did the zip file, (f6flpy-x64.zip) but could not figure how to execute it or put it on a disc, so downloaded the (iata_enu.exe) and hope it was the right one for a 64 bit system.  
    Anyway, I am now connected via Ethernet cable to my modem, and down loading 126 Windows Updates which should take a while.
    My only other issue, that I am aware of is that I do not seem to have any Wireless Lan software, and even though I have added Lan drivers via the recovery Disc, they do not show up anywhere.. Will have to figure out what is going on here, and why it isn't working...
    Maybe it is related to something in the Device Manager called
    "Other Devices"  Under that I have 4 items not working.  They are listed like this...
           Base System Drive,
           Base System Drive (a duplicate?)  
           Network Controller
           Video Controller.  
    I have tried uninstalling them, and allowing Windows to reinstall, but they still are not activated.  Not sure what this is for, and how to update it, but will search some more on another forum thread for these issues.  Maybe I will try again after all my Windows updates are done and see what happens.  
    Thanks again for your help.  If you have any other insights on the Wireless issue, that would be great.  It is turned on, but in the Windows tray, I only get the Ethenet Icon option, and it does not see or present wireless connection options like before.  I am sure this is something simple.  
    cheers
    mvh

  • [Forum FAQ] Troubleshooting error "The specified SQL server instance is not valid" when installing SCOM reporting service

    Symptom
    If you have failed to install SCOM reporting service, you may encounter below error when you reinstall it:
    “The specified SQL server instance is not valid”.
    (Figure 1)
    Figure 1.
    Reason
    This issue may be caused by multiple reasons, for example the reasons in Figure 1.
    However, you may find that SSRS and Report Server website are configured correctly and no SSL or proxy Server is used. In these scenario, you can open the log file under path
    to find the root reason:
    C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\LogFiles
    Later, you will find the error as below:
    ERROR: Throwing Microsoft.ReportingServices.Library.ReportServerDisabledException: , Microsoft.ReportingServices.Library.ReportServerDisabledException:
    The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content. ---> System.Runtime.InteropServices.COMException
    (0x80090016): Keyset does not exist (Exception from HRESULT: 0x80090016)
    at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
    at RSManagedCrypto.RSCrypto.ReencryptSymmetricKey(Byte[] symKeyBlob, Byte[] pPublicKeyBlob)
    at Microsoft.ReportingServices.Library.ConnectionManager.<GetEncryptionKey>b__2()
    --- End of inner exception stack trace ---;
    Solution
    According to the error message, you can delete encrypted content by following the steps below:
    Open SQL Reporting Services Configuration Manager.
    Select “Encryption Keys”.
    Click “Delete” to delete all encrypted content. (Figure 2)
    Figure 2.
    After that, we can install SCOM reporting service again, after successfully install reporting service, we should see the SCOM operation console as below:
    Figure 3.
    In addition, you may also encounter other errors when installing SCOM reporting service, and the troubleshooting steps may be different. However, we can also check SQL reporting
    service logs to find the root reason.
    Here are some articles that would be helpful for SCOM reporting service installation and troubleshooting:
    How to Install the Operations Manager Reporting Server
    http://technet.microsoft.com/en-us/library/hh298611.aspx
    Unable to install SCOM 2012 Reporting Services
    http://blogs.technet.com/b/mdegre/archive/2013/05/27/unable-to-install-scom-2012-reporting-services.aspx
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Hello,
    I'm afraid you must use a dedicated instance of SQL Server for each site(SCOM/SCCM). Some similar issues were disscussed on this forum:
    SCCM and SCOM - SQL Server 
    http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/bfa14da9-4692-4c64-a107-e085c967d259
    SCOM, SCCM, SQL on same server?
    http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/b5373aa7-5233-4b1f-9b39-b86e481e04d5
    Thanks,
    Yog Li
    TechNet Community Support

  • Windows Media Player Error; Troubleshooting Error

    Question #1
    When I try to play music in windows Media Player I get the following message:
    Windows Media Player cannot play the file because there is a problem with your sound device.  There might not be a sound device installed on your computer, it might be in use by another program, or it might not be functioning properly.
    The sound was working about a week ago, and I do have IDT High Definition Audio CODEC driver on my laptop. 
    Question @2
    When I run any Troubleshooting program I get the following error code:
    Pkg ID: AudioPlaybackDiagnostics  (This varies depending on what I'm troubleshooting)
    Path: Unknown (This varies)
    Error Code:  0x8E5E0247  (This error code is always the same)
    Source:  Engine
    User: Leyna-PC\Leyna
    Context:  Elevated  (This is usually restricted)

    Hi Mike,
    Try the following.
    Download the IDT Audio installer on the link below and save it to your Downloads folder.
    http://ftp.hp.com/pub/softpaq/sp63501-64000/sp63555.exe
    When done, open windows Control Panel, open Device Manager and open up Sound, Video and Game Controllers.  Right click the IDT device and select Uninstall - you should also get a prompt to remove the current driver, tick the box to allow this and then proceed with the uninstall.
    When done, download and reinstall the Chipset driver on the link below.
    Chipset Driver - Windows 8.1
    When complete, shut down the notebook by holding down the Shift key as you click Shutdown to temporrily prevent a hybrid boot.
    Start the notebook and let Windows fully load - it will automatically load an audio driver, but just let this complete.  Then open your Downloads folder, right click on the IDT installer and select 'Run as Administrator' to start the installation.  When this has completed, right click the speaker icon in the Taskbar and select Playback Devices.  Left click 'Speakers and Headphones' once to highlight it and then click the Set Default button - restart the notebook and try playing the mp3 file.
    Regards,
    DP-K
    ****Click the White thumb to say thanks****
    ****Please mark Accept As Solution if it solves your problem****
    ****I don't work for HP****
    Microsoft MVP - Windows Experience

  • Troubleshooting Error 0x70080035 when accessing NAS

    I posted this issue on the Microsoft Community forum and they recommended that I post my query in the TechNet forum.
    In summary, here is my tale of woe:
    As of last weekend, I can no longer access my Buffalo Linkstation NAS from my laptop with Windows 8.1 over wifi. I upgraded to Win 8.1 several months ago and everything has been working just fine until a few weeks ago (March 23). The problem is that the
    NAS appears by name in the network, but when I click on it it cannot be found and I get error 0x80070035, path not found. After spending several days looking for a solution, I restored my laptop to a restore point about two weeks earlier and everything started
    working again. It's been working fine until this weekend (April 5), now the same problem is back.
    I can browse it via its IP address, I can access the DHCP table in my router (Linksys WRT54G) and I can see the Linkstation listed there. I turned off my firewall (Symantec Endpoint) and I still get the same results. The Linkstation does show up as a media
    device and I can access all of my media.
    I can ping the NAS using its IP address, but if I ping it using its hostname, it cannot find it. I get the same results when I plug my laptop into the router. I can ping the NAS hostname from my Windows 7 PC without any problems. I can also browse my PC
    from the laptop without any problems. DHCP for the NAS just doesn't work on the laptop. Since I can ping the NAS via its IP address but not its name, my laptop has a DNS problem. Any troubleshooting help would be greatly appreciated.
    It was suggested that I try the following suggestions but nothing here worked:
    http://social.technet.microsoft.com/Forums/windows/en-US/17c9ea7d-52df-4ef9-95fa-0a961d11bfa3/fix-for-cannot-access-nas-drives-sharefolder-is-not-accessible-or-error-code-0x80070035?forum=w8itpronetworking
    If this helps, here is what I get from IPCONFIG /ALL:
    Windows IP Configuration
       Host Name . . . . . . . . . . . . : laptop
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Peer-Peer
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
    Wireless LAN adapter Local Area Connection* 4:
       Media State . . . . . . . . . . . : Media disco
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft H
       Physical Address. . . . . . . . . : 24-FD-52-13
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    Wireless LAN adapter Local Area Connection* 2:
       Media State . . . . . . . . . . . : Media disco
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft W
       Physical Address. . . . . . . . . : 24-FD-52-13
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    Wireless LAN adapter Wi-Fi:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek RTL
    I-E NIC
       Physical Address. . . . . . . . . : 24-FD-52-13
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.1.1
       Subnet Mask . . . . . . . . . . . : 255.255.255
       Lease Obtained. . . . . . . . . . : Friday, Apr
       Lease Expires . . . . . . . . . . : Sunday, Apr
       Default Gateway . . . . . . . . . : 192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 68.94.156.1
                                           68.94.157.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter Ethernet:
       Media State . . . . . . . . . . . : Media disco
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Qualcomm At
    ernet Controller (NDIS 6.30)
       Physical Address. . . . . . . . . : 00-8C-FA-4B
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter isatap.{F28B5C86-CBDC-49F9-9C01-FF4
       Media State . . . . . . . . . . . : Media disco
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft I
       Physical Address. . . . . . . . . : 00-00-00-00
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter Local Area Connection* 14:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunn
       Physical Address. . . . . . . . . : 00-00-00-00
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:5ef5
    erred)
       Link-local IPv6 Address . . . . . : fe80::10b2:
       Default Gateway . . . . . . . . . : ::
       DHCPv6 IAID . . . . . . . . . . . : 167772160
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Here are the tracert results for the Win 8.1 Laptop and Win 7 desktop:
    Tracert results for Laptop w/Windows 8.1:
    Microsoft Windows [Version 6.3.9600]
    (c) 2013 Microsoft Corporation. All rights reserved.
    C:\Users\bill>tracert 192.168.1.113
    Tracing route to LS-XHL25B [192.168.1.113]
    over a maximum of 30 hops:
      1     2 ms     2 ms     1 ms  LS-XHL25B [192.168.1.113]
    Trace complete.
    C:\Users\bill>tracert LS-XHL25B
    Unable to resolve target system name LS-XHL25B
    Tracert results for Desktop w/Windows 7:
    C:\Users\Bill>tracert 192.168.1.113
    Tracing route to LS-XHL25B [192.168.1.113]
    over a maximum of 30 hops:
      1    <1 ms    <1 ms    <1 ms  LS-XHL25B [192.168.1.113]
    Trace complete.
    C:\Users\Bill>tracert LS-XHL25B
    Tracing route to LS-XHL25B [192.168.1.113]
    over a maximum of 30 hops:
      1    <1 ms    <1 ms    <1 ms  LS-XHL25B [192.168.1.113]
    Trace complete.

  • Troubleshooting "error generating preview" in Installer

    From time to time, I have run into this maddening condition where I build an installer and it will not run because it reports “error generating preview” errors on the EXE for which I am trying to build the installer.  Most often, I can build the EXE just fine, without errors.  The run button does not show any problems, and the application EXE runs without issue.  When I try to build the installer, I get the error.  I have scoured NI’s web site and find many people with this problem, loads of “try this” type advice, and reports of “I fixed it” that often don’t make any sense.  It is nearly impossible to troubleshoot this problem in an orderly, sensible way.  Sure there are some build log files that can be activated, and you can look through them, but rarely is there anything “telling” in these rather verbose dumps (if they are created at all).  How is it that the Installer builder can notify me that there is an “error generating preview”, but cannot point me at the source of the error?!  How insane is that?
    I would like to put out a passion plea to National Instruments Engineering, or to one of you many LabVIEW community gurus’s to provide some detailed instructions for diagnosing, finding, and fixing these vexing errors.  Can someone please write up some sort of step by step for this diagnosis?
    The second thing I would love is for NI to report more detail in the Installer builder as to what is causing the error.  Telling me there is an error (that you just found) but keeping the issue a secret does not help me get my job done.
    If there is already a detailed step-by-step guide for diagnosing and fixing these issues, I apologize for this post and would be very grateful if someone would kindly point me to this oracle of wisdom.
    Thanks,
    -cb

    Greetings Community,
    Just circling back to report out on what I did to get my install build to work again.  This list contains things that *probably* fixed this issue on my system, although it is a bit of a mysterious issue so somewhat hard to nail down.  Anyway, these comments may help someone some day.
    What might prevent the build of an installer
    You have a VI in a Dialog Disable Structure that has a problem.  It could be a broken VI or a left-over VI that points to a VI that no longer exists.  Whatever the problem, just because it is "commented out" does not mean that the compiler will ignore it.  By the way National Instruments, I think this is a bug.  Why does the compiler try to process things that are commented out?
    You have a String that is wired to the selector of a Case Structure.  I ran into this once.  I could not build the installer.  Somehow I found a reference online where someone commented on this being an issue.  I found my problem VI, replaced the string with a typedef into the selecter and poof, it worked again.
    You have a hard-coded path reference in your VI that points to a directory that does not exist (invalid path).  In my case recently, I had a string with a path wired into a build path reference.  The directory was used elsewhere to open VI's on the fly.  For some reason this was OK with the EXE builder, but not OK with the installer builder.
    Here is a "gotcha" - if you move a LabVIEW project to another directory, the installer forgets all of the file dependencies you have created in the installer setup.  When I get a new version of LV, I create a LV project directory called "LabVIEW 2013" and move my previous (and still active) projects into that directory.  I know this seems kind of dorky, but it helps me keep things straight.  When I move my projects, the installer break.  Trying to re-construct the build settings has been troublesome and can lead to odd "error generating preview" messages because something wasn't re-built correctly.
    Well, that's what I know.  The F2 patch for 2013 did not fix my most recent problem, #3 above did.  If anyone finds other build issues to look for while troubleshooting, can you please post to this thread?
    Thanks,
    -cb

  • Network Troubleshooting Error 0x8E5E0247

    Hi I have a Sony VAIO S Series VPCS117GA Laptop with Windows 7 installed on it.
    Recently, I encountered a problem while connecting to an already existing WIFI network.
    It was working fine until a few days back. But now I can't connect to it.
    When I try to troubleshoot the error, it says "A problem is preventing the troubleshooter from starting"
    Package ID : Unknown
    Path : C:\Windows\diagnostics\system\networking
    Error code : 0x8E5E0247
    Source : Engine
    User :
    Context : Restricted
    What should I do to solve this problem?
    I have tried every thing I could. Still there seems to be no solution to this.
    Please help.
    Thanks in advance

    Hi,
    Have you checked the below articles?
    Use Network troubleshooter event logs to solve network problems
    Wired and wireless network problems
    Please take a try with the suggestions mentioned and if possible upload us the event log for the network errors.
    Best regards
    Michael Shao
    TechNet Community Support

  • Troubleshoot Error - Unable to perform table-based value assignment config

    After to creating class, characteristics, and value assignment type, the system is unable to perform table-based value assignment configuration. The following error is displayed:

    Hi Mr. SAP,
    Based on the diagnosis, you can figure out that most likely someone is already editing the customizing table or might you are not authorized..
    In case if you have the access to SM12 Transaction code, kindly check if an entry present there. If yes it means the table is locked and you can't proceed on that. you have to reach out to the specific resource to unlock the table who did a lock, else you need to reach out to BASIS to make that entry delete.
    Regarding authrization for locking of table, please check SU53 after the execution of the T-code, if you are missing any role. If you find anything there, then reach out to your Security team to get and assigned roles to your profile.
    Regards,
    Abhi

  • [ForumFAQ]How to troubleshoot error "SSPI handshake failed with error code 0x80090324"

    Understanding the problem:
    When connect to SQL Server with Windows authentication, you may receive the following message in the SQL Server error log:
    SSPI handshake failed with error code 0x80090324, state 14 while establishing a connection with integrated security; the connection has been closed.
    Security Support Provider Interface (SSPI) is a set of Windows APIs that allows for delegation and mutual authentication over any generic data transport layer, such as TCP/IP sockets. SQL Server supports Kerberos indirectly through the Windows Security Support
    Provider Interface (SSPI) when SQL Server is using Windows Authentication.
    "SSPI Handshake Failed" error happens usually when connection failed between the server and domain controllers or failed Kerberos Authentication. There are many reason for SSPI Handshake error to appear in SQL Server error log.
    Troubleshot the problem:
    Download and install the Windows error code lookup tool Err.exe to view error descriptions for Windows Error Codes.
    The error code 0x80090324 (SEC_E_TIME_SKEW) means "clock on client and server machines are skewed". In most case, this is a Kerberos issue. Kerberos is using a timestamp to protect against replay attacks. The maximum time skew that can be tolerated
    between a ticket's timestamp and the current time at the KDC is 5 minutes by default.
    Also check the Windows Event Log of client machine, domain controller and the SQL Server machine for existence of W32time error messages.
    The solution:
    Make sure the clock of client server, domain controller and the server running SQL Server are within five minutes of each other. Or Resynchronize the clock by run w32tm /resync on client machine and SQL Server machine.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    This error can happen due to Active Directory configuration issue or Network related issues. Assuming they are fine,
    another reason could be related to fail Kerberos Authentication to connect to SQL Server.
    In Windows 2003 and above, the default method of establishing a connection is Kerberos but if it fails, then connection may be established using NTLM. An error may be registered on SQL Server error log due to Kerberos failure.
    To confirm if you have any database connection using Kerberos authentication, run this on your SQL Server
    SELECT distinct auth_scheme FROM sys.dm_exec_connections
    If you only see NTLM and SQL then, there is no Kerberos connection.
    To use Kerberos, the client and SQL Server must be in the same domain or trusted domains and a Service Principal Name (SPN) must be registered with Active Directory for SQL Server service account.
    You can check if the service account already has SPN, by running this on the SQL Server
    setspn -l <domain\sqlserviceaccount>
    If you don't see anything starting with MSSQLSvc\ then the account is not setup with SPN.
    You can manually register SPN as a Domain Administrator using these commands.
    To      create an SPN for the NetBIOS name of the SQL Server use the following      command:
    setspn –A MSSQLSvc/<SQL Server computer name>:1433      <Domain\Account>
    To      create an SPN for the FQDN of the SQL Server use the following command:
    setspn      -A MSSQLSvc/<SQL Server FQDN>:1433 <Domain\Account>
    If SQL Server service account is granted "Validated write to service principal name" privilege in Active Directory, SQL Server database engine will register itself when it starts and unregisters at shutdown. If you Domain Administrators do not permit this setting
    then you should manually register the SPN and the SSPI error will go away.
    Also the SQL Server service account must be granted "Account is trusted for delegation" privilege in Active Directory. If your SQL Server connects to other SQL Server using Linked Server then the server must also be granted "Trust this computer for delegation
    to any service" privilege.
    For a named instance, you can use the FQDN of the named instance instead of SQL Server FQDN and use the port number.
    For a clustered server, you should use the FQDN of the SQL Server virtual name. In this case you will need two entries, one with port name and one without such as
    setspn -A MSSQLSvc/<Virtual SQL Server FQDN> <Domain\Account>
    setspn -A MSSQLSvc/<Virtual SQL Server FQDN>:1433 <Domain\Account>
    Kerberos authentication works when SQL Server, Service Account and Windows account accessing the SQL Server are in same windows domain. If anyone these are in different domain, there must be bidirectional trust established between the domains, otherwise it
    does not work.

  • Troubleshooting Error: 942, Severity: 14, State: 4

    Hi all,
    I'm in the process of decomission an old SQL Server 2000. I'm migrating the databases hosted in that instance one by one. I have managed various workaround to handle the changed server\instance name. When I complete the process for one database, I put it
    offline in the SQL 2000.
    I've a trouble with one database, when I put it offline I see into the profiler a lot of error like this (1 error every 1 seconds):
    Error: 942, Severity: 14, State: 4
    For what I know this error is because somthing is trying to access a database that is inaccessible (in my case offline) but I can't figure from which client the request came!
    Please help!

    Hello,
    If you have the Audit Database Management event selected on Profiler then that error is expected whenever a database if offline.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • How do I troubleshoot Error: 150: 30 on OS X 10.8?

    Online instructions provide guidance in trouble shooting Error 150: 30 ("Licensing for this product has stopped working) for Mac OS X 10.7.  It does not work on Mountain Lion (10.8).  Incredibly frustrating.  Any suggestions>

    I went through the steps indicated on http://helpx.adobe.com/x-productkb/global/error-licensing-stopped-mac-os.html, including going deleting the FlexNet Publisher folder and proceeding to the step of adding the commands in the Terminal program (since the LicenseRecoveryProgram does not work in the native 10.8 environment).  I type the command line, dragged the app into the Terminal window and hit return.  I was prompted for my administrator password and entered it.  After that, nothing; no prompt windows, nada.  I pulled up my Force Quit Applications window and saw that the LicenseRecoveryProgram was not responding.  Rather than pull out a pistol and shoot the computer, I posted the question here.

Maybe you are looking for