Some jobs fail BackupExec, Ultrium 215 drive, NW6.5 SP6

The OS is Netware 6.5 SP6.
The server is a HP Proliant DL-380 G4.
The drive is a HP StorageWorks Ultrium LTO-1 215 100/200GB drive.
The drive is connected to a HP PCI-X Single Channel U320 SCSI HBA, which I recently installed, in order to solve slow transfer speeds, and to solve CPQRAID errors which stalled the server during bootup (it was complaining to have a non-disk drive on the internal controller).
Backup Exec Administrative Console is version 9.10 revision 1158, I am assuming that this means that BE itself has this version number.
Since our data is now more than the tape capacity I have recently started running two jobs interleaved, to backup (around) half of the data at night. One which runs Monday, Wednesday and Friday and one which runs Tuesday and Thursday.
My problem is that while the Tue/Thu job completes succesfully every time, the Mon/Wed/Thu job fails every time.
The jobs have identical policies (except for the interleaved weekdays), but different file selections.
The job log of the Mon/Wed/Thu job fails with this error:
##ERR##Error on HA:1 ID:4 LUN:0 HP ULTRIUM 1-SCSI.
##ERR##A hardware error has been detected during this operation. This
##ERR##media should not be used for any additional backup operations.
##ERR##Data written to this media prior to the error may still be
##ERR##restored.
##ERR##SCSI bus timeouts can be caused by a media drive that needs
##ERR##cleaning, a SCSI bus that is too long, incorrect SCSI
##ERR##termination, or a faulty device. If the drive has been working
##ERR##properly, clean the drive or replace the media and retry the
##ERR##operation.
##ERR##Vendor: HP
##ERR##Product: ULTRIUM 1-SCSI
##ERR##ID:
##ERR##Firmware: N27D
##ERR##Function: Write(5)
##ERR##Error: A timeout has occurred on drive HA:1 ID:4 LUN:0 HP
##ERR##ULTRIUM 1-SCSI. Please retry the operation.(1)
##ERR##Sense Data:
##ERR##00 00 00 00 - 00 00 00 00 - 00 00 00 00 - 00 00 00 00
##ERR##00 00 00 00 - 00 00 00 00 - 00 00 00 00 - 00 00 00 00
##NML##
##NML##
##NML##
##NML## Total directories: 2864
##NML## Total files: 23275
##NML## Total bytes: 3,330,035,351 (3175.7 Megabytes)
##NML## Total time: 00:06:51
##NML## Throughput: 8,102,275 bytes/second (463.6 Megabytes/minute)
I am suspecting the new controller, or perhaps a broken drive?
I have run multiple cleaning jobs on the drive with new cleaning tapes. The cabling is secured in place.
I have looked for firmware updates, but even though theres a mentioning of a new firmware on hp's site (see http://h20000.www2.hp.com/bizsupport...odTypeId=12169), I can't find the firmware for netware HP LTT (the drive diagnosis / update tool).
I'm hoping someone can provide me some useful info towards solving this problem.
Regards,
Tor

My suggestion to you is to probably just give up on fixing this. I
have the same DL380, but a slightly newer drive(Ultrium 448). After
working with HP, Adaptec, & Symantec for over a year I gave up. I've
tried different cards (HP-LSI, Adaptec) , cables, and even swapped the
drive twice with HP but was never able to get it to work.
In the end I purchased a new server, moved the card and tape drive,
and cables all over to the new server and the hardware has been
working fine in the new box for the last year or so. Until I loaded l
SP8 the other day.
My guess is that the PCI-X slot used for these cards isn't happy with
the server hardware.
On Tue, 27 Jan 2009 11:16:02 GMT, torcfh
<[email protected]> wrote:
>
>The OS is Netware 6.5 SP6.
>
>The server is a HP Proliant DL-380 G4.
>
>The drive is a HP StorageWorks Ultrium LTO-1 215 100/200GB drive.
>
>The drive is connected to a HP PCI-X Single Channel U320 SCSI HBA,
>which I recently installed, in order to solve slow transfer speeds, and
>to solve CPQRAID errors which stalled the server during bootup (it was
>complaining to have a non-disk drive on the internal controller).
>
>Backup Exec Administrative Console is version 9.10 revision 1158, I am
>assuming that this means that BE itself has this version number.
>
>Since our data is now more than the tape capacity I have recently
>started running two jobs interleaved, to backup (around) half of the
>data at night. One which runs Monday, Wednesday and Friday and one which
>runs Tuesday and Thursday.
>
>My problem is that while the Tue/Thu job completes succesfully every
>time, the Mon/Wed/Thu job fails every time.
>
>The jobs have identical policies (except for the interleaved weekdays),
>but different file selections.
>
>The job log of the Mon/Wed/Thu job fails with this error:
>
>##ERR##Error on HA:1 ID:4 LUN:0 HP ULTRIUM 1-SCSI.
>
>##ERR##A hardware error has been detected during this operation. This
>
>##ERR##media should not be used for any additional backup operations.
>
>##ERR##Data written to this media prior to the error may still be
>
>##ERR##restored.
>
>##ERR##SCSI bus timeouts can be caused by a media drive that needs
>
>##ERR##cleaning, a SCSI bus that is too long, incorrect SCSI
>
>##ERR##termination, or a faulty device. If the drive has been working
>
>##ERR##properly, clean the drive or replace the media and retry the
>
>##ERR##operation.
>
>##ERR##Vendor: HP
>
>##ERR##Product: ULTRIUM 1-SCSI
>
>##ERR##ID:
>
>##ERR##Firmware: N27D
>
>##ERR##Function: Write(5)
>
>##ERR##Error: A timeout has occurred on drive HA:1 ID:4 LUN:0 HP
>
>##ERR##ULTRIUM 1-SCSI. Please retry the operation.(1)
>
>##ERR##Sense Data:
>
>##ERR##00 00 00 00 - 00 00 00 00 - 00 00 00 00 - 00 00 00 00
>
>##ERR##00 00 00 00 - 00 00 00 00 - 00 00 00 00 - 00 00 00 00
>
>##NML##
>
>##NML##
>
>##NML##
>
>##NML## Total directories: 2864
>
>##NML## Total files: 23275
>
>##NML## Total bytes: 3,330,035,351 (3175.7 Megabytes)
>
>##NML## Total time: 00:06:51
>
>##NML## Throughput: 8,102,275 bytes/second (463.6
>Megabytes/minute)
>
>I am suspecting the new controller, or perhaps a broken drive?
>
>I have run multiple cleaning jobs on the drive with new cleaning tapes.
>The cabling is secured in place.
>
>I have looked for firmware updates, but even though theres a mentioning
>of a new firmware on hp's site (see http://tinyurl.com/d8tkku), I can't
>find the firmware for netware HP LTT (the drive diagnosis / update
>tool).
>
>I'm hoping someone can provide me some useful info towards solving this
>problem.
>
>Regards,
>Tor

Similar Messages

DPM 2012 R2 Backup job FAILED for some Hyper-v VMs and Some Hyper-v VMs are not appearing in the DPM

DPM 2012 R2 Backup job FAILED for some Hyper-v VMs
DPM encountered a retryable VSS error. (ID 30112 Details: VssError:The writer experienced a transient error. If the backup process is retried,
the error may not reoccur.
(0x800423F3))
All the vss Writers are in stable state
Also Some Hyper-v VMs are not appearing in the DPM 2012 R2 Console When I try to create the Protection Group please note that they are not part of cluster.
Host is 2012 R2 and The VM is also 2012 R2.

Hi,
What update rollup are you running on the DPM 2012 R2 server ? DPM 2012 R2 UR5 introduced a new refresh feature that will re-enumerate data sources on an individual protected server.
Check for VSS errors inside the guests that are having problems being backed up.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Some jobs are failing due to listener.

Hi all,
Only some jobs are failing ,and remaining jobs succeeded.I checked the listener, it was up only.(10.2.0.2 on linux)
the reason for failing jobs showed is
ORA-12541: TNS:no listener
Can you please tell what is the reason for this
Thanks in advance,
Prashant

