SSIS Package fails in the middle of the execution with some error

Hi ALL,
I have an SSIS Package which basically loops across various files and various sheets and loads that data into a SQL table.Lets say i have 50 files it loads randomly somewhere around 30 and suddenly fails in the middle with the following error
[Excel Source [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. 
The AcquireConnection method call to the connection manager "Excel" failed with error code 0xC0202009. 
 I have no idea what this mean, i googled around and saw that i need to change the debugging properties from TRUE to FALSE, i did that but no use.
Can someone please explain me what could be the reason for this one to be happening and how can i get around this one?
Thanks.

Hi Patrick,
The link you gave above helped me to achieve what i exactly want. I am using multiple processes to load the files now.
It really sucks that there is no solution for this one.But glad i am able to work it in different way.
Thanks a lot for your reply.
Not sure if its related
I've had similar error recently while working with ACE provider and these steps helped me to fix it
http://visakhm.blogspot.in/2013/12/how-to-solve-microsoftaceoledb120-error.html
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Similar Messages

  • SQL Server Agent running SSIS package fails Unable to determine if the owner of job has server access

    I have a web application developed through VS 2012 which has a button on a form that when operated starts a SQL Server agent job on the server that runs an SSIS package.  The website and the instance of SQL Server with the agent and SSIS package are
    on the same windows 2008 r2 server.  When the button is operated no exceptions are raised but the SSIS package did not execute.
    When I look in the logfileviewer at the job history of the sql server agent job I see that the job failed with message...
    The job failed.  Unable to determine if the owner (DOMAINNAME\userid) of job runWebDevSmall has server access (reason: Could not obtain information about Windows NT group/user 'DOMAINNAME\userid'<c/> error code 0x6e. [SQLSTATE 42000] (Error 15404)).,00:00:00,0,0,,,,0
    ...even though DOMAINNAME\userid is in the logins for the sql server and has admin authorities.
    Could someone show me what I need to do to get this to run?  Thanks tonnes in advance for any help, Roscoe

    This can happen when the network is too slow to allow a timely completion of the verification. Or the account running has no such right.
    I suggest you try using the SA account for the job as it does not require to poll the AD.
    Arthur My Blog

  • In the middle of the installation processing, this has appeared: "There is a problem with the windows installer package. A program is required for this install to complete could not be run." my question is, what is that specific program?

    in the middle of the installation processing, this has appeared: "There is a problem with the windows installer package. A program is required for this install to complete could not be run." my question is, what is that specific program?

    Let's try the following user tip with that one:
    "There is a problem with this Windows Installer package ..." error messages when installing iTunes for Windows

  • When i was partitioning my hard drive i ran out of power (so it closed in the middle of the process). now when i try to partition it says Couldn't modify partition map because file system verification failed.

    When i was partitioning my hard drive i ran out of power (so it closed in the middle of the process). now when i try to partition it says Couldn’t modify partition map because file system verification failed.

    You'll have to select the entire external hard drive by the hardware name itself and then apply a new partition table to it under the Partition tab of Disk Utility. Erase and format the drive.
    GUID for OS X.

  • SSIS Package Fails when Scheduled as a SQL Server Agent Job

    I have an SSIS package that runs without any problems when executed through BIDS.
    However, when I schedule the SSIS as an Agent job, it fails completely or part way through. When it partially runs, the part that it is failing on is a Script Task that moves the source data file to an archive folder (on the same server).
    I have tried using my domain account as the owner of the job, then the job fails straight off and I get an error:
    Unable to determine if the owner (Domain\MyID) of job JobName has server access (reason: Could not obtain information about Windows NT group/user 'Domain\MyID'
    If I change the owner to the 'sa' account , then the job partially runs, but then fails because 'sa' is a SQL account and does not have access to the filesystem.
    I have managed to get it to work by using the SQL2008_Local account and granting modify permissions to the affected folders.
    My question is - what is the advised way of doing this?
    Thanks
    Gary

    Hi Garyv.King,
    When you see a SSIS package fails running in a SQL Agent job, you need to first consider the following conditions:
    1. The user account that is used to run the package under SQL Server Agent differs from the original package author.
    2. The user account does not have the required permissions to make connections or to access resources outside the SSIS package.
    For more detailed information about the issue, please following this KB article:
    An SSIS package does not run when you call the SSIS package from a SQL Server Agent job step
    http://support.microsoft.com/kb/918760 
    You can check SQL Server Agent’s activity logs, Windows Event logs and SSIS logs to get more clues. Also the tool Process Monitor is helpful to track the cause of registry or file access related issues.
    The following 4 issues are common encountered in the SSIS forum.
    1. The package's Protection Level is set to EncryptSensitiveWithUserKey but your SQL Server Agent service account is different from the SSIS package creator.
    2. Data source connection issue.
    3. File or registry access permission issue.
    4. No 64-bit driver issue.
    For more information about it, please see:
    How do I troubleshoot SSIS packages failed execution in a SQL Agent job:
    http://social.technet.microsoft.com/Forums/en-US/sqlintegrationservices/thread/e13c137c-1535-4475-8c2f-c7e6e7d125fc 
    Thanks,
    Eileen

  • DTEXEC does not fail when SSIS package fails

    I need to run my SSIS 2012 packages through the catalog with DTEXEC. This works very well, except that if my SSIS package fails, DTEXEC does not fail. I need DTEXEC to fail, so my scheduler knows that there is an error.
    I use the following command:
    dtexec /ISServer "\SSISDB\MyFolder\MyProject\MyPackage.dtsx" /Ser MyServer /Par $Package::Partition;201412 /Env 5
    When I check the status of the run in the Catalog, it is failed.
    When I used SSIS 2008, I had no problem getting DTEXEC to fail when the packages failed.

    I've had the same problem, and come up with the following prototype for a SQL Script which I run in our JAMS Enterprise Scheduler. It uses SSISDB stored procedures to start the SSIS package and polls every 5 seconds to report any messages, and final
    status code of the package. JAMS parameters are delimited by << >> symbols, and will need to be changed for your scheduler/batch process. I guess the script could be converted to a stored procedure. I'm also hoping it will work with SQL High
    Availability groups to ensure the SSIS package runs on the server that's hosting the active database.
    DECLARE @execution_id BIGINT
    DECLARE @status INT= 1
    DECLARE @Event_Message_id BIGINT= 0
    DECLARE @Last_Event_Message_id BIGINT= 0
    DECLARE @message_time DATETIME2(7)
    DECLARE @message NVARCHAR(MAX)
    --Create a SSIS execution for the required SSIS package and return the execution_id
    EXEC [SSISDB].[catalog].[create_execution] @package_name = N'<<pPackageName>>.dtsx',
        @execution_id = @execution_id OUTPUT, @folder_name = N'<<pSSISFolderName>>',
        @project_name = N'<<pSSISProjectName>>', @use32bitruntime = <<p32Bit>>, @reference_id = NULL
    RAISERROR('Starting SSIS package <<pPackageName>> with execution_id %I64d on server %s',0,0,@execution_id,@@SERVERNAME) WITH NOWAIT
    --Set the logging level 0-none, 1-basic (recommended), 2-performance, 3-verbose
    EXEC [SSISDB].[catalog].[set_execution_parameter_value] @execution_id,
        @object_type = 50, @parameter_name = N'LOGGING_LEVEL',
        @parameter_value = <<pLogging_Level>>
    --Start the package executing
    EXEC [SSISDB].[catalog].[start_execution] @execution_id
    WHILE @status IN ( 1, 2, 5, 8 ) --created (1), running (2), canceled (3), failed (4), pending (5), ended unexpectedly (6), succeeded (7), stopping (8), and completed (9).
        BEGIN
            WAITFOR DELAY '00:00:05'
        --Get the status to see later if we've finished
            SELECT  @status = status
            FROM    SSISDB.catalog.executions
            WHERE   execution_id = @execution_id 
        --Are there any event messages since we last reported any?
            DECLARE curEventMessages CURSOR FAST_FORWARD
            FOR
                SELECT  event_message_id ,
                        message_time ,
                        message
                FROM    SSISDB.catalog.event_messages
                WHERE   operation_id = @execution_id
                        AND event_message_id > @Last_Event_Message_id;
            OPEN curEventMessages
            FETCH NEXT FROM curEventMessages INTO @Event_Message_id, @message_time,
                @message
            WHILE @@FETCH_STATUS = 0
                BEGIN
            --We've found a message, so display it - watch out for % signs in the message, they'll cause an error if we don't replace them
                    SET @message = CONVERT(NVARCHAR(MAX), @message_time, 113)
                        + ' ' + replace(@message,'%',' percent')
                    RAISERROR(@message,0,0) WITH NOWAIT
                    SET @Last_Event_Message_id = @Event_Message_id --Make a note that we've reported this message
                    FETCH NEXT FROM curEventMessages INTO @Event_Message_id,
                        @message_time, @message
                END
            CLOSE curEventMessages
            DEALLOCATE curEventMessages
        END
    --@Status indicates that package execution has finished, so let's look at the outcome, and error if there's a problem
    IF @status = 7
        RAISERROR('Package Succeeded',0,0)
    ELSE
        IF @status = 9
            RAISERROR('Package completed',0,0)
        ELSE
            IF @status = 3
                RAISERROR('Package Cancelled',16,1)
            ELSE
                IF @status = 4
                    RAISERROR('Package failed (see error message above)',16,1)
                ELSE
                    IF @status = 6
                        RAISERROR('Package ended unexpectedly',16,1)
                    ELSE
                        RAISERROR('Package ended with unknown status %i',16,1,@status)

  • SSIS 2012 Scheduled SSIS package fail to start – Execution timed out

    Hi
    I am currently running into an issue that seem to have a live Connect issue raised for it. The following is the link to the connect issue https://connect.microsoft.com/SQLServer/feedback/details/783291/ssis-package-fails-to-start-application-lock-timeout-in-ssisdb-catalog-create-execution
    There is also a blog post that explains this issue in more detail, however the solution
    it provides does not work all the time and I am very reluctant to create custom stored procedures in the SSISDB. http://speaksql.wordpress.com/2013/06/27/ssis-2012-fail-to-start-execution-timed-out/
    Just to give some more background. When scheduling 10 or more, in my case I scheduled 14, SQL Server Agent Jobs all executing a package in the SSIS Catalog and all kicking off on exactly the same time about 10% to 20% of these jobs fail stating one of the
    following error messages:
    The operation failed because the execution timed out.  Source: .Net SqlClient Data Provider  Started:  12:20:01  Finished: 12:20:07  Elapsed:  5.797 seconds.  The package execution failed.  The step failed.
    Description: Transaction (Process ID 66) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.  Source: .Net SqlClient Data Provider  Started:  14:06:48  Finished: 14:06:53
     Elapsed:  4.719 seconds.  The package execution failed.  The step failed.
    This timeout takes place both when using TSQL to start the package in the Job or when the step in the Job is set to start the package as an Integration Services Package.
    Steps to recreate this:
    1. Create one SSIS package that simply executes for around a minute. For example you can use an Execute SQL Task and simply execute the following TSQL "WAITFOR DELAY '00:01:00'"
    2. Create 14 SQL Server Agent Jobs each executing the same package and schedule all of them to run at the same time.
    3. Watch the execution of the jobs take place and note the failures. (This does not always happen and you might get one run in which everything executes without a problem. The next run might have 6 or 7 of the jobs fail.)
    You can also create 14 different SSIS packages, one for each job, and the result is the same.
    I am running on SQL 2012 SP1 CU4. Windows Server 2012 R2 patched to the lastest patch level.
    This issue does not happen when the packages are deployed to the SSIS Package Store the way that it was done in SQL2008 and before. It only occurs when the SSIS packages are deployed to the SSIS Catalog.
    Any help or feedback on this would be greatly appreciated.
    Kind Regards,
    Christo Olivier

    Hi Tom
    Thank you for the fast response. I went and increased the value by 1024KB instead of the initial
    512KB. Unfortunately this seems to only alleviate the issue but does not stop it from occurring. It
    is happening much less often now but still occurring intermittently.
    Regards,
    Christo

  • Why does iphoto screen go grey and a spinning wheel in the middle of the page and nothing else

    can someone tell me why i always get a spinning wheel in the middle of the page and nothing else when trying to open iphoto

    Either the program, the iPhoto Library or the iPhoto preference file is hosed.
    First thing is first, backup your user file folders to a external hard drive and disconnect.
    The easiest (and most likey the cause of your issue) to fix would be the iPhoto preference file
    iPhoto preference file fix
    Look in your /Users/Library/Preference for a file like
    com.apple.iphotopreferences.plist
    or
    com.apple.iphoto.plist
    and delete it and reboot, restart iPhoto and re-enter your preferences.
    If your on OS X Lion, your going to have to use the Finder's "Go To" to get to the Library as it's hidden as in Snow Leopard it's not.
    Reinstall iPhoto
    If that doesn't resolve your issue and your on Lion, you can redownload the iLife software from the MacAppStore and simply reinstall it, which will overwrite iPhoto and fix it.
    If your on Snow Leopard you reboot holding c from the 10.6 grey installer disks (only) that came with your comptuer and simply reinstall OS X 10.6 which will reinstall iPhoto (the 10.6.3 Snow Leopard retail disk doesn't have iLife)
    If you purchased iLife from the boxed set, then reinstall it.
    If you had iLife from 10.5 and your on 10.6 or 10.7, or got it free with 10.6 and now on 10.7, then your going to have to wait until you try the next step (then extract iPhoto from the installer disk using Pacifist or purchase iLife)
    Rebuild iPhoto Library
    If that doesn't resovle your issue you can right click (or control click) on the iPhoto Library and "Show Package Contents" inside will be a folder with all your original photo's. Copy these out and move the iPhoto Library out of the Pictures folder and rename it (if you can) so iPhoto can't find it.
    Then restart iPhoto and see if it creates a new iPhoto Library, then simply import the pictures from the copy you made.
    If it fails to work after this, there is a corrupted picture in your iPhoto, you'll have to repeat the same process with importing a few pictures at a time until you can locate the corrupted ones.

  • My iPhone 5 won't use 3G when 4G isn't available. I live in the middle of nowhere, but with my iPhone 4 I could use the Internet on 3G just fine. Now I don't get anything unless I'm on wifi. I have AT

    My iPhone 5 won't use 3G when 4G isn't available. I live in the middle of nowhere, but with my iPhone 4 I could use the Internet on 3G just fine without needing wifi. Now I don't get anything unless I'm on wifi. My phone says '4G' but then says 'could not activate cellular data' or gives me the gray google failed because you dont have internet page. I have AT&amp;T if that matters. I just want to get Internet and my email like I used to be able to. Slow 3G is fine with me, but I need it to work on my iPhone 5. Can anyone help me?

    Oh ok, thank you! So I just got a bum SIM card when I bought this phone or something?

  • Anyone help mac book screen White with a question Mark in the middle of the screen .matthew

    Can anyone help my mac book screen has gone White with a question Mark in the middle of the screen .Matthew

    Reinstall OS X without erasing the drive
    Do the following:
    1. Repair the Hard Drive and Permissions
    Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    2. Reinstall Snow Leopard
    If the drive is OK then quit DU and return to the installer.  Proceed with reinstalling OS X.  Note that the Snow Leopard installer will not erase your drive or disturb your files.  After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
    Download and install the Combo Updater for the version you prefer from support.apple.com/downloads/.

  • What to do when my Macbook air won't load from startup. It hangs in the middle during the black apple screen at the beginning

    my Mac book air will not start up it hangs in the middle of the status bar when I turn it on and will not move.

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
    Step 1
    The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
    There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
    a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
    b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
    c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
    Step 3
    Sometimes a startup failure can be resolved by resetting the NVRAM.
    Step 4
    If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
    Step 5
    If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
    Step 6
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    Step 7
    If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
    Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
    Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
    If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
    If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 8
    Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
    Step 9
    If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.  
    Step 10
    Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Step 11
    Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
    Step 12
    This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
    Step 13
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

  • I have an error message "page_bottom_overlay-2.png" which comes up when I try to publish.  There is a large X with a Question mark in the middle over the entire background of the page.  The error message says the file is missing.  I did not delete files.

    I have an error message "page_bottom_overlay-2.png" which comes up when I try to publish.  There is a large X with a Question mark in the middle over the entire background of the page.  The error message says the file is missing.  I did not delete files.  How can I find files that seem to be missing?

    This is probably one of the files that is required by the template you are using.
    These files are inside the iWeb app. Control click the iWeb app icon and select "Show package contents".
    You need to dig down through the folders and files to find what you want...
    Contents/Resources/da.lproj/Templates/
    If the file is missing you would need to re install the iWeb app...
    http://www.iwebformusicians.com/iWeb/iWeb-Tips.html

  • Grey line in the middle on the screen

    help a grey line in the middle of the screen

    Probably a hardware issue, it could be a failing display or graphics card. I'd recommend running Apple Hardware Test in Extended Mode 2-3x to see if it finds any errors. At some point you will need to make an appointment at  our local Apple Store or AASP for professional assesment.
    BTW please complete your profile, you can find the link under Your Stuff in the upper right of this screen. At the very least let us know the version of OS X on your computer and what computer you own.

  • Strange small glyph in the middle of the screen when using LabVIEW 8.2.1

    I've started noticing a strange small glyph in the middle of the screen when I am using LabVIEW 8.2.1.
    Sometimes it is there, sometimes it isn't. Has anyone else seen this? Why is it there? Can I get rid of it?
    (Just in case you think I am going crazy from too much LabVIEW I'll include a screen capture of it...)
    Well that's it. I barely noticed it on my blue/ background picture. It seems to be there on my XP machine but not my Win2K machine.
    Message Edited by Troy K on 10-11-2007 10:49 AM
    Troy
    CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
    I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
    Beware of the man who won't be bothered with details. - William Feather
    The greatest of faults is to be conscious of none. - Thomas Carlyle
    Attachments:
    strange glyph.PNG ‏1 KB

    It's something from your video driver (If I recall correctly an NVIDIA).
    LabVIEW creates somewhere off-screen a window with  a size of 0,0. The driver detects this and as som sort of anti-spam moves it on-screen.
    Ton
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

  • Tty1-6 freeze in the middle of the boot process, tty7 and X works fine

    I'm running Arch+KDE (and some alternative like xmonad as wm). I have the following strange problem:
    Booting works fine, KDM starts, I can login, everythings works. However, although I can change to tty1-6 via ctrl+alt+f1...6 they are frozen in the middle of the boot process, here's exactly what I see after switching to another tty:
    [ 2.733866] ata2.00: 78165360 sectors, multi 16: LBA48
    [ 2.747003] ata2.00: configured for UDMA/100
    [ 2.747223] scsi 1:0:0:0: Direct-Access ATA ST340014A 3.06 PQ: 0 ANSI: 5
    [ 2.760075] usb 1-1: new high speed USB device number 2 using ehci_hcd
    [ 2.771843] sd 1:0:0:0: [sda] 78165360 512-byte logical blocks: (40.0 GB/37.2 GiB)
    [ 2.772018] sd 1:0:0:0: [sda] Write Protect is off
    [ 2.772098] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
    [ 2.772128] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 2.777708] sr0: scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray
    [ 2.777797] cdrom: Uniform CD-ROM driver Revision: 3.20
    [ 2.778630] sr 0:0:0:0: Attached scsi CD-ROM sr0
    [ 2.785447] sda: sda1 sda2 sda3 sda4
    [ 2.786061] sd 1:0:0:0: [sda] Attached SCSI disk
    [ 2.885089] hub 1-1:1.0: USB hub found
    [ 2.885518] hub 1-1:1.0: 4 ports detected
    [ 2.993360] usb 1-2: new high speed USB device number 3 using ehci_hcd
    [ 3.236962] usb 1-1.1: new full speed USB device number 5 using ehci_hcd
    [ 3.384005] input: Logitech Logitech USB Headset as /devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1.1/1-1.1:1.3/input/input1
    [ 3.384294] generic-usb 0003:046D:0A02.0001: input,hidraw0: USB HID v1.00 Device [Logitech Logitech USB Headset] on usb-0000:00:1d.7-1.1/input3
    The next lines which are not shown are (via dmesg)
    [ 3.384294] generic-usb 0003:046D:0A02.0001: input,hidraw0: USB HID v1.00 Device [Logitech Logitech USB Headset] on usb-0000:00:1d.7-1.1/input3
    [ 3.390423] usbcore: registered new interface driver usbhid
    [ 3.390511] usbhid: USB HID core driver
    [ 3.393690] usb 1-1.3: new high speed USB device number 6 using ehci_hcd
    [ 3.424849] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
    [ 3.840034] usb 3-1: new low speed USB device number 2 using uhci_hcd
    [ 4.025136] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input2
    [ 4.025381] generic-usb 0003:046D:C050.0002: input,hidraw1: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.1-1/input0
    [ 5.739092] udevd[227]: starting version 171
    [ 6.392169] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3
    [ 6.392182] ACPI: Sleep Button [SLPB]
    [ 6.392256] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
    [ 6.392262] ACPI: Power Button [PWRF]
    [ 6.484257] input: PC Speaker as /devices/platform/pcspkr/input/input5
    [ 6.486020] ACPI: acpi_idle registered with cpuidle
    [ 6.567251] Linux agpgart interface v0.103
    [ 6.589560] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    [ 6.695744] i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    [ 6.711992] iTCO_vendor_support: vendor-support=0
    [ 6.719428] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06
    [ 6.720445] iTCO_wdt: Found a ICH5 or ICH5R TCO device (Version=1, TCOBASE=0x0460)
    [ 6.721211] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    [ 6.722801] parport_pc 00:07: reported by Plug and Play ACPI
    [ 6.722852] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
    [ 6.743621] agpgart-intel 0000:00:00.0: Intel 865 Chipset
    [ 6.743658] agpgart-intel 0000:00:00.0: detected gtt size: 131072K total, 131072K mappable
    [ 6.743755] agpgart-intel 0000:00:00.0: detected 1024K stolen memory
    [ 6.744774] agpgart-intel 0000:00:00.0: AGP aperture is 128M @ 0xa0000000
    [ 6.847264] ppdev: user-space parallel port driver
    [ 6.852667] Intel 82802 RNG detected
    [ 6.878022] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    [ 6.923869] [drm] Initialized drm 1.1.0 20060810
    [ 7.050148] i915 0000:00:02.0: enabling device (0000 -> 0003)
    [ 7.050160] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    [ 7.050168] i915 0000:00:02.0: setting latency timer to 64
    [ 7.072268] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
    [ 7.072273] e100: Copyright(c) 1999-2006 Intel Corporation
    [ 7.072344] e100 0000:01:08.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
    [ 7.110870] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
    [ 7.110875] [drm] Driver supports precise vblank timestamp query.
    [ 7.113855] i915 0000:00:02.0: BAR 6: can't assign [??? 0x00000000 flags 0x0] (bogus alignment)
    [ 7.113859] [drm] failed to find VBIOS tables
    [ 7.133720] e100 0000:01:08.0: PME# disabled
    [ 7.140882] [drm] initialized overlay support
    [ 7.141854] e100 0000:01:08.0: eth0: addr 0xfe9df000, irq 20, MAC addr 00:07:e9:4b:a9:8c
    [ 7.178193] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
    [ 7.181514] render error detected, EIR: 0x00000010
    [ 7.181514] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
    [ 7.181514] render error detected, EIR: 0x00000010
    [ 7.219489] No connectors reported connected with modes
    [ 7.219497] [drm] Cannot find any crtc or sizes - going 1024x768
    [ 7.237564] sr 0:0:0:0: Attached scsi generic sg0 type 5
    [ 7.238588] sd 1:0:0:0: Attached scsi generic sg1 type 0
    [ 7.299180] Console: switching to colour frame buffer device 128x48
    [ 7.347619] fb0: inteldrmfb frame buffer device
    [ 7.347623] drm: registered panic notifier
    [ 7.347832] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
    [ 7.557756] Intel ICH 0000:00:1f.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    [ 7.557804] Intel ICH 0000:00:1f.5: setting latency timer to 64
    [ 7.681210] nvidia: module license 'NVIDIA' taints kernel.
    [ 7.681217] Disabling lock debugging due to kernel taint
    [ 7.710730] Linux media interface: v0.10
    [ 7.800616] usbcore: registered new interface driver uas
    [ 7.877282] Linux video capture interface: v2.00
    [ 7.930178] uvcvideo: Found UVC 1.00 device <unnamed> (046d:0802)
    [ 7.972100] input: UVC Camera (046d:0802) as /devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1.3/1-1.3:1.0/input/input6
    [ 7.972388] usbcore: registered new interface driver uvcvideo
    [ 7.972392] USB Video Class driver (v1.0.0)
    [ 7.990026] intel8x0_measure_ac97_clock: measured 50989 usecs (2457 samples)
    [ 7.990031] intel8x0: clocking to 48000
    [ 8.093410] Initializing USB Mass Storage driver...
    [ 8.100022] scsi4 : usb-storage 1-2:1.0
    [ 8.103449] usbcore: registered new interface driver usb-storage
    [ 8.103453] USB Mass Storage support registered.
    [ 8.401795] usbcore: registered new interface driver snd-usb-audio
    [ 8.568477] nvidia 0000:01:01.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
    [ 8.568494] vgaarb: device changed decodes: PCI:0000:01:01.0,olddecodes=io+mem,decodes=none:owns=io+mem
    [ 8.569407] NVRM: loading NVIDIA UNIX x86 Kernel Module 173.14.30 Thu Apr 14 08:47:14 PDT 2011
    [ 9.104388] scsi 4:0:0:0: Direct-Access WD Ext HDD 1021 2002 PQ: 0 ANSI: 4
    [ 9.104713] sd 4:0:0:0: Attached scsi generic sg2 type 0
    [ 9.105502] sd 4:0:0:0: [sdb] 2930272256 512-byte logical blocks: (1.50 TB/1.36 TiB)
    [ 9.106381] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
    [ 9.106386] sd 4:0:0:0: [sdb] Assuming drive cache: write through
    [ 9.108519] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
    [ 9.108524] sd 4:0:0:0: [sdb] Assuming drive cache: write through
    [ 9.129321] sdb: sdb1 sdb2 sdb3 sdb4
    [ 9.131752] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
    [ 9.131758] sd 4:0:0:0: [sdb] Assuming drive cache: write through
    [ 9.131762] sd 4:0:0:0: [sdb] Attached SCSI disk
    [ 10.662601] EXT4-fs (sda3): re-mounted. Opts: (null)
    [ 11.097052] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
    [ 11.412380] Adding 2104508k swap on /dev/sda2. Priority:-1 extents:1 across:2104508k
    [ 14.876829] e100 0000:01:08.0: eth0: NIC Link is Up 100 Mbps Full Duplex
    [ 20.827578] NET: Registered protocol family 10
    [ 31.203380] eth0: no IPv6 routers present
    The curious thing is that everything works perfect in KDE, resp. tty7 ?!?

    what ever upgrade the software downloaded is the problem
    You didn't mention this in your first post. Any idea what it was? Backups?
    Besides that, this may be a fault in the video card, driver, or a screen fault.
    Courtesy of BDAqua (if possible):
    Take a screen shot & view that in Preview, move the Preview window around, if you see double lines it's a Video card/VRAM problem, if the lines do not move moving the pic around then it's the LCD or cable.

Maybe you are looking for