T450s Thinkpad - ERROR 2101: Detection error on SSD1 (M.2)

Model: T450sEquiped as:Intel i54+4GB RAM256GB SSD (M.2) Configured as boot disk running Win 7 x64500GB HDD as additional storage Issue:Seemingly at random, approx once every one to two weeks while PC is on and at the desktop but not actively being used (meaning no user is sitting in front of it performing tasks) it will error and crash. The error is a black screen with the following error: 2101: Detection error on SSD1 (M.2) Press Esc to continue. According to the user Esc does nothing and the only escape is to long press the physical power button until a power down occurs. On reboot the system comes up without issue. No user has actually seen the crash take place. MY QUESTION(S):1st. Is this most likely an issue with the T450s not being able to reliably boot from the m.2 slot or is this more likely an issue with the SSD installed in the m.2 slot?2nd. Is this something altogether different? Any (knowledgeable) advice or info appreciated.

It is hard to diagnose without seeing it, but my experience has been that the Gen4 and later CPUs (like yours) support a very low power state that is incompatible with some devices. (that would make it a problem with the card) Make sure you have the latest BIOS and power manager software installed. Look in the device manager and find the M.2 SSD. There should be a power management tab. Turn off the option to allow the system shut the device off to save energy.

Similar Messages

Error 2101 Detection error on HDD2 (mini sata) X220

running 1.40 biosthink I have WWAN model as there is a SIM slot and there are a red and blue wires ready for the 3G wireless card.all lenovo drivers etc checked to latest versionsInstalled 128GB Kingspan which failed to do anything and caused the whole system to be unbootable. Turns out the ssd was dead as it did not work in working usb enclosure.swapped in 64GB msata minipci from my old eee901 it is the correct size for the lenovo slot - it wasn't for the 901 and I am now getting 2101 Detection Error on hdd2 on boot up.I have tried reseating the card, cleaning the pins, reseating, booting to Hirens, Slacko, Gparted, Fedora and not been able to see it as the error code is pre OS... Anything I can do? - roll back drivers, roll back bios, buy specific brand msata any suggestions welcome :-)

Ram speed is not the issue I mentioned the speed purely in response to
comment relating to the bios and ram speed.
Because i would like to multiboot I would like to get an ssd to run in the
msata slot, which is currently empty. I bought a 128GB Kingspan ssd that
did "nothing" in the slot and refused to even let the x220 boot (I tried
booting from the ultrabase and from the laptop) i tried reseating the ssd a
number of times but the laptop would not boot with it in the msata slot.
And the Kingspan ssd did nothing in a working external msata enclosure and
is being returned.
I have an old m-factor 64GB ssd from my eee901 (with 2 or 3 mixed format
partitions on it) and I tried that in the x220 at which point I received
the 2101: Detection error on hdd2. I tried reseating the ssd to no avail
and tried cleaning the contacts with rubbing alcohol and reseated it but
still keep getting the error.
What I do not know is if the x220 is a wwan model does it need a specific
brand of msata ssd to work in the slot? E.G. the Intel 80GB + that are
mentioned in the forums.
Re Bios: According to the readme file attached to the older bios versions
that are available from lenovo there were some fixes for the wwan models
that related to the ssds which is why I asked about rolling back the bios
in the hope that an earlier bios might work the ssd in the msata slot.
(Rather as the later bios restricts the speed of the ram...)
Thanks again for all of your help. I'm new to messing around with the x
series and don't know all of the quirks etc :-)

W520: PNY XLR8 240GB SSD with error "2100: Detection Error on HDD0 (Main HDD)"

When I try to boot my W520, I get a BIOS boot up error : "2100: Detection Error on HDD0 (Main HDD)". I am using PNY XLR8 240GB SSD.
It worked fine for a month.
I also have PGP installed and whole disc encrypted.
I installed an update of Intel Management Engine Firmware and Intel Chipset, both are the latest from lenovo site because I was experiencing expreme slowness from my harddrive. Programs would freeze. Webpages would take forever to load..
The next time I rebooted, I got the error. If I leave the SSD out for a bit, and put the SSD back in, the disk will work for some time... but on next reboot, it is again detection error..
TRIM is enabled on my system. I am not sure how the SSD died so quickly.
I am back to using my HDD but I am not happy. I want a solution... is this a intel chipset issue? Intel IMEI issue? Is the PNY SSD just a bad model?
I've googled plenty and dont really see a solution. Sometimes there is a firmware update.. PNY has no firmware updates for my drive.. I don't see anybody else using PNY on their W520, but plenty of people are experiencing Error 2100 with SSD on their W520.. somethings fishy..
help please! thanks in advance !