Some of the failing jobs could be referencing a db link and you need to verify the tns alias being used in the database links
Use tnsping <tnsalias> to verify the connect string

Temporary error "A Crystal Reports job failed because a free license ..."

Hi all,
We coded with VS 2003 a .NET 1.1 application which using the Crystal Report 9 Redistribution package .NET ready to display reports from measured data from our device. The data is stored in a SQL Server 2000 MSDE. Crystal Report has his own DB connection to the SQL server to read the data to display the report.
Our application runs well on approx. 100 distributed installations. But on six customers installation we get this error. Actual on two customers PCs using the same DB we get the error "A Crystal Reports job failed because a free license could not be obtained in the time allocated.". This error pop up every time, when the report is shown. Although the report get shown completely.
I observed in the 'Windows Event Viewer => "System" log after the above-mentioned error following entry "Crystal Report job was delayed 2 (sec)." once for every time when the user requested a report.
I restored an empty DB on customers PC and the error don't pop up anymore.
All CR .NET assemblies have the version 9.2.3300.0. I tested also the "CrystalReportNET_keycodefix.zip", but it doesn't help. I had checked for hours all the issues about this error message on the internet. I tested the most fitting solutions, but not one fix the problem.
I tested customers full DB on my Virtual Machine with same installation, but I don't get the error.
Cheers
Ronny

Hi Ludek 
 
Thanks for your answer. I checked all the things you asked me to do on both system. 
 
Here are the results from my investigations: 
 
1) The keycode.dll was not on the not working PC. 
I copied it to the root of C: as on the working PC. I registered it with regsvr32.exe and tested the issue. 
=> The problem still exist. 
 
 
 
2) I compared the keycode on both system: 
HKLM\SOFTWARE\Crystal Decisions\9.0\Crystal Reports\Keycodes\CR Ent 
 
non working PC: 
1 AAP50-GS00000-U7000RN 131203342 3979604006 
The code is different in comparison to the working PC, because I carried out the 'CrystalReportNET_keycodefix.zip'. Before this I made an export of the above registry key. Afterwards I wasn't able to merge this export (backup) again with the registry. I assume due to the included carriage returns in the keycode. 
 
working PC 
1 XXXXX 
 
 
 
3) I used the Process Monitor and got following error during the error sequence: 
 
I list only some key entries from the hundreds of error entries. Please inform me, how I can provide you the full logger files. 
 
non working PC: 
WriteFile C:\...\Administrator.QCNIR002\Local Settings\temp\~cpe{AD83....} Fast IO Disallowed 
RegEnumKey HKCR\Drive\shellex\FolderExtensions NO MORE ENTRIES 
RegOpenKey HKLM\Software\Crystal Decisions\9.0\Crystal Reports\Database NAME NOT FOUND 
RegOpenKey HKCU\Software\Crystal Decisions\9.0\Crystal Reports\Database NAME NOT FOUND 
RegOpenKey HKLM\Software\Policies\Microsoft\Windows NT\DnsClient NAME NOT FOUND 
 
But I observed beside the results: No more entries, Name not found, Fast IO Disallowed, Buffer overflow (RegQueryKey) and Range not locked (UnlockFileSingle of printer driver) no other errors. 
 
 
working PC 
Operation: Path: Result: 
WriteFile C:\...\Administrator\Local Settings\temp\~cpe{AD83....} Fast IO Disallowed 
RegEnumKey HKCR\Drive\shellex\FolderExtensions NO MORE ENTRIES 
RegOpenKey HKLM\Software\Crystal Decisions\9.0\Crystal Reports\Database NAME NOT FOUND 
RegOpenKey HKCU\Software\Crystal Decisions\9.0\Crystal Reports\Database NAME NOT FOUND 
 
 
 
4) Service Packs 
We could only compare the file size of the Merge Module we used with the one you provided me in the above link. 
 
<table border=0 cellpadding=0 cellspacing=0>
<tr>
<td>file name</td>
<td>file size of used Merge Module</td>
<td>file size of SP1 Merge Module</td>
</tr>
<tr>
<td width=150>crnetruntime.msm</td>
<td width=100>4'764'672 Byte</td>
<td width=100>4'770'304 Byte</td>
</tr>
<tr>
<td>license.msm</td>
<td>578'048 Byte</td>
<td>578'048 Byte</td>
</tr>
<tr>
<td>reportengine.msm</td>
<td>10'701'824 Byte</td>
<td>10'905'088 Byte</td>
</tr>
</table>
 
But I tried to install SP7 on my PC and on customers PC, but I got following error after I accepted the license agreement in the setup.exe: titlebar of window 'Information', Msg: 'Failed to create Backup folder -110' and just a button 'OK'. I got into an infinit loop and I could only end the process: 'IKernel.exe'. 
Remark: I get the same error with SP5 and SP6. 
 
 
 
5) Modules - comparison of DLL's 
 
I cross checked all the DLL in Modules, which begin with CR and some other, because there were over 100 DLL's. 
 
<table x:str border=0 cellpadding=0 cellspacing=0 width=834 style='border-collapse:
collapse;table-layout:fixed;width:626pt'>
<col width=385 style='mso-width-source:userset;mso-width-alt:14080;width:289pt'>
<col width=179 style='mso-width-source:userset;mso-width-alt:6546;width:134pt'>
<col width=110 style='mso-width-source:userset;mso-width-alt:4022;width:83pt'>
<col width=80 span=2 style='width:60pt'>
<tr height=17 style='height:12.75pt'>
<td height=17 width=385 style='height:12.75pt;width:289pt'>CRHEAPALLOC.DLL</td>
<td width=179 style='width:134pt'>9.2.0.2</td>
<td width=110 style='width:83pt'>9.2.0.2</td>
<td width=80 style='width:60pt'></td>
<td width=80 style='width:60pt'></td>
</tr>
<tr height=17 style='height:12.75pt'>
<td height=17 style='height:12.75pt'>CRPE32.DLL</td>
<td>9.2.3.1183</td>
<td>9.2.3.1183</td>
<td colspan=2 style='mso-ignore:colspan'></td>
</tr>
<tr height=17 style='height:12.75pt'>
<td height=17 style='height:12.75pt'>CRQE.DLL</td>
<td>9.2.1.625</td>
<td>9.2.1.625</td>
<td colspan=2 style='mso-ignore:colspan'></td>
</tr>
<tr height=17 style='height:12.75pt'>
<td height=17 style='height:12.75pt'>CRTOWORDS_EN.DLL</td>
<td>9.2.0.14</td>
<td>9.2.0.14</td>
<td colspan=2 style='mso-ignore:colspan'></td>
</tr>
<tr height=17 style='height:12.75pt'>
<td height=17 style='height:12.75pt'>CRYSTALDECISIONS.CRYSTALREPORTS.ENGINE.DLL</td>
<td>9.3.9500.10</td>
<td>9.3.9500.10</td>
<td colspan=2 style='mso-ignore:colspan'></td>
</tr>
<tr height=17 style='height:12.75pt'>
<td height=17 style='height:12.75pt'>CRYSTALDECISIONS.REPORTAPPSERVER.CLIENTDOC.DLL</td>
<td>9.2.3300.0</td>
<td>9.2.3300.0</td>
<td colspan=2 style='mso-ignore:colspan'></td>
</tr>
<tr height=17 style='height:12.75pt'>
<td height=17 style='height:12.75pt'>CRYSTALDECISIONS.REPORTSOURCE.DLL</td>
<td>9.3.9500.7</td>
<td>9.3.9500.7</td>
<td colspan=2 style='mso-ignore:colspan'></td>
</tr>
<tr height=17 style='height:12.75pt'>
<td height=17 style='height:12.75pt'>CRYSTALDECISIONS.SHARED.DLL</td>
<td>9.3.9500.10</td>
<td>9.3.9500.10</td>
<td colspan=2 style='mso-ignore:colspan'></td>
</tr>
<tr height=17 style='height:12.75pt'>
<td height=17 style='height:12.75pt'>CRYSTALDECISIONS.WINDOWS.FORMS.DLL</td>
<td>9.3.9500.12</td>
<td>9.3.9500.12</td>
<td colspan=2 style='mso-ignore:colspan'></td>
</tr>
<tr height=17 style='height:12.75pt'>
<td height=17 style='height:12.75pt'>CRYSTALKEYCODELIB.DLL</td>
<td>9.2.3300.0</td>
<td>9.2.3300.0</td>
<td colspan=2 style='mso-ignore:colspan'></td>
</tr>
<tr height=17 style='height:12.75pt'>
<td height=17 style='height:12.75pt'>keycode.dll</td>
<td>9.0.0.281</td>
<td>9.0.0.281</td>
<td colspan=2 style='mso-ignore:colspan'></td>
</tr>
<tr height=17 style='height:12.75pt'>
<td height=17 style='height:12.75pt'>MSADCE.DLL</td>
<td>2.81.1135.0</td>
<td>2.81.1135.0</td>
<td colspan=2 style='mso-ignore:colspan'></td>
</tr>
<tr height=17 style='height:12.75pt'>
<td height=17 style='height:12.75pt'>MSADCER.DLL</td>
<td>2.81.1117.0</td>
<td>2.81.1117.0</td>
<td colspan=2 style='mso-ignore:colspan'></td>
</tr>
<tr height=17 style='height:12.75pt'>
<td height=17 style='height:12.75pt'>MSADO15.DLL</td>
<td>2.81.1128.0</td>
<td>2.81.1128.0</td>
<td colspan=2 style='mso-ignore:colspan'></td>
</tr>
<tr height=17 style='height:12.75pt'>
<td height=17 style='height:12.75pt'>MSADRH15.DLL</td>
<td>2.81.1117.0</td>
<td>2.81.1117.0</td>
<td colspan=2 style='mso-ignore:colspan'></td>
</tr>
<tr height=17 style='height:12.75pt'>
<td height=17 style='height:12.75pt'>MSCORLIB.DLL</td>
<td class=xl26>01/15/09 22:31:34</td>
<td class=xl26>7/7/08 13:39</td>
<td class=xl24></td>
<td class=xl25></td>
</tr>
<tr height=17 style='height:12.75pt'>
<td height=17 style='height:12.75pt'>sqlresld.dll</td>
<td>2000.80.382.0</td>
<td>2000.080.0382.00</td>
<td colspan=2 style='mso-ignore:colspan'></td>
</tr>
<tr height=17 style='height:12.75pt'>
<td height=17 style='height:12.75pt'>crdb_ado.dll</td>
<td>9.2.1.542</td>
<td>9.2.1.542</td>
<td colspan=2 style='mso-ignore:colspan'></td>
</tr>
</table>
 
