Header-Flash

Pages

Showing posts with label error. Show all posts
Showing posts with label error. Show all posts

Sep 24, 2011

Fix: Error: Windows - Low On Registry Space : The system has reached the maximum size allowed for the system part of the registry. Additional storage requests will be ignored.

Symptoms:
On a Windows  XP or Windows  2003  Server you get a warning window giving you the following error message :

Window Title :      Windows Low on Registry Space
The system has reached the maximum size allowed for the system part of the registry  Additional storage requests will be ignored.


Problem: 
The main cause is that Windows page-file is corrupted. 
This problem seems to occur in the following circumstances :
– After the installation of Service Pack 2 on Windows 2003 servers.
– After a change of hardware
– And by far the most common occurrence that we have seen is when a change of antivirus software, or a major update to antivirus software, is performed. For example, upgrade from ESET NOD32 v4.2 to v5.0.

For anyone else experiencing this specific “Low on Registry Space” error who does not fall in either of the above two categories, the corruption may have occurred during a power surge or power cut (if your PC is not protected by a UPS), or during a freeze of your PC/server, or, lastly , your hard disk may be going bad and starting to corrupt files and the paging file (if you think it may be the latter, monitor the situation carefully – check, in particular, for NTFS errors in the System log of the Event Viewer).

Solution:
  1. Go to the Control Panel.
  2. Open the System icon.
  3. Choose the Advanced tab.
  4. Click  Settings in the  Performance  sub-section.
  5. Choose the Advanced tab.
  6. Click  CHANGE in the Virtual Memory section.
  7. Choose the Advanced tab.
  8. Click  CHANGE  in the  Virtual Memory section. You will now see that the paging file has a zero size (shown at the bottom under "Currently allocated")
  9. Change the paging file setting to System managed size.
  10. Click  SET.
  11. Click  OK.
  12. At this point you may be asked if you want to overwrite the old paging file  - Answer YES !
  13. Click OK all the way out back to the Control Panel.
  14. You may or may not be asked to reboot your computer.  Reboot anyway.
That’s it.

Mar 21, 2011

Fix: IE8 Warning ‘Do you want to view only the webpage content that was delivered securely?’

When browsing to secured sites using IE8 you get this warning:

‘Do you want to view only the webpage content that was delivered securely?’


How to Fix:

  1. Going  to Tools->Internet Options->Security
  2. Select the ‘Security’ tab
  3. Click the ‘Custom Level’ button
  4. In the ‘Miscellaneous’ section change “Display mixed content” to Enable

Mar 20, 2011

Avid: Error "Assertion Failed: objh == br-> anchorObjh"

"Assertion Failed: objh == br-> anchorObjh"
"File: ..\..\..\MediaComposer\Bin\binQuiklook.c, Line: 322"

* the path and number could be different

When working on Avid Media Composer you get errors like:
Try these steps:

1. if the project was created using an older Avid from the one you work on, create a new project and import your data into it.

2. in the bin window try working in "Text Mode" instead of "Script" mode.

Feb 16, 2011

Fix: Avid Error: "The application binary file has been corrupted, please reinstall the system"

Error:
Error when loading project in Avid MC saying:
"The application binary file has been corrupted, please reinstall the system"

The cause for the problem is Bin's created in earlier version of Avid such as Avid Express Pro.


Solution:

The Avid Media Composer does not like the bins created under Avid Xpress Pro. Sure it is smart to create a new project and new user settings (and clean site settings, delete msm files etc...)  but the REAL trick here is make completely new bins with slightly different names. e.g. for an old bin called 
make a new bin called somethiing like
. Do this for all your bins. Move the clips and sequences out of the old bins and into the new ones, then delete the old. The error message will be cured. 
Personally, I was also getting an error message on launch of MC saying . The problem here is that Avid is moving to a different type of graphics architecture which uses a different method of video overlay. The bottom line is that while I am using an HP Compaq nx9600 notebook (Avid qualified and recommended (and supposedly supported ) at the time of writing) however there is something about the way the ATI X600 graphics card inside handles things that bumps up against the latest Avid software. But there is a solution. Yea! Firstly, Launch Media Composer while holding down the L and O keys. This puts the Avid software into legacy overlay mode, making it compatible with the ATI card. There will be no error message. Once up, open the console and enter
legacyoverlay on
This will cause the setting to be retained for subsequent sessions and the error will continue to be gone.
The ATI card in my notebook is non-upgradeable. But if you run into this one on an upgradeable PC and you do later install one of the recommended nVidia cards, you will just need to take another trip to the console and type
legacyoverlay off
Before I found these fixes out I did yet another rebuild of my OS from the ground up. Didn't help a smidge. Hey, Doc Avid, don't you treat me! You gotta get the prescription right my friend. If you are going to throw out random suggestions, stick with the basics, like rebuilding settings files. Don't suggest tearing down the house unless you know what you are talking about. please! (Sorry for coming on a little strong here. I do not mean to be rude. But it is frustrating to follow advice to rebuild your entire OS and then discover that had no connection with the issue)
Credit:

Feb 13, 2011

Error opening attachments in Outlook saying "Access Denied" & Check Permissions


Hebrew Error:
"אין אפשרות ליצור את הקובץ: filename.tif. לחץ באמצעות לחצן העכבר הימני על התיקייה שבה ברצונך ליצור את הקובץ ולאחר מכן לחץ על 'מאפיינים' בתפריט הקיצור כדי לבדוק את ההרשאות שלך עבור התיקיה."
When opening an attachment directly from within Outlook you could get an error message saying that it can’t create the file and to that you need check the permissions on the folder you want to save it in. In most cases the permissions on the folder isn’t the issue but the fact that the folder is "full". When you open an attachment directly from within Outlook it will first save a copy to a subfolder of the Temporary Internet Files folder. Cleaning out the folder will solve the issue.

The special folder where outlook temporarily saves the file for opening is listed in the registry.

Locate the folder path:


Outlook 97 HKEY_CURRENT_USER\Software\Microsoft\Office\8.0\Outlook\Security
Outlook 98 HKEY_CURRENT_USER\Software\Microsoft\Office\8.5\Outlook\Security
Outlook 2000 HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Outlook\Security
Outlook 2002/XP HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security
Outlook 2003 HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security
Outlook 2007 HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Security

Go to the folder:

  1. Open the OutlookSecureTempFolder registry key from the location provided in Step 1.
  2. Copy the path from the key.
  3. Open Explorer
  4. Paste the address in the Address Bar and press Enter 
  5. Empty the folder.