No go, the drive is in there pretty firmly, a tech support to PNY said they are going to replace my drive.
They came to the same conclusion I did - which is that the drive is toast..
Drive slow downs and eventually unable to detect points to this.. I was hoping for some firmware update. I am really surprised an SSD died because I thought the whole point of them - no spinning parts - would make them last longer.. but there is some sort of logic board and maybe the flash drive itself went kaput.. who knows.
They do have 3 year warranty on my mode and i'm happy to take it. Luckily my old HDD was still around and works.. so thats what i'll be using for the next few weeks while I ship this to them and have them send me a new one.
I asked about Advanced replacement, which is when they send me a new one before they recieve my current ssd. They said the Advanced replacemenet costs $30, and they would need credit card info to place a charge of the original amount for the drive incase I didnt send in the drive too. So it would cost me $30 plus temporary $100-150 or so... which I opted not to do... So I wait now for a few weeks. I dont know if I'll get another PNY drive in the future. OCZ has faired pretty well for me, I've had 3 of them work on desktops/laptops flawlessly.

2100: Detection error on HDD0 (Main HDD)

I have a Lenovo ThinkPad Yoga, with a 256GB SSD and an i5 processor.
I received it on April 29. After two weeks of normal use, it crashed and gave this error:
“2100: Detection error on HDD0 (Main HDD)”
I could not get it to boot. I took it to a computer repair shop and they (Lenovo warrantee) replaced the SSD. It worked for about a week, then crashed again, same error. My tech guy said that it might be a bad board, frying hard drives; but Lenovo insisted on replacing the hard drive again. Ten days later, same crash. I unplugged it and put it on a shelf for the weekend, intending to take it back to the shop. Monday morning I plugged it in and it started up normally.
It has been working normally for three days, but I am worried about getting the same error and crash. Can you tell me what might be happening, and if there is anything I can do to prevent a recurrence?
This seems to be a common problem across many machine models, but I haven't found any solutions to it.
Solved!
Go to Solution.

Thanks!
Funny, my post was dated 7/15/2014. That article is dated 7/17/2014. Someone might be listening
http://support.lenovo.com/en_US/detail.page?DocID=HT082504
Will test it out, hopefully it works.
-Sloppy

T450s: 2100: Detection error on HDD0 (Main HDD)

Hi,I got T450s with 500GB HDD which I replaced with 500GB SSD Crucial MX200.After installing Windows 8.1 Pro, turning on bitlocker and restarting machine, I saw black screen with white text: 2100: Detection error on HDD0 (Main HDD) usually if I power off laptop and turn it on again, problem gets solved and I can start Windows, but then after restarting computer again the error is usually there again... I've noticed that if I turn off the bitlocker, the problem doesn't appear (at least I wasn't able to encounter it without bitlocker). I saw threads about similar problems with this and other thinkpad models as well as crucial and samsung SSDs, but none was actually reporting that it may be connected with bitlocker functionality... (I can't be 100% sure it is, but so far it looks like it). any idea how I can fix it so that it works also when bitlocker is enabled? Thanks!

I have exactly the same problem too with a T550 and a 1TB Crucial MX200. Did you ever find a solution? I'm tempted to return the MX200 and try a Samsung 850 EVO instead.

2100: Detection error on HDD0 (Thinkpad Yoga)

I have a Thinkpad Yoga which today was turned on while I was away (i.e. computer was not in use). When returning back the screen said "2100: Detection error on HDD0 (Main HDD)". Windows must have crashed (probably just another one of those faulty Lenovo drivers) and then the system couldn't boot up.
Everything seems alright after a hard reboot but I'm afraid my SSD drive has gone bad.
Link to image
Found a support document of the error on Thinkpads with Samsung SSD, but mine have a LiteOn. Can anyone help me find out why this happened and if anything is wrong with my SSD?
Thanks,
// Måns
The support document I'm talking about: http://support.lenovo.com/us/en/documents/ht082504
Moderator note: large image(s) converted to link(s): About Posting Pictures In The Forums

Hi guys,
had the same error and found out, that the cable from Motherboard to HDD controller was not plugged in correctly.
After plugin correctly the error disappeared.
Hope to help you.
BR, David