Please specify the more detailed, if you mean the Crystal framework files or the .NET files. Could you give me please the location of the framework dlls and database client dlls like a folder name, so that I can check also all of them. 
 
I can provide you also the Module logger files, if you require them. 
 
 
I would appreciate your further help very much. 
 
Cheers 
 
Ronny
Edited by: Ronny S. on Jul 6, 2009 4:57 PM
Edited by: Ronny S. on Jul 6, 2009 5:02 PM
Edited by: Ronny S. on Jul 6, 2009 5:17 PM
Edited by: Ronny S. on Jul 8, 2009 11:44 AM
Edited by: David Hilton on Jul 15, 2009 11:04 AM
Removed private keycode.

ERROR VNIC creation job failed

Hello All,
I have brought oracle VM X86 manager into ops center 12c control. When I try to create a new virtual machine it is throwing the ‘ERROR VNIC creation job failed’ error. Can anybody throw some light over this issue.
Thanks in advance.
Detailed log is
44:20 PM IST ERROR Exception occurred while running the task
44:20 PM IST ERROR java.io.IOException: VNIC creation job failed
44:20 PM IST ERROR VNIC creation job failed
44:20 PM IST ERROR com.sun.hss.services.virtualization.guestservice.impl.OvmCreateVnicsTask.doRun(OvmCreateVnicsTask.java:116)
44:20 PM IST ERROR com.sun.hss.services.virtualization.guestservice.impl.OvmAbstractTask.run(OvmAbstractTask.java:560)
44:20 PM IST ERROR sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
44:20 PM IST ERROR sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
44:20 PM IST ERROR sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
44:20 PM IST ERROR java.lang.reflect.Method.invoke(Method.java:597)
44:20 PM IST ERROR com.sun.scn.jobmanager.common.impl.TaskExecutionThread.run(TaskExecutionThread.java:194)
Regards,
george

Hi friends
I managed to find the answer. Internally it is has some indexes in the data base level. It still maintains the indexes in the shadow tables. Those all need to be deleted. With our Basis team help I have successfully deleted those and recreated the indexes.
As Soorejkv said sap note 1283322 will help you on this to understand the scenarios.
Thank you all.
Regards
Ram

Error in Control Framework: Background job failed

Hi Experts,
One background job failed with job log: Error in Control Framework in ECC 6.0 system; the job is supposed to produce a XML report. Can anyone please give some idea on this why it could happen? One SAP note 893534 has described same kind of issue but in CRM system. That note even cant be implemeneted in ECC 6.0. Any workaround? Is it a BASIS issue here?
Thanks & Regards,
SKB

Hello,
please check the variant. We had this problem, and when checking the variant I got a shortdump because the variant did not fit to the program (there were problems with subscreens in the selection screen). After adjusting the variant with program RSVARDOC_610 the variant was ok.
I can not check if this solved the problem because the job runs weekly, and the next job is on Monday. But give it a try...
HTH,
Jens Hoetger

Report Job failed when Bursting is used in BI Publisher 11.1.1.5

The Report Job failed when Bursting is used.
error message:
[INSTANCE_ID=aimedap1s.1347261753557] [OUTPUT_ID=1421][ReportProcessor]Error rendering documentoracle.xdo.servlet.scheduler.ProcessingException: [ReportProcessor]Error rendering document
at oracle.xdo.enterpriseScheduler.bursting.BurstingReportProcessor.renderReport(BurstingReportProcessor.java:455)
at oracle.xdo.enterpriseScheduler.bursting.BurstingReportProcessor.onMessage(BurstingReportProcessor.java:127)
at oracle.xdo.enterpriseScheduler.util.CheckpointEnabl
the reproduce steps :
1. Create a Bursting query in the Data Model
2. Create Report Job with the option
"Use Bursting Definition to Determine Output & Delivery Destination" enabled
3.Schedule the report Job
4. run the report and found the status of it is problem, the error message above can be found.
*Note:not all the report job failed when bursting is used, in step1 when set OUTPUT_FORMAT as PDF,HTML,RTF,PowerPoint 2007,
the report will be run successfully,but when set other OUTPUT_FORMAT that list in the following document, the report can not run successfully.
http://docs.oracle.com/cd/E21764_01/bi.1111/e18862/T527073T555155.htm
Adding Bursting Definitions>>Defining the Query for the Delivery XML
>>OUTPUT_FORMAT
Can anyone give some advice on how to troubleshooting it?
Looking forward for your reply
Regards

Hello vma.
I happened to find the solution on 11.1.1.3. With xdo-server.jar, you can use DataProcessor class.
For details and sample source code:
http://blog-koichiro.blogspot.com/2011/11/bi-publisher-java-apigenerate-pdf-with.html
* Not sure if it works on 11.1.1.5 though, I hope this gonna help you.

[SOLVED] XOrg fails to load Nvidia driver on startup

Hi,
I'm having a fairly strange issue where XOrg is failing to load my driver when I start up my laptop. I'm using kdm, but this is causing it to fail. However, doing a simple
$sudo systemctl restart kdm
works, and everything starts up fine. When kdm is in the failed state, I see this:
$sudo systemctl status kdm
● kdm.service - K Display Manager
Loaded: loaded (/usr/lib/systemd/system/kdm.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2014-12-19 18:47:26 EST; 41s ago
Main PID: 247 (kdm)
CGroup: /system.slice/kdm.service
└─247 /usr/bin/kdm -nodaemon
Dec 19 18:47:26 laptop systemd[1]: Started K Display Manager.
Dec 19 18:47:27 laptop kdm[247]: X server died during startup
Dec 19 18:47:27 laptop kdm[247]: X server for display :0 cannot be started, session disabled
And in my XOrg log, I see:
[ 3.639]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 3.639]
X.Org X Server 1.16.2.901 (1.16.3 RC 1)
Release Date: 2014-12-09
[ 3.639] X Protocol Version 11, Revision 0
[ 3.639] Build Operating System: Linux 3.17.2-1-ARCH x86_64
[ 3.639] Current Operating System: Linux laptop 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC 2014 x86_64
[ 3.639] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw initrd=../initramfs-linux.img
[ 3.639] Build Date: 10 December 2014 02:34:24PM
[ 3.639]
[ 3.639] Current version of pixman: 0.32.6
[ 3.639] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 3.639] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 3.639] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 19 18:47:26 2014
[ 3.645] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 3.649] (==) No Layout section. Using the first Screen section.
[ 3.649] (==) No screen section available. Using defaults.
[ 3.649] (**) |-->Screen "Default Screen Section" (0)
[ 3.649] (**) | |-->Monitor "<default monitor>"
[ 3.650] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 3.650] (==) Automatically adding devices
[ 3.650] (==) Automatically enabling devices
[ 3.650] (==) Automatically adding GPU devices
[ 3.658] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 3.658] Entry deleted from font path.
[ 3.659] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 3.659] Entry deleted from font path.
[ 3.659] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 3.660] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 3.660] Entry deleted from font path.
[ 3.660] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 3.660] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 3.660] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 3.660] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 3.660] (II) Loader magic: 0x818d80
[ 3.660] (II) Module ABI versions:
[ 3.660] X.Org ANSI C Emulation: 0.4
[ 3.660] X.Org Video Driver: 18.0
[ 3.660] X.Org XInput driver : 21.0
[ 3.660] X.Org Server Extension : 8.0
[ 3.662] (EE) systemd-logind: failed to get session: PID 267 does not belong to any known session
[ 3.663] (--) PCI:*(0:1:0:0) 10de:11a1:1558:0371 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 3.663] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 3.664] (II) LoadModule: "glx"
[ 3.675] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 3.767] (II) Module glx: vendor="NVIDIA Corporation"
[ 3.767] compiled for 4.0.2, module version = 1.0.0
[ 3.767] Module class: X.Org Server Extension
[ 3.768] (II) NVIDIA GLX Module 343.36 Mon Dec 1 15:50:02 PST 2014
[ 3.769] (==) Matched nouveau as autoconfigured driver 0
[ 3.769] (==) Matched nv as autoconfigured driver 1
[ 3.769] (==) Matched modesetting as autoconfigured driver 2
[ 3.769] (==) Matched fbdev as autoconfigured driver 3
[ 3.769] (==) Matched vesa as autoconfigured driver 4
[ 3.769] (==) Assigned the driver to the xf86ConfigLayout
[ 3.769] (II) LoadModule: "nouveau"
[ 3.769] (WW) Warning, couldn't open module nouveau
[ 3.769] (II) UnloadModule: "nouveau"
[ 3.769] (II) Unloading nouveau
[ 3.769] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 3.769] (II) LoadModule: "nv"
[ 3.769] (WW) Warning, couldn't open module nv
[ 3.769] (II) UnloadModule: "nv"
[ 3.769] (II) Unloading nv
[ 3.769] (EE) Failed to load module "nv" (module does not exist, 0)
[ 3.769] (II) LoadModule: "modesetting"
[ 3.769] (WW) Warning, couldn't open module modesetting
[ 3.769] (II) UnloadModule: "modesetting"
[ 3.769] (II) Unloading modesetting
[ 3.769] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 3.769] (II) LoadModule: "fbdev"
[ 3.769] (WW) Warning, couldn't open module fbdev
[ 3.769] (II) UnloadModule: "fbdev"
[ 3.769] (II) Unloading fbdev
[ 3.769] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 3.769] (II) LoadModule: "vesa"
[ 3.770] (WW) Warning, couldn't open module vesa
[ 3.770] (II) UnloadModule: "vesa"
[ 3.770] (II) Unloading vesa
[ 3.770] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 3.770] (EE) No drivers available.
[ 3.770] (EE)
Fatal server error:
[ 3.770] (EE) no screens found(EE)
[ 3.770] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 3.770] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 3.770] (EE)
Which looks like it loads my nvidia driver, but then just decides not to use it for some reason... After I restart kdm, it seems to use the driver fine:
[ 78.897]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 78.897]
X.Org X Server 1.16.2.901 (1.16.3 RC 1)
Release Date: 2014-12-09
[ 78.897] X Protocol Version 11, Revision 0
[ 78.897] Build Operating System: Linux 3.17.2-1-ARCH x86_64
[ 78.897] Current Operating System: Linux laptop 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC 2014 x86_64
[ 78.897] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw initrd=../initramfs-linux.img
[ 78.897] Build Date: 10 December 2014 02:34:24PM
[ 78.897]
[ 78.897] Current version of pixman: 0.32.6
[ 78.897] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 78.897] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 78.897] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 19 18:48:38 2014
[ 78.897] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 78.897] (==) No Layout section. Using the first Screen section.
[ 78.897] (==) No screen section available. Using defaults.
[ 78.897] (**) |-->Screen "Default Screen Section" (0)
[ 78.897] (**) | |-->Monitor "<default monitor>"
[ 78.898] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 78.898] (==) Automatically adding devices
[ 78.898] (==) Automatically enabling devices
[ 78.898] (==) Automatically adding GPU devices
[ 78.898] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 78.898] Entry deleted from font path.
[ 78.898] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 78.898] Entry deleted from font path.
[ 78.898] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 78.898] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 78.898] Entry deleted from font path.
[ 78.898] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 78.898] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 78.898] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 78.898] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 78.898] (II) Loader magic: 0x818d80
[ 78.898] (II) Module ABI versions:
[ 78.898] X.Org ANSI C Emulation: 0.4
[ 78.898] X.Org Video Driver: 18.0
[ 78.898] X.Org XInput driver : 21.0
[ 78.898] X.Org Server Extension : 8.0
[ 78.900] (EE) systemd-logind: failed to get session: PID 542 does not belong to any known session
[ 78.900] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 78.901] (--) PCI:*(0:1:0:0) 10de:11a1:1558:0371 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 78.901] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 78.901] (II) LoadModule: "glx"
[ 78.902] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 78.913] (II) Module glx: vendor="NVIDIA Corporation"
[ 78.913] compiled for 4.0.2, module version = 1.0.0
[ 78.913] Module class: X.Org Server Extension
[ 78.913] (II) NVIDIA GLX Module 343.36 Mon Dec 1 15:50:02 PST 2014
[ 78.914] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[ 78.914] loading driver: nvidia
[ 78.914] (==) Matched nvidia as autoconfigured driver 0
[ 78.914] (==) Matched nouveau as autoconfigured driver 1
[ 78.914] (==) Matched nv as autoconfigured driver 2
[ 78.914] (==) Matched nouveau as autoconfigured driver 3
[ 78.914] (==) Matched nv as autoconfigured driver 4
[ 78.914] (==) Matched modesetting as autoconfigured driver 5
[ 78.914] (==) Matched fbdev as autoconfigured driver 6
[ 78.914] (==) Matched vesa as autoconfigured driver 7
[ 78.914] (==) Assigned the driver to the xf86ConfigLayout
[ 78.914] (II) LoadModule: "nvidia"
[ 78.914] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 78.920] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 78.920] compiled for 4.0.2, module version = 1.0.0
[ 78.920] Module class: X.Org Video Driver
[ 78.920] (II) LoadModule: "nouveau"
[ 78.921] (WW) Warning, couldn't open module nouveau
[ 78.921] (II) UnloadModule: "nouveau"
[ 78.921] (II) Unloading nouveau
[ 78.921] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 78.921] (II) LoadModule: "nv"
[ 78.921] (WW) Warning, couldn't open module nv
[ 78.921] (II) UnloadModule: "nv"
[ 78.921] (II) Unloading nv
[ 78.921] (EE) Failed to load module "nv" (module does not exist, 0)
[ 78.921] (II) LoadModule: "modesetting"
[ 78.921] (WW) Warning, couldn't open module modesetting
[ 78.921] (II) UnloadModule: "modesetting"
[ 78.921] (II) Unloading modesetting
[ 78.921] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 78.921] (II) LoadModule: "fbdev"
[ 78.922] (WW) Warning, couldn't open module fbdev
[ 78.922] (II) UnloadModule: "fbdev"
[ 78.922] (II) Unloading fbdev
[ 78.922] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 78.922] (II) LoadModule: "vesa"
[ 78.922] (WW) Warning, couldn't open module vesa
[ 78.922] (II) UnloadModule: "vesa"
[ 78.922] (II) Unloading vesa
[ 78.922] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 78.922] (II) NVIDIA dlloader X Driver 343.36 Mon Dec 1 15:28:39 PST 2014
[ 78.922] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 78.922] (++) using VT number 7
[ 78.935] (II) Loading sub module "fb"
[ 78.935] (II) LoadModule: "fb"
[ 78.935] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 78.936] (II) Module fb: vendor="X.Org Foundation"
[ 78.936] compiled for 1.16.2.901, module version = 1.0.0
[ 78.936] ABI class: X.Org ANSI C Emulation, version 0.4
[ 78.936] (II) Loading sub module "wfb"
[ 78.936] (II) LoadModule: "wfb"
[ 78.936] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 78.937] (II) Module wfb: vendor="X.Org Foundation"
[ 78.937] compiled for 1.16.2.901, module version = 1.0.0
[ 78.937] ABI class: X.Org ANSI C Emulation, version 0.4
[ 78.937] (II) Loading sub module "ramdac"
[ 78.937] (II) LoadModule: "ramdac"
[ 78.937] (II) Module "ramdac" already built-in
[ 78.939] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 78.939] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 78.939] (==) NVIDIA(0): RGB weight 888
[ 78.939] (==) NVIDIA(0): Default visual is TrueColor
[ 78.939] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 78.940] (**) NVIDIA(0): Enabling 2D acceleration
[ 79.610] (II) NVIDIA(0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 79.610] (II) NVIDIA(0): 3D Vision stereo.
[ 79.610] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
[ 79.612] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 670MX (GK104) at PCI:1:0:0 (GPU-0)
[ 79.612] (--) NVIDIA(0): Memory: 3145728 kBytes
[ 79.612] (--) NVIDIA(0): VideoBIOS: 80.04.67.00.06
[ 79.612] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 79.616] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 670MX at PCI:1:0:0
[ 79.616] (--) NVIDIA(0): Chi Mei Optoelectronics corp. (DFP-0) (boot, connected)
[ 79.616] (--) NVIDIA(0): Samsung SyncMaster (DFP-1) (connected)
[ 79.616] (--) NVIDIA(0): DFP-2
[ 79.616] (--) NVIDIA(0): DFP-3
[ 79.616] (--) NVIDIA(0): DFP-4
[ 79.616] (--) NVIDIA(0): Chi Mei Optoelectronics corp. (DFP-0): Internal LVDS
[ 79.616] (--) NVIDIA(GPU-0): Chi Mei Optoelectronics corp. (DFP-0): 330.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): Samsung SyncMaster (DFP-1): Internal TMDS
[ 79.616] (--) NVIDIA(GPU-0): Samsung SyncMaster (DFP-1): 165.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): DFP-2: Internal TMDS
[ 79.616] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): DFP-3: Internal DisplayPort
[ 79.616] (--) NVIDIA(GPU-0): DFP-3: 960.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[ 79.616] (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
[ 79.616] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 79.616] (**) NVIDIA(0): device Chi Mei Optoelectronics corp. (DFP-0) (Using EDID
[ 79.616] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
[ 79.616] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 79.616] (**) NVIDIA(0): device Samsung SyncMaster (DFP-1) (Using EDID frequencies
[ 79.616] (**) NVIDIA(0): has been enabled on all display devices.)
[ 79.618] (==) NVIDIA(0):
[ 79.618] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 79.618] (==) NVIDIA(0): will be used as the requested mode.
[ 79.618] (==) NVIDIA(0):
[ 79.619] (II) NVIDIA(0): Validated MetaModes:
[ 79.619] (II) NVIDIA(0): "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
[ 79.619] (II) NVIDIA(0): Virtual screen size determined to be 3600 x 1080
[ 80.144] (--) NVIDIA(0): DPI set to (128, 130); computed from "UseEdidDpi" X config
[ 80.144] (--) NVIDIA(0): option
[ 80.144] (--) Depth 24 pixmap format is 32 bpp
[ 80.144] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 80.144] (II) NVIDIA: access.
[ 80.150] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 80.150] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 80.150] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 80.150] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 80.150] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 80.150] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 80.150] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 80.150] (II) NVIDIA(0): Config Options in the README.
[ 80.155] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
[ 80.532] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 80.532] (==) NVIDIA(0): Backing store enabled
[ 80.532] (==) NVIDIA(0): Silken mouse enabled
[ 80.533] (==) NVIDIA(0): DPMS enabled
[ 80.533] (II) Loading sub module "dri2"
[ 80.533] (II) LoadModule: "dri2"
[ 80.533] (II) Module "dri2" already built-in
[ 80.533] (II) NVIDIA(0): [DRI2] Setup complete
[ 80.533] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 80.533] (--) RandR disabled
[ 80.539] (II) Initializing extension GLX
[ 80.605] (II) config/udev: Adding input device Power Button (/dev/input/event14)
[ 80.605] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 80.605] (II) LoadModule: "evdev"
[ 80.606] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 80.607] (II) Module evdev: vendor="X.Org Foundation"
[ 80.607] compiled for 1.16.2, module version = 2.9.1
[ 80.607] Module class: X.Org XInput Driver
[ 80.607] ABI class: X.Org XInput driver, version 21.0
[ 80.607] (II) Using input driver 'evdev' for 'Power Button'
[ 80.607] (**) Power Button: always reports core events
[ 80.607] (**) evdev: Power Button: Device: "/dev/input/event14"
[ 80.608] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 80.608] (--) evdev: Power Button: Found keys
[ 80.608] (II) evdev: Power Button: Configuring as keyboard
[ 80.608] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input18/event14"
[ 80.608] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 80.608] (**) Option "xkb_rules" "evdev"
[ 80.608] (**) Option "xkb_model" "pc104"
[ 80.608] (**) Option "xkb_layout" "us"
[ 80.635] (II) config/udev: Adding input device Video Bus (/dev/input/event15)
[ 80.635] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 80.635] (II) Using input driver 'evdev' for 'Video Bus'
[ 80.635] (**) Video Bus: always reports core events
[ 80.635] (**) evdev: Video Bus: Device: "/dev/input/event15"
[ 80.635] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 80.635] (--) evdev: Video Bus: Found keys
[ 80.635] (II) evdev: Video Bus: Configuring as keyboard
[ 80.635] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/LNXVIDEO:00/input/input19/event15"
[ 80.635] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 80.635] (**) Option "xkb_rules" "evdev"
[ 80.635] (**) Option "xkb_model" "pc104"
[ 80.635] (**) Option "xkb_layout" "us"
[ 80.636] (II) config/udev: Adding input device Power Button (/dev/input/event13)
[ 80.636] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 80.636] (II) Using input driver 'evdev' for 'Power Button'
[ 80.636] (**) Power Button: always reports core events
[ 80.636] (**) evdev: Power Button: Device: "/dev/input/event13"
[ 80.636] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 80.636] (--) evdev: Power Button: Found keys
[ 80.636] (II) evdev: Power Button: Configuring as keyboard
[ 80.636] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input17/event13"
[ 80.636] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 80.636] (**) Option "xkb_rules" "evdev"
[ 80.636] (**) Option "xkb_model" "pc104"
[ 80.636] (**) Option "xkb_layout" "us"
[ 80.637] (II) config/udev: Adding input device Lid Switch (/dev/input/event11)
[ 80.637] (II) No input driver specified, ignoring this device.
[ 80.637] (II) This device may have been added with another device file.
[ 80.637] (II) config/udev: Adding input device Sleep Button (/dev/input/event12)
[ 80.637] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 80.637] (II) Using input driver 'evdev' for 'Sleep Button'
[ 80.637] (**) Sleep Button: always reports core events
[ 80.637] (**) evdev: Sleep Button: Device: "/dev/input/event12"
[ 80.637] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 80.637] (--) evdev: Sleep Button: Found keys
[ 80.637] (II) evdev: Sleep Button: Configuring as keyboard
[ 80.637] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input16/event12"
[ 80.637] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[ 80.637] (**) Option "xkb_rules" "evdev"
[ 80.637] (**) Option "xkb_model" "pc104"
[ 80.637] (**) Option "xkb_layout" "us"
[ 80.638] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event18)
[ 80.638] (II) No input driver specified, ignoring this device.
[ 80.638] (II) This device may have been added with another device file.
[ 80.638] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event19)
[ 80.638] (II) No input driver specified, ignoring this device.
[ 80.638] (II) This device may have been added with another device file.
[ 80.639] (II) config/udev: Adding input device LOGITECH G110 G-keys (/dev/input/event3)
[ 80.639] (**) LOGITECH G110 G-keys: Applying InputClass "evdev keyboard catchall"
[ 80.639] (II) Using input driver 'evdev' for 'LOGITECH G110 G-keys'
[ 80.639] (**) LOGITECH G110 G-keys: always reports core events
[ 80.639] (**) evdev: LOGITECH G110 G-keys: Device: "/dev/input/event3"
[ 80.639] (--) evdev: LOGITECH G110 G-keys: Vendor 0x46d Product 0xc22b
[ 80.639] (--) evdev: LOGITECH G110 G-keys: Found keys
[ 80.639] (II) evdev: LOGITECH G110 G-keys: Configuring as keyboard
[ 80.639] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.1/3-4.1.1:1.0/0003:046D:C22B.0003/input/input7/event3"
[ 80.639] (II) XINPUT: Adding extended input device "LOGITECH G110 G-keys" (type: KEYBOARD, id 10)
[ 80.639] (**) Option "xkb_rules" "evdev"
[ 80.639] (**) Option "xkb_model" "pc104"
[ 80.639] (**) Option "xkb_layout" "us"
[ 80.639] (II) config/udev: Adding input device Gaming Keyboard G110 (/dev/input/event4)
[ 80.639] (**) Gaming Keyboard G110: Applying InputClass "evdev keyboard catchall"
[ 80.639] (II) Using input driver 'evdev' for 'Gaming Keyboard G110'
[ 80.639] (**) Gaming Keyboard G110: always reports core events
[ 80.639] (**) evdev: Gaming Keyboard G110: Device: "/dev/input/event4"
[ 80.640] (--) evdev: Gaming Keyboard G110: Vendor 0x46d Product 0xc22a
[ 80.640] (--) evdev: Gaming Keyboard G110: Found keys
[ 80.640] (II) evdev: Gaming Keyboard G110: Configuring as keyboard
[ 80.640] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.3/3-4.1.3:1.0/0003:046D:C22A.0004/input/input8/event4"
[ 80.640] (II) XINPUT: Adding extended input device "Gaming Keyboard G110" (type: KEYBOARD, id 11)
[ 80.640] (**) Option "xkb_rules" "evdev"
[ 80.640] (**) Option "xkb_model" "pc104"
[ 80.640] (**) Option "xkb_layout" "us"
[ 80.640] (II) config/udev: Adding input device Gaming Keyboard G110 (/dev/input/event5)
[ 80.640] (**) Gaming Keyboard G110: Applying InputClass "evdev keyboard catchall"
[ 80.640] (II) Using input driver 'evdev' for 'Gaming Keyboard G110'
[ 80.640] (**) Gaming Keyboard G110: always reports core events
[ 80.640] (**) evdev: Gaming Keyboard G110: Device: "/dev/input/event5"
[ 80.640] (--) evdev: Gaming Keyboard G110: Vendor 0x46d Product 0xc22a
[ 80.640] (--) evdev: Gaming Keyboard G110: Found keys
[ 80.640] (II) evdev: Gaming Keyboard G110: Configuring as keyboard
[ 80.640] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.3/3-4.1.3:1.1/0003:046D:C22A.0005/input/input9/event5"
[ 80.640] (II) XINPUT: Adding extended input device "Gaming Keyboard G110" (type: KEYBOARD, id 12)
[ 80.640] (**) Option "xkb_rules" "evdev"
[ 80.640] (**) Option "xkb_model" "pc104"
[ 80.641] (**) Option "xkb_layout" "us"
[ 80.641] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/event1)
[ 80.641] (**) Razer Razer Lachesis: Applying InputClass "evdev pointer catchall"
[ 80.641] (II) Using input driver 'evdev' for 'Razer Razer Lachesis'
[ 80.641] (**) Razer Razer Lachesis: always reports core events
[ 80.641] (**) evdev: Razer Razer Lachesis: Device: "/dev/input/event1"
[ 80.641] (--) evdev: Razer Razer Lachesis: Vendor 0x1532 Product 0xc
[ 80.641] (--) evdev: Razer Razer Lachesis: Found 12 mouse buttons
[ 80.641] (--) evdev: Razer Razer Lachesis: Found scroll wheel(s)
[ 80.641] (--) evdev: Razer Razer Lachesis: Found relative axes
[ 80.641] (--) evdev: Razer Razer Lachesis: Found x and y relative axes
[ 80.641] (II) evdev: Razer Razer Lachesis: Configuring as mouse
[ 80.641] (II) evdev: Razer Razer Lachesis: Adding scrollwheel support
[ 80.641] (**) evdev: Razer Razer Lachesis: YAxisMapping: buttons 4 and 5
[ 80.641] (**) evdev: Razer Razer Lachesis: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 80.641] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.2/3-4.2:1.0/0003:1532:000C.0001/input/input5/event1"
[ 80.641] (II) XINPUT: Adding extended input device "Razer Razer Lachesis" (type: MOUSE, id 13)
[ 80.642] (II) evdev: Razer Razer Lachesis: initialized for relative axes.
[ 80.642] (**) Razer Razer Lachesis: (accel) keeping acceleration scheme 1
[ 80.642] (**) Razer Razer Lachesis: (accel) acceleration profile 0
[ 80.642] (**) Razer Razer Lachesis: (accel) acceleration factor: 2.000
[ 80.642] (**) Razer Razer Lachesis: (accel) acceleration threshold: 4
[ 80.642] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/mouse0)
[ 80.642] (II) No input driver specified, ignoring this device.
[ 80.642] (II) This device may have been added with another device file.
[ 80.643] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/event2)
[ 80.643] (**) Razer Razer Lachesis: Applying InputClass "evdev keyboard catchall"
[ 80.643] (II) Using input driver 'evdev' for 'Razer Razer Lachesis'
[ 80.643] (**) Razer Razer Lachesis: always reports core events
[ 80.643] (**) evdev: Razer Razer Lachesis: Device: "/dev/input/event2"
[ 80.643] (--) evdev: Razer Razer Lachesis: Vendor 0x1532 Product 0xc
[ 80.643] (--) evdev: Razer Razer Lachesis: Found keys
[ 80.643] (II) evdev: Razer Razer Lachesis: Configuring as keyboard
[ 80.643] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.2/3-4.2:1.1/0003:1532:000C.0002/input/input6/event2"
[ 80.643] (II) XINPUT: Adding extended input device "Razer Razer Lachesis" (type: KEYBOARD, id 14)
[ 80.643] (**) Option "xkb_rules" "evdev"
[ 80.643] (**) Option "xkb_model" "pc104"
[ 80.643] (**) Option "xkb_layout" "us"
[ 80.643] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event6)
[ 80.643] (II) No input driver specified, ignoring this device.
[ 80.643] (II) This device may have been added with another device file.
[ 80.644] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event7)
[ 80.644] (II) No input driver specified, ignoring this device.
[ 80.644] (II) This device may have been added with another device file.
[ 80.644] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
[ 80.644] (II) No input driver specified, ignoring this device.
[ 80.644] (II) This device may have been added with another device file.
[ 80.644] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event9)
[ 80.644] (II) No input driver specified, ignoring this device.
[ 80.644] (II) This device may have been added with another device file.
[ 80.645] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event10)
[ 80.645] (II) No input driver specified, ignoring this device.
[ 80.645] (II) This device may have been added with another device file.
[ 80.645] (II) config/udev: Adding input device BisonCam, NB Pro (/dev/input/event17)
[ 80.645] (**) BisonCam, NB Pro: Applying InputClass "evdev keyboard catchall"
[ 80.645] (II) Using input driver 'evdev' for 'BisonCam, NB Pro'
[ 80.645] (**) BisonCam, NB Pro: always reports core events
[ 80.645] (**) evdev: BisonCam, NB Pro: Device: "/dev/input/event17"
[ 80.645] (--) evdev: BisonCam, NB Pro: Vendor 0x5986 Product 0x512
[ 80.645] (--) evdev: BisonCam, NB Pro: Found keys
[ 80.645] (II) evdev: BisonCam, NB Pro: Configuring as keyboard
[ 80.645] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/input/input23/event17"
[ 80.645] (II) XINPUT: Adding extended input device "BisonCam, NB Pro" (type: KEYBOARD, id 15)
[ 80.645] (**) Option "xkb_rules" "evdev"
[ 80.645] (**) Option "xkb_model" "pc104"
[ 80.645] (**) Option "xkb_layout" "us"
[ 80.646] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 80.646] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 80.646] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 80.646] (**) AT Translated Set 2 keyboard: always reports core events
[ 80.646] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 80.646] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 80.646] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 80.646] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 80.646] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 80.646] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 16)
[ 80.646] (**) Option "xkb_rules" "evdev"
[ 80.646] (**) Option "xkb_model" "pc104"
[ 80.646] (**) Option "xkb_layout" "us"
[ 80.646] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event20)
[ 80.646] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 80.647] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 80.647] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[ 80.647] (II) LoadModule: "synaptics"
[ 80.647] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 80.647] (II) Module synaptics: vendor="X.Org Foundation"
[ 80.647] compiled for 1.16.0, module version = 1.8.1
[ 80.647] Module class: X.Org XInput Driver
[ 80.647] ABI class: X.Org XInput driver, version 21.0
[ 80.647] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 80.647] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 80.647] (**) Option "Device" "/dev/input/event20"
[ 80.756] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5662 (res 42)
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4660 (res 47)
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 80.757] (**) Option "TapButton1" "1"
[ 80.757] (**) Option "TapButton2" "2"
[ 80.757] (**) Option "TapButton3" "3"
[ 80.757] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 80.757] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 80.810] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio2/input/input22/event20"
[ 80.810] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 17)
[ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.038
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 80.810] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 80.811] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
[ 80.811] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 80.811] (II) config/udev: Adding input device PC Speaker (/dev/input/event16)
[ 80.811] (II) No input driver specified, ignoring this device.
[ 80.811] (II) This device may have been added with another device file.
[ 88.265] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 88.265] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 88.282] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 88.282] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 88.291] (II) NVIDIA(0): Setting mode "LVDS-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, HDMI-0: 1680x1050_60_0 @1680x1050 +1920+0 {ViewPortIn=1680x1050, ViewPortOut=1680x1050+0+0}"
[ 89.221] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 89.221] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 90.639] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 90.639] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 93.745] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 93.745] (II) NVIDIA(GPU-0): 3D Vision stereo.
Notably, the following lines appear in the working case, but not the broken case:
[ 78.914] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[ 78.914] loading driver: nvidia
Does anyone know what might be going on here?
Last edited by straemer (2014-12-20 13:03:58)

Hmmmm, that doesn't seem to be the issue. I have a nvidia geforce gtx 670mx. The nvidia website does link me to the 340xx driver for that card, but downgrading to that version still has the same issue. I suspect the issue is in Xorg, since it seems to load the module, but then decides it doesn't have a driver to run for some reason.

Background jobs failing with ABAP/4 processor: RFC_CONVERSION_FIELD

Hi Guru's,
Below are the backgroud jobs failing with runtime Error " ABAP/4 processor: RFC_CONVERSION_FIELD" in solution manager system (solution manager 3.0,SR2). Not sure why all these jobs failing with this dump on of sudden. i haven't made any changes to the system in the recent past.
BTC_CMS_COLLECTOR
SAP_APPLICATION_STAT_COLLECTOR
SESS_Y000001806_COLL_TRANS
ABAp Dump says that
Conversion error between two character sets
What happened?
Conversion error "ab_rfccon" from character set 4103 to character set 1100.
When executing a remote function call a conversion error occurred. This
occurred when receiving or sending the data. The conversion error can
only appear, when the data is transferred from a Unicode system to a
non-Unicode system.
Could some one please share some information if any one experienced the issue. Please note that all of our ECC systems are uni-code systems.
Thanks & Regards,
Vinod.

Hi Vinod
Just try to understand the purpose of these jobs and may be these Notes will help you
Note 814707 - Troubleshooting for RFC connections Unicode/non-Unicode
Note 647495 - RFC for Unicode ./. non-Unicode Connections
Note 1361970 - Conversion problems during RFC communication

SSIS job fails on connection to target db - works in debug

the ongoing saga...
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. The SQL Server Agent job owner is sa ...that seemed to resolve some issues as originally I had the owner being another
admin on the same box. Now the job seems to be failing on connect to the target database on an IBM iSeries DB2 server. The job runs fine in debug connecting to the db and doing its task successfully.
The log indicates that the user specified in the connection manager is using an invalid password or is otherwise unable to connect, although it works fine in debug mode and save password is specified.  I use BIDS remote desktoped to the server
when developing and debuging.
Can anyone show me whats wrong now? Thanks much in advance for any help, Roscoe
The log shows as follows...
The job failed. The Job was invoked by User DOMAINNAME\myuserid. The last step to run was step 1 (Step1).,00:00:00,0,0,,,,0
06/12/2014 13:34:50,runWebDevSmall,Error,1,NTSVR59,runWebDevSmall,Step1,,Executed as user: WINDOWSSERVRNAME\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 10.0.5500.0 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights
reserved.    Started: 1:34:50 PM Error: 2014-06-12 13:34:50.31     Code: 0xC0016016     Source:       Description: Failed to decrypt protected XML node "DTS:Password"
with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error:
2014-06-12 13:34:50.84     Code: 0xC0202009     Source: vbTestsmall Connection manager "iSeriesname.DBNAME.iSeriesuserid"     Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE
DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "IBMDA400 Session" Hresult: 0x80004005 Description: "CWBSY0002 - Password for user iSeriesuser on system iSeriesname is not
correct ". End Error Error: 2014-06-12 13:34:50.86     Code: 0xC00291EC     Source: clear iSeriesname libraryname tablename Execute SQL Task     Description: Failed
to acquire connection "iSeriesname.DBNAME.iSeriesuserid". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error DTExec: The package execution returned DTSER_FAILURE (1).
Started: 1:34:50 PM Finished: 1:34:50 PM Elapsed: 0.703 seconds. The package execution failed. The step failed.,00:00:00,0,0,,,

Hi Arthur, Thanks for the reply,
BIDS would not let me save the package with ProtectionLevel of ServerStorage giving error...
Failed to apply package protection with error 0xC0014061 "The protection level, ServerStorage, cannot be used when saving to this destination. The system could not verify that the destination supports secure storage capability.". This error occurs when saving
to Xml.
(vbTestsmall)
...but it would let me change the ProtectionLevel to EncryptSensitiveWithPassword so I did that and provided the jobstep in the agent with the password and the agent was able to run successfully.
Thanks for all the help...I will follow your blog, Roscoe

The Job Failed Due to MAX-Time at ODS Activation Step

Hi
I'm getting these errors "The Job Failed Due to MAX-Time at ODS Activation Step" and
"Max-time Failure"
How to resolve this failure?

Hi ,
You can check the ODs activation logs in ODs batch montior >> click on taht job >>> job log
for this first you check in sm37 how many jobs are running if there are many otehr long running jobs then . the ODs activation will happen very slowly as the system is overloaded .. due to the long running jobs ..this causes the poor performance of system ..
for checking the performance of system .. you first check the lock waits in ST04..and check wether they are progressing or nt ..
check sm66 .. for the no of process running on system ..
check st22 >> for short dumps ..
check Os07> to check the cpu idle tiem if its less tehn 20% . then it means the cpu is overlaoded .
check sm21 ...
check the table space avilable in st04..
see if the system is overlaoded then the ODS wont get enough work process to create the backgorund jobs for that like(Bi_BCTL*)..jobs .the updation will happen but very slowly ..
in this case you can kill few long running jobs which are not important .. and kill few ODs activations also ..
Dont run 23 ODs activation all at a time .. run some of them at a time ..
And as for checking the key points for data loading is check st22,cehck job in R/3 , check sm58 for trfc,check sm59 for Rfc connections
Regards,
Shikha