To make things easier you can use this cool tool from HowTo-Outlook.com.
The tool allows you to:


  • Easy access to Outlook's SecureTempFolder used for opening attachments




  • Determination of the current size of the folder




  • Empty the folder




  • Command line options to run as a Scheduled Tasks and logon/logoff scripts.




  • Nov 18, 2010

    Fix: Windows 7 Activation Error saying the Product Key you entered can be used only in certain countries or regions

    Problem:
    When you try to activate you geniune license you receive an error saying:

    "the product key you entered can be used only in certain countries or regions. Either activate windows where you bought it or buy a new product"

    Cause:
    This behaviour is related to licenses sold in developing markets such as southeast asia, south America and more. Microsoft's activation server is geographically oriented and cannot verify your location correctly.

    Solution:
    Click on the Start menu, and type the following command:
    SLUI 4
    In the wizard- choose your country and click Next. Now complete the Phone Activation procedure as instructed.

    Sep 14, 2010

    FIX: WinXP Setup Error "Setup cannot copy the file cmnicfg.xml"

    The Problem:
    During the first text-phase of setup, during the installation files copy, you recieve an error saying:
    "Setup cannot copy the file cmnicfg.xml"
    This error is related to wrong permissions set on the System32 folder.
    What most likely happened:
    - You had Vista/7 installed & you decided to re-install XP over it
    - During setup you chose not to format the partition
    Windows tried to delete the old Windows folder but left many files it couldn't delete due to changes in
    NTFS permissions left by the former OS....

    The solution:
    You can choose one of the following options:
    1. Format the partition.
    2. On the destination partition, rename the Windows folder
    3. During install, set the folder name for the installation to be different than the existing.

    Aug 29, 2010

    FIX: Outlook Error When Clicking on Hyperlinks

    The problems affects Outlook 2003-2010
    The error comes in the following ways:

    This operation has been canceled due to restrictions in effect on this computer. Please contact your system administrator.
    or in Hebrew:

    פעולה זו בוטלה עקב מגבלות החלות על מחשב זה. נא פנה למנהל המערכת

    The Problem:
    the problem is related to corrupt registry settings for HTML links.
    According to Microsoft you need to use this article to fix the issue:
    http://support.microsoft.com/kb/310049

    The Solution:

    I've found it much easier to follow these steps:

    1. Download and run this registry fix for HTML links:
        http://www.dougknox.com/xp/fileassoc/html_association_fix.zip
        Note that you need to extract the Reg file from the zip, double-click on it and approve the request
        to update the Registry.
     *   This method works fine on Windows XP/Vista/7

    Oct 8, 2009

    Fix: Office 2007 Setup Error 1406 on Vista

    Symptoms:

    While installing Office 2007 you get error 1406 saying:
    "setup cannot write the value to the registry key"
    if you click on Ignore it can popup up tp six times during the installation.

    The error message that you receive lists the registry subkey that is causing the error to occur.When attempting to install Microsoft Office, it will often reference one or more of the following keys:

    HKEY_LOCAL_MACHINE > Software > Classes > HWXInk.E-Ink

    HKEY_LOCAL_MACHINE > Software > Classes > HWXInk.E-Ink.1
    HKEY_LOCAL_MACHINE > Software > Classes > SketchObj.SketchInk
    HKEY_LOCAL_MACHINE > Software > Classes > SketchObj.SketchInk.1

    In order to resolve this, we need to give the installer permission to write to these keys.

    Solution:

    Launch the registry editor by choosing Start > Run (or Windows Key+R) and typing REGEDIT.

    Locate the first of the above-listed registry keys. Right-click on the key and click Permissions. In the list of groups or user names, see if “Everyone” is listed. If the group exists, skip to step 5. If the group does not exist, begin with step 1:

    1. Click the Add button below the “Group or user names” box.
    2. Click Advanced at the bottom of the next window.
    3. Click “Find Now” on the right side of the next window.
    4. In the list of results, choose the “Everyone” entry, click OK, and then OK again.
    5. In the “Group or user names” box, be sure Everyone is highlighted, and check the box to allow Full Control.
    6. Repeat for the next registry key in the list.

    Once permissions have been adjusted for all four of the listed keys, reboot the computer and attempt to install Office.

    Reference: http://support.microsoft.com/kb/838687

    Sep 10, 2009

    How to Fix Outlook Error: Cannot start Microsoft Office Outlook. Cannot Open the Outlook Window

    I recently came across this error message on a machine running Office 2007 and Windows 7:

    Symptoms:
    "Cannot start Microsoft Office Outlook. Cannot Open the Outlook Window"
    or
    "Cannot start Microsoft Office Outlook. Outlook cannot open the Outlook window.  Invalid XML, the view cannot loaded"
    or
    "אין אפשרות להפעיל את microsoft office outlook, אין אפשרות לפתוח את OUTLOOK.XML לא חוקי, אין אפשרות לפתוח את חלון התצוגה"
    or
    "אין אפשרות להפעיל את Microsoft Office Outlook. אין אפשרות לפתוח את חלון Outlook."


    Solution:
    Run this command from Start > Run:

    OUTLOOK.EXE /resetnavpane


    From What I understand, the problem can happen in Outlook 2003/2007 and Windows XP/Vista/7.

    Aug 5, 2009

    How To Debug BSOD Blue Screen Errors using BlueScreenView Utility

    A new tool from the home of Nirsoft has come to the rescue.
    Using BlueScreenView, a small portable debugging tool, you can easily find information regarding your previous Stop errors (also known as Blue Screen of Death).
    The tool uses the saved memory dump files that Windows saves in the folder C:\Windows\MiniDump\

    After running the tool you'll see a table listing each memory dump info including: date & time of crash, the Error Code and parameters and most important- the suspected driver/cause of the crash.

    One small extra is the ability to change the detail view into a Blue-Screen simulation screen that shows you how the error message approximately looked like:




















    Why using this tool instead of the Windows Debugging Tools Pack from Microsoft?
    1. it doesn't need another installation of external software.
    2. it does a batch debug of all mini-dump files altogether instead of one-by-one using WinDbg.
    3. it runs directly from your USB :)

    Have fun!

    YaronM

    Jun 12, 2009

    Fix: InstallShield Engine "Setup Is Unable To Find or Update IsScript.msi"


    ERRORS
    During installation, you may get an error message regarding the IsScript engine. The following are some of the common error messages encountered with the IsScript engine:
    • "Setup Is Unable To Find or Update ISScript.msi"
    • Cannot find IsScript.msi
    • The version of IsScript.msi is old
    • The feature you are trying to use is on a network resource that is unavailable. Click OK to try again, or enter an alternate path to a folder containing the installation package 'IsScript.Msi' in the box below.

    FIX
    To fix this issue, you need to determine the version number of the IsScript engine you need, download it, and install it.
    1. Right-click on the installation file that you are trying to install and select Properties
      • The typical names for installation files are setup.exe, update.exe, installer.exe, etc.
      • Your installation file can be found on the CD where you are running the setup from.
    2. In the Properties dialog, click on the Version tab.
    3. Look at the File Version field to determine the version number of the IsScript engine you need:
      • If the file version number is 2.0x or less, download the IKernel engine and install it on your computer.
        • Delete the folder C:\Program Files\Common Files\InstallShield\engine from the machine.
        • Once downloaded, double-click it. This installs the IKernel engine, which should fix the issue.
      • If the file version number starts with 7, download the following ISScript.msi file and install it on your computer.
        • Delete the folder C:\Program Files\Common Files\InstallShield\Driver\7 from the machine.
        • Unzip the above file using the WinZip utility.
        • Double-click the IsScript.msi file. This installs the IsScript engine, which should fix the issue.
      • If the file version number starts with 8, download the following IsScript8.msi file and install it on your computer.
        • Delete the folder C:\Program Files\Common Files\InstallShield\Driver\8 from the machine.
        • Unzip the above file using the WinZip utility.
        • Double-click the IsScript8.msi file. This installs the IsScript engine, which should fix the issue.
      • If the file version number starts with 9, download the following IsScript9.msi file and install it on your computer.
        • Delete the folder C:\Program Files\Common Files\InstallShield\Driver\9 from the machine.
        • Unzip the above file using the WinZip utility.
        • Double-click the IsScript9.msi file. This installs the IsScript engine, which should fix the issue.
      • If the file version number starts with 9.5 , download the following IsScript10.msi file and install it on your computer.
        • Delete the folder C:\Program Files\Common Files\InstallShield\Driver\10 from the machine.
        • Unzip the above file using the WinZip utility.
        • Double-click the IsScript9.msi file. This installs the IsScript engine, which should fix the issue.
      • If the file version number starts with 10 , download the following IsScript10.msi file and install it on your computer.
        • Delete the folder C:\Program Files\Common Files\InstallShield\Driver\10 from the machine.
        • Unzip the above file using the WinZip utility.
        • Double-click the IsScript9.msi file. This installs the IsScript engine, which should fix the issue.
      • If the file version number starts with 10.5 , download the following IsScript1050.msi file and install it on your computer.
        • Delete the folder C:\Program Files\Common Files\InstallShield\Driver\1050 from the machine.
        • Unzip the above file using the WinZip utility.
        • Double-click the IsScript9.msi file. This installs the IsScript engine, which should fix the issue.
      • If the file version number starts with 11 , download the following IsScript11.msi file and install it on your computer.
        • Delete the folder C:\Program Files\Common Files\InstallShield\Driver\11 from the machine.
        • Unzip the above file using the WinZip utility.
        • Double-click the IsScript9.msi file. This installs the IsScript engine, which should fix the issue.


    More Information

    May 5, 2009

    Fix: Error "Buffer Overrun Detected" on WINWORD.EXE in Office 2003

    This error is specific to the Hebrew version of Office 2003 SP3 and also affect an Office 2003 SP3 with Hebrew Language-Pack installed. The error says:

    Microsoft Visual C ++ Runtime library 
    buffer overrun detected! Program: C:\Program Files\Microsoft Office\Office11\Winword.exe 
    A buffer overrun has been detected which has corrupted the program's internal state. 
    the program cannot safely continue execution and must now be terminated.

    The error occurs just after you open a document or start typing a message in Outlook. the cause of the problem is a known-bug in the spell-checking mechanism. to solve it you need to install a Hotfix and also delete the custom-dictionary file that was created by Word.
    Download the Hotfix from Microsoft or from Here.
    In my link I also added to the zip a batch file that helps deleting the custom-dictionary file.

    There are 3 files to use:
    1. MSSP3HE.msp (For Hebrew Localized Office): run it until the setup finishes successfully.
    2. HBRMUI.msp (For Hebrew LangPack): run it- you'll probably get a message saying you don't need it.
    3. Fix-Buffer-Overrun.bat = run it to delete the custom.dic file. alternativley, delete the file manually from this location: %userprofile%\application data\microsoft\proof\custom.dic

    To test the hotfix you can just start Word and type gibberish until you get the red-line beneath the letters.

    Apr 1, 2009

    Outlook Error when opening TIF Attachment files

    You may receive the following error message when opening attachments in Outlook (such as PDF faxes): "Can't create file: FAX.TIF. Right-Click the folder you want to create the file in, and then click Properties on the shortcut menu to check your permissions on the folder."

    Microsoft Outlook uses a temporary folder to save and open the attachments. By default that folder is:
    "C:\Documents and Settings\%USER_NAME%\Local Settings\Temporary Internet Files\OLK#\" (where # is a random number) Some of the latest security updates for Windows 2000 and XP are preventing folders to be created in that folder. The solution is to use the regular TEMP folder.

    NOTE for Vista Users: the folders path is changed in Vista to: 
    "C:\Users\%username%\AppData\Local\Microsoft\Windows\Temporary Internet Files"


    1. Use REGEDIT.EXE to locate the following key:
    HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security

    (Note: Depending on your version you may have to modify that path after the "Office" key. You may have folders 8.0, 9.0, 10.0, 11.0, go the highest number. This is probably the version that you use.)

    2. Modify the Key "OutlookSecureTempFolder", by replacing "Temporary Internet Files" with "Temp". For example:
    OLD VALUE: "C:\Documents and Settings\username\Local Settings\Temporary Internet Files\OLK177\"

    (Note: There may be a different number than 177)

    NEW VALUE: "C:\Documents and Settings\username\Local Settings\Temp\OLK177\"


    3. Restart Microsoft Outlook.







    Credit goes to JacksonTechnical