Detection Error 2100 - Lenovo X240 with Crucial M500 SSD

I have a new Lenovo X240 out of the box. I immediately upgraded with a Crucial M500 SSD 240mb drive. The computer is running a fresh install of Windows 7 64-bit. The BIOS on the laptop is the most current. The firmware on the M500 is the most current. It seems that every several times I start or reboot the system I receive "DETECTION ERROR 2100". After powering off the machine and powering it on again the computer will boot to Winddows.
I have seen numerous posts about this issue between Crucial vs. Lenovo. I've tried every suggested fix to no avail. I have tried the configuration using an identical, brand new M500 SSD with the same results. Am I missing something?
Thanks in advance for your suggestions,.

Hi Mrtree,
Welcome to Lenovo Community Forums!
I’m sorry to hear that you are facing the issue with SSD drive on ThinkPad X240.
Regarding the issue we have got the same thread in the forum, but it is different model.
I suggest you to chect with the below link to follow the further troubleshooting steps.
Please click here to visit the page, and proceed with the steps provided in that.
Hope this helps. Do post back if issue persists!
Best regards,
Hemanth Kumar
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Detection Error 2100 - M500 SSD in Lenovo X240 laptop

I have a new Lenovo X240 out of the box. I immediately upgraded with a Crucial M500 SSD 240mb drive. The computer is running a fresh install of Windows 7 64-bit. The BIOS on the laptop is the most current. The firmware on the M500 is the most current. It seems that every several times I start or reboot the system I receive "DETECTION ERROR 2100". After powering off the machine and powering it on again the computer will boot to Winddows. I have seen numerous posts about this issue between Crucial vs. Lenovo. I've tried every suggested fix to no avail. I have tried the configuration using an identical, brand new M500 SSD with the same results. Am I missing something?
Thanks in advance for your suggestions,.

Hello mrtree and welcome to the Crucial forum. I spotted your post yesterday and spent some time Googling for info from the Lenovo support forum last night. I found several things you are probably aware of. First, this Detection Error 2100 is not limited to just the X240 series laptops, there are quite a few other models affected in the same way. Second, it is not limited to only Crucial SSDs, there are people with Samsungs, Toshibas, Intels, and even conventional drives that have experienced this same problem at system boot. These two observations indicate to me that problem is probably related to BIOS/firmware/driver issues. Since you have stated that you already installed the latest BIOS(v. 2.23?) and firmware(chipset v. 9.5.22.1760?), that leaves one area: drivers. From what I can see, the latest Intel RST drivers available are version 12.8.10.1005, dated 1/26/2014. Please be aware that there are seperate downloads for 32 and 64 bit systems. There is also a Solid State Drive Firmware Update Utility listed, but I do not recommend using it since Crucial M500s are not listed in the "Read Me" notes. Which brings up the question of SSD firmware, do you have the MU03 or MU05 firmware installed on your Crucial SSDs? Also, just to double check, do you have AHCI mode enabled in your BIOS settings? You'd be surprised at how many people overlook this. I suppose that Lenovo will get around to releasing updated software addressing this issue, as they have for the other brands of SSD drives, it's just a question of when. Edit: Two more things I thought of after my initail post. First, did you order your M500 directly from Crucial? When I ordered the M500 for my Lenovo T400 Thinkpad, I went to the website and used the advisor to find the M500 part number for my machine. I called to order several days later, and when I gave the part number to the customer representative, she immediately replied "that's for a Lenovo T400, correct?". That tells me there is a part number that is specific to the T400 series, and this may also be the case with the X240 series. Ordering from an online retailer or purchasing the M500 from a store may not have given you the correct part. Second, does your machine have Intel's Management Engine firmware installed, and do you have it enabled? Try entering BIOS and disabling it, just to see if this problem persists. I've noticed that on my T400, when I boot from the DVD drive or a USB stick, I see a brief warning message from the Management Engine stating that I'm not using the normal boot device, but then my machine boots regardless. Perhaps it's causing some sort of grief for your machine.

How can I configure ReFS to NOT fail read operations when a checksum error is detected (on non-Storage-Spaces volumes where data integrity streams are enabled)?