I have Process chains as well as some jobs which run.Most of the data is l

Hi Experts,
I have Process chains as well as some jobs which run.Most of the data is loaded through custom ABAP extracts.Now where to check for these jobs and how to understand them.I know that we can check for jobs in sm37.But how do u load data using these jobs.Please tell me in detail how and where u execute these jobs.Please give me an answer

For creating a job use..transaction sm36.Define start condition ,periodicity. etc..
To monitor it you can use--sm37 job monitoring
Various options in sm37 which you can use after check(tick) on any particulur job..and then click on joblog.
To view variants of any job click step>goto(top menu bar)>variant.
,rsmo ( process monitor) -- to view data load--you can view there data load daywise..here to view any particulur data load..click on infopackage /dtp/datasource in rsa1 and click on the monitor icon at the top..system will show you the concerned dataloads in process monitor
For monitoring process chains--go in RSPC and double click on the chain and click on log button(yellow color) select data range..and you can view the status of a chain....red if failed and green if success..and yellow if still running.
Also in sm37 you can find the status of a process chain by searching with job name---bi_process_trigger.
To execute chaingo to RSPC>double click on the chain-->schedule(F8)
If you know the data target of loading ,go in rsa1 and right click on the data target and select manage and you can view the request being loaded.

Data services job failes while insert data into SQL server from Linux

SAP data services (data quality) server is running on LInux server and Windows. Data services jobs which uses the ODBC driver to connect to SQL server is failing after selecting few thousand records with following reason as per data services log on Linux server. We can run the same data services job from Windows server, the only difference here is it is using SQL server drivers provided by microsoft. So the possible errors provided below, out of which #1 and #4 may not be the reason of job failure. DBA checked on other errors and confirmed that transaction log size is unlimited and system has space.
Why the same job runs from Windows server and fails from Linux ? It is because the ODBC drivers from windows and Linux works in different way? OR there is conflict in the data services job with ODBC driver.
===== Error Log ===================
8/25/2009 11:51:51 AM Execution of <Regular Load Operations> for target <DQ_PARSE_INFO> failed. Possible causes: (1) Error in the SQL syntax;
(2)6902 3954215840 RUN-051005 8/25/2009 11:51:51 AM Database connection is broken; (3) Database related errors such as transaction log is full, etc.; (4) The user defined in the
6902 3954215840 RUN-051005 8/25/2009 11:51:51 AM datastore has insufficient privileges to execute the SQL. If the error is for preload or postload operation, or if it is for
===== Error Log ===================

this is another method
http://www.mssqltips.com/sqlservertip/2484/import-data-from-microsoft-access-to-sql-server/
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

SQL Server agent job failing to back up database

I have set up a SQL server agent job to back up database on regular basis.. For some reason the back up fails.. Could not find any meaningful info in the logs.. Transaction logs are getting created for the same DB but not the database back up..
The below is my environment..
MS SQL Server 2005 - 9.00.1399.06
Windows 2003 server SP2
Any pointers would be helpful.. I checked the event logs and the agent logs and did not see obvious error.
Thanks

I have set up a SQL server agent job to back up database on regular basis.. For some reason the back up fails.. Could not find any meaningful info in the logs.. Transaction logs are getting created for the same DB but not the database back up..
The below is my environment..
MS SQL Server 2005 - 9.00.1399.06
Windows 2003 server SP2
Any pointers would be helpful.. I checked the event logs and the agent logs and did not see obvious error.
Thanks
NO answer can be provided unless you show us the error message. There can be numerous reasons for backup job to fail. See job history for details please post complete information present in job history.
Check errorlog and note what error message is there at time when the backup job failed. You could find something useful. Please learn how to post question in forum just saying I have a problem will not help both of us.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

CO_COSTCTR Archiving Write Job Fails

Hello,
The CO_COSTCTR archiving write job fails with the error messages below.
Input or output error in archive file \\HOST\archive\SID\CO_COSTCTR_201209110858
Message no. BA024
Diagnosis
An error has occurred when writing the archive file \\HOST\archive\SID\CO_COSTCTR_201209110858 in the file system. This can occur, for example, as the result of temporary network problems or of a lack of space in the fileing system.
The job logs do not indicate other possible causes. The OS and system logs don't have either. When I ran it in test mode it it finished successfully after long 8 hours. However, the error only happens during production mode where the system is generating the archive files. The weird thing, I do not have this issue with our QAS system (db copy from our Prod). I was able to archive successfully in our QAS using the same path name and logical name (we transport the settings).
Considering above, I am thinking of some system or OS related parameter that is unique or different from our QAS system. Parameter that is not saved in the database as our QAS is a db copy of our Prod system. This unique parameter could affect archiving write jobs (with read/write to file system).
I already checked the network session timeout settings (CMD > net server config) and the settings are the same between our QAS and Prod servers. No problems with disk space. The archive directory is a local shared folder \\HOST\archive\SID\<filename>. The HOST and SID are variables which are unique to each system. The difference is that our Prod server is HA configured (clustered) while our QAS is just standalone. It might have some other relevant settings I am not aware of. Has anyone encountered this before and was able to resolve it?
We're running SAP R3 4.7 by the way.
Thanks,
Tony

Hi Rod,
We tried a couple of times already. They all got cancelled due to the error above. As much as we wanted to trim down the variant, the CO_COSTCTR only accepts entire fiscal year. The data it has to go through is quite a lot and the test run took us more that 8 hours to complete. I have executed the same in our QAS without errors. This is why I am bit confused why in our Production system I am having this error. Aside that our QAS is refreshed from our PRD using DB copy, it can run the archive without any problems. So I made to think that there might be unique contributing factors or parameters, which are not saved in the database that affects the archiving. Our PRD is configured with High availability; the hostname is not actually the physical host but rather a virtual host of two clustered servers. But this was no concern with the other archiving objects; only in CO_COSTCTR it is giving us this error. QAS has archiving logs turned off if it’s relevant.
Archiving 2007 fiscal year cancels every after around 7200 seconds, while the 2008 fiscal year cancels early around 2500 seconds. I think that while the write program is going through the data in loops, by the time it needs to access back the archive file, the connection has been disconnected or timed out. And the reason why it cancels almost consistently after an amount of time is because of the variant, there is not much variety to trim down the data. The program is reading the same set of data objects. When it reaches to that one point of failure (after the expected time), it cancels out. If this is true, I may need to find where to extend that timeout or whatever it is that is causing above error.
Thanks for all your help. This is the best way I can describe it. Sorry for the long reply.
Tony

Some jobs fail BackupExec, Ultrium 215 drive, NW6.5 SP6

Similar Messages

Maybe you are looking for