According to William Stanek, in his Windows Server 2012 R2 Inside Out: Configuration, Storage & Essentials book, this is apparently possible: (pg. 615 - here it is on Google Books: https://books.google.ca/books?id=0IyfBAAAQBAJ&pg=PT819&lpg=PT819&dq=read+operation )
Integrity can be enabled when the system is not running on Storage Spaces. When
integrity is enabled and ReFS detects a checksum mismatch, ReFS logs an event and
fails the read operation by default. If you don’t want the read operation to fail, you
can configure ReFS to continue with the read operation. A related event will be logged
regardless.
So then how do I configure it to do that???
(And just to make it super-clear, I'm NOT using Storage Spaces, so there is no redundancy via mirroring/parity, and I'm not expecting any file repair - just detection of corruption. It's just a basic volume formatted with ReFS and
with integrity streams enabled, via format E: /fs:ReFS /i:enabled
For those who want more details, here's the situation:
I try to perform a read operation on a file with corrupted data (purposely done for testing using a low-level disk editor), I get a the following error message:
And an event ID 133 from ReFSv1 gets logged in the System log:
Clicking "Try Again" just brings up the same message, and clicking "Skip" skips the operation entirely.
This is indeed the correct default behaviour.
What I want instead is for the read operation to be allowed to complete, with corrupt data and all, and ONLY for the event to be logged. And according to William Stanek, this is supposed to be configurable somewhere - and after hours of searching, I haven't
been able to find anything.

Hi Tommy,
>>How can I configure ReFS to NOT fail read operations when a checksum error is detected
We can use PowerShell command Set-FileIntegrity to configure this. The specific parameter for controlling this behavior is
-Enforce <Boolean>which indicates whether to enable blocking access to a file if integrity streams do not match the data.
Regarding this point, the following article can be referred to as reference.
Set-FileIntegrity
https://technet.microsoft.com/en-us/library/jj218351.aspx
Best regards,
Frank Shen
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Solution - Battery error is detected. Irreparable damage to the battery has been detected. Replace

I own a T61 7658 I bough on 2008, it worked great with the default power settings until October 22nd I decided to change my power profile to MAXIMUM PERFORMANCE.
Next day I received on Message Center...
10/23/2010 - Battery health is critical. With the current system settings and a full charge, your battery can provide approximately 3.0 hours of use. A new battery could provide up to an estimated 5.5 hours.
I kept using the Laptop with the Max performance until...
11/12/2010 - Battery error is detected. Irreparable damage to the battery has been detected. Replace the battery with a new one.
I have used IBM/Lenovo for years and even had used batteries for 5 years without a single issue.
I have read many posts of people having the same problem not only with T61s, but many other Lenovo models, and also read posts of Lenovo's administrators suggesting this is normal and justifying that batteries should be good for at least 12 months and after that we are on own, basically meaning we should be thankful in name of our own safety that we had that battery protection and we must replace it at our own cost and forget about it. That is a very easy way out, isn’t it.
But certainly, not only batteries with more than 12 months are failing, even new batteries are and have been replaced with multiple exchange programs posted by Lenovo in their website just as in http://download.lenovo.com/lenovo/content/batt/082009/LandingPage.html. and also in multiple MIGR battery replacement campaigns available to all online as well.
Good thing here is that Lenovo has recognized the problem and has exchange the batteries still under warranty and also few of the batteries without warranty limiting to some serial numbers on the MIGR battery replacement campaigns, but the bad side is that Lenovo is leaving behind other clients like me and many others not being selected for replacement. But I’m sure we all have a good battery but turned useless due to the Lenovo programmed safety temperature limits in the power manager and the battery board. Please let me explain.
This is my conclusion. There is nothing wrong with used or new batteries or their cells in 99% of the cases, I'm sure my battery is okay although is being turned useless by the battery protection feature on my T61.
Lenovo must recognize the problem is the settings they have programmed on the power manager and battery protection board. It is very understandable that when users select a Power Scheme that demands higher amounts of power to generate better performance on the system this also demand additional power generating heat on battery and on the power supply as the computer is running at full performance, just as happens on my ipod when watching video, or in my kid’s R/C truck when running continuously and will happen with any other battery powered device.
Therefore any scheme requiring performance is generating heat and is tripping the battery protection and this is not a client’s fault, as are we just using an available scheme provided on our Lenovo system. If the battery protection is not calibrated to support this power demand, then there is a poor design/testing of the capabilities of the system and the battery protection parameters that instruct the battery to save itself from a fire or burning … which is understandable.
The bad side is that there is not possible reset option for the end users, the only option is to buy a new battery at our own cost after the 12 months of warranty, when the cause of the problem is originated in the computer system design settings and can happen at any time, that is way, the system warned me, as in:
10/23/2010 - Battery health is critical. With the current system settings and a full charge, your battery can provide approximately 3.0 hours of use. A new battery could provide up to an estimated 5.5 hours.
The computer is saying! At maximum performance, You are using too much power, and my battery will last just 3 hrs (9 cells on my system) instead of the 5.5 hrs that should last. But not only the running time was reduced, the heat on the power supply system and Battery was also increased due to the higher power demand, the battery can not handle the demand and protect itself to prevent fire or damage.
So who has to pay for this? Can Lenovo do something about it? For us client and for future clients? This not a matter of having or not having warranty, this can happen at any time in any computer.
I'm writing this hoping to be heard and supported and I hope LENOVO provides a satisfactory solution to the issue. I'm not going to say will never buy Lenovo again I already did, I invested my money on Lenovo and with warranty or not I'm looking forward to get a decent response.
Lenovo must change the parameters for tripping battery protection probably handled at BIOS level, and to provide a reset feature to all "locked" batteries there is many people that has lost at least one battery, some other more than that.  Since even if we get a replacement, the chances  the issue will continue is there, as long as I select a high power demand scheme the problem sooner or later will be back.   Even car makers support their clients beyond the warranty if they detect that the issue compromises safety and their reputation.  Fix it.
M.Padron.

amtho, welcome to the forum,
start by looking at this site and also look at this site which is actually linked to from the first one.
Hope this helps
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog

JSPM: Error while detecting start profile for instance with ID _c.

Hi Experts,
we have an error when we start JSPM with message "cannot initialize application data. Error while detecting start profile for instance with ID _c." . Until now nothing has been updated yet. The system can be started up and shut down without any problem. The profiles are found in /usr/sap/PMA/SYS/profile
Our BI system is currently Netweaver 7.0 with SPS14. We plan to update it to SPS20. But when we start JSPM, we have abover error.
could somebody give a help? Thank you very much.
Rongfeng
P.S. the log file DETECT_SYSTEM_PARAMETERS_01.LOG:
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/log/log_2009_11_18_10_28_50/DETECT_SYSTEM_PARAMETERS_01.LOG]/>
<!PATTERN[DETECT_SYSTEM_PARAMETERS_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
#1.5^H#C000995FC0200000000000207BD47BD40004789C01294DB0#1258511336558#/System/Server/Upgrade/JSPM##com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:397)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:397)#Java###Initializing JSPM data model...##
#1.5^H#C000995FC0200000000000217BD47BD40004789C01295968#1258511336561#/System/Server/Upgrade/JSPM##com.sap.sdt.jspm.gui.InitialParametersDetector.detectProfileDirectory(InitialParametersDetector.java:1468)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectProfileDirectory(InitialParametersDetector.java:1468)#Java###Detected profile directory .#1#/usr/sap/PMA/SYS/profile#
#1.5^H#C000995FC0200000000000227BD47BD40004789C0141AFE0#1258511338156#/System/Server/Upgrade/JSPM##com.sap.sdt.jspm.gui.InitialParametersDetector.detectDb(InitialParametersDetector.java:936)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectDb(InitialParametersDetector.java:936)#Java###Detecting the parameters of the database...##
#1.5^H#C000995FC0200000000000237BD47BD40004789C014205D0#1258511338178#/System/Server/Upgrade/JSPM##com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:261)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:261)#Java###Executing command with arguments .#2#dbinfo#/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/config/DBINFO.XML#
#1.5^H#C000995FC0200000000000247BD47BD40004789C01421570#1258511338182#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#Java###Java process ID , name has been started.#2#5#com.sap.sdt.dmt.main.DMT#
#1.5^H#C000995FC0200000000000257BD47BD40004789C01421958#1258511338183#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#Java###Command line: #2# #/opt/IBMJava2-amd64-142/jre/bin/java -cp .:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/sdt_dmt.jar:/oracle/client/10x_64/instantclient/ojdbc14.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/jddi.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/opensqlsta.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/tc_sec_secstorefs.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/frame.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/exception.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/logging.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/jperflib.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/util.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/./lib/tc_sec_secstorefs.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/./lib/exception.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/./lib/logging.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/./lib/opensqlsta.jar:/sapmnt/PMA/global/security/lib/tools/info/IAIKSecurityFS.list:/sapmnt/PMA/global/security/lib/tools/iaik_jce.jar:/sapmnt/PMA/global/security/lib/tools/iaik_smime.jar:/sapmnt/PMA/global/security/lib/tools/iaik_jsse.jar:/sapmnt/PMA/global/security/lib/tools/w3c_http.jar:/sapmnt/PMA/global/security/lib/tools/iaik_ssl.jar:/sapmnt/PMA/global/security/lib/engine/info/IAIKSecurityFS.list:/sapmnt/PMA/global/security/lib/engine/iaik_jce.jar com.sap.sdt.dmt.main.DMT -rootdir=/usr/sap/PMA/DVEBMGS10/j2ee/JSPM -descriptor=csrt29_PMA -logfile=/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/log/log_2009_11_18_10_28_50/DMT_01.LOG dbinfo /usr/sap/PMA/DVEBMGS10/j2ee/JSPM/config/DBINFO.XML#
#1.5^H#C000995FC0200000000000267BD47BD40004789C01422128#1258511338185#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#Java###Standard out: #2# #/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/log/log_2009_11_18_10_28_50/DMT_01_01.OUT#
#1.5^H#C000995FC0200000000000277BD47BD40004789C01424838#1258511338195#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#Java###Process ID has been started.#1#5#
#1.5^H#C000995FC0200000000000287BD47BD40004789C014253F0#1258511338198#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#Java###Waiting for process ID , name to finish.#2#5#java#
#1.5^H#C000995FC0200000000000297BD47BD40004789C017402B0#1258511341454#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#Java###Process ID , name has been finished, exit code .#3#5#java#0#
#1.5^H#C000995FC02000000000002A7BD47BD40004789C01741638#1258511341459#/System/Server/Upgrade/JSPM##com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:273)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:273)#Java###Command has been executed.#1#dbinfo#
#1.5^H#C000995FC02000000000002B7BD47BD40004789C017421F0#1258511341462#/System/Server/Upgrade/JSPM##com.sap.sdt.jspm.gui.InitialParametersDetector.detectDb(InitialParametersDetector.java:984)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectDb(InitialParametersDetector.java:984)#Java###Detection of the parameters of the database has finished. Database type is , database name is and database version is .#3#ORA#Oracle#10.2.0.2.0#
#1.5^H#C000995FC02000000000002C7BD47BD40004789C01744CE8#1258511341473#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.sysinfo.AbstractInfoController.updateProfileVariable(AbstractInfoController.java:284)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.sysinfo.AbstractInfoController.updateProfileVariable(AbstractInfoController.java:284)#Java###Parameter has been detected. Parameter value is .#2#/J2EE/StandardSystem/DefaultProfilePath#/usr/sap/PMA/SYS/profile/DEFAULT.PFL#
Sorry, I don't know how to format post
Edited by: Rongfeng Shi on Nov 18, 2009 4:20 AM

Hi Rongfeng,
There is not much information about the error in the log file you have pasted above.
Please repeat the issue and catch the log files once again.
Are you able to open SDM ?
Best Regards
Raghu

Error Message " An error occured while running the detection " Sharepoint 2010 & Project Server 2010

i am trying to Update the Service Pack of sharepoint & Project
Server (SP2) . i got an error while running the Package " An error occured while running the detection " ... I searched a bit and ran ROISCAN.vbs script which is by provided by MS to identify any issues ... i Found that few MSI files of sharepoint
are missing from WINDOWS Installer folder.... My Question is Should i repair the Sharepoint or any tool that i can use to get the MSI ?

There is a MS internal tool for fixing this issue but for this may be you need to contact MS, refer to below links:
Utility Name: OPUtil.vbs
http://social.technet.microsoft.com/Forums/en-US/a7919b10-e4fe-4911-9016-bb6b81cf4194/sharepoint-patch-update-issue
http://blogs.technet.com/b/paulpaa/archive/2010/03/26/sharepoint-2007-hotfix-failed-with-an-error-the-detection-failed-this-can-be-due-to-a-corrupted-installation.aspx
Please ensure that you mark a question as Answered once you receive a satisfactory response.

Fix for ORA-00060: Deadlock detected errors

Hello APEX community,
in the last days we are hitting more and more frequent the ORA-00060: Deadlock detected error in one of our applications. Logged an SR with Oracle Support but so far not too much help, except pointing to some older bugs:
Bug 6618662: APEX APPEARS TO BE CAUSING DEADLOCK - CASE COLLECTION or Bug 7587013: INSERTING AND DELETING WWV_FLOW_DATA CAUSES DEADLOCK, which do not look at all appealing as the first bug was logged in Nov 2007 and the resolution was delayed from version 3.1, to 4.0 and even to 4.1, while de second was logged in Nov 2008 and not much happened with it.
I am curious how many other users are hitting the same issue and which workarounds found for the problem. For example yesterday I could see 12 such errors in my log, today already 3.
Florin

Hi John,
here it is: http://www.moyersoen.be/auction/1442/ or http://www.moyersoen.be/pls/apex/f?p=2008:11:0::::P11_AUCTION_ID:1442. Normally the page response time is < 0.20, but from time to time it goes up to more than 20 seconds and at those times I can see also the ORA-00060: Deadlock detected errors.
Looks like the users are clicking twice refresh for that page. I am trying now to build a testcase that reproduce the issue easily.
Florin

Opening Excel Report results in 'Errors were detected in File .....'

Dear Professionals,
Ive an Excel report that upon openning produces the following error.
'Errors were detected in file 'T:\Customer .......'
Excel proceeds to strip out the ALL the Query Tables from the report discarding them due to integrity problems as described in the original error.
Query Table 'ExternalData_2' on '[xxxxxx Report - April FY14_v1.12.5.1.xls]SoldTo' was discarded due to integrity problems.
The query tables are connected to an 2010 MSAccess db on a networked drive. The file was created with Excel 2013 on a virgin machine, no add-ins are active. The file is saved in Excel .xls (2003) format.
While the error seems to only make cosmetic changes, the data seems intact. However it is an confidence issue for the end user to encounter such an error as these reports go to external customers.
I've circumvented the error by converting the Listobjects to Ranges prior to saving the file but I'd like to get to the root of the problem please.
Ive looked at disabling the office validation feature, however this is short term local solution that didnt seem to work and not practical going forward.
Also seemingly related, when compiling the report in Excel 2010 it randomly crashes at the point where the .Save method is executed (locally or to network). This crash disappeared when the report was compiled with Excel 2013. I've also not experienced
the crash since the Listobjects were converted to ranges when compiling in Excel 2010.
Any help / pointers would be most appreciated.
Kind regards,
David

Hi,
Thank you for using Excel IT Pro Discussions forum.
Are you using Office 2010 RTM version? If it is trial version or beta version, I suggest upgrading it to the RTM version.
First, please check if this KB article helps:
Error message when you try to open a workbook in Excel 2007: "Excel found unreadable content in Book_Name"
http://support.microsoft.com/kb/929766
Note: The steps are for Excel 2007. The steps in Excel 2010 are similar.
If the problem persists, let’s also check the following settings in Excel 2010.
========
1.
In Excel 2010, click File > Options > Trust Center > File block settings.
2.
Check the checkboxes before:
Excel 2007 and later Wordbooks and Templates
Excel 2007 and later Macro-Enabled Workbooks and Templates
Excel 2007 and later Add-in Files
Excel 2007 and later Binary Workbooks
Then, try to open the Excel 2007 file in Excel 2010 and check the results again.
Best Regards,
Sally Tang
TechNet Subscriber Support
in forum
If you have any feedback on our support, please contact
[email protected]

Preflight detected errors - overset text (1)

Hi
I have copied / pasted text from a Word document and tried 2 ways to place it in my InDesign CS6 document
(1) putting copied text into a prepared text box
(2) using the 'text box' that 'came with' the copied text (enlarged to fit area)
each time the dreaded 'red box with a + ' sign inside appears on the rt. side of the 'finalised' text
and 1 error shows at the bottom which is the Preflight detected error - overset text
I have loads of other text in my document but none copied/pasted
Writing the text manually into the document is not an option in this case
Do I have to format it somehow? I would really appreciate a really simple A-Z step answer for this old gal
cheers - any help will really stop my hair from greying any further Lou

Does the text contain special glyphs that require a font with Maori support? Id not then you can edit the styles to change the font (or, on the strong probability that the Word file doen't really use styles, you can use Find Font to replace it). if you do need Maori support, you should install a font that supports it, like Arial Maori, on the computer. ID uses any fonts installed normally for the OS (presuming they are not really badly made) or that are located in the private Adobe or InDesign fonts folders.

T450s Thinkpad - ERROR 2101: Detection error on SSD1 (M.2)

Similar Messages

Maybe you are looking for