Unable to mount MDM repository

hello,
I'm working with MDM console, I'm able to mount the MDM Server successfuly but when I mount a existing repository, the repository appears with a grey padlock and no tables and subtables appear.
Any idea?
Thanks in advance,
Marta.

Hi,
This happenns when there is version mismatch between MDM Repository and the Client used to mount the repository.
Try to Update the Repository by right clicking on the repository and select Update Repository option.
Also check the version of the Console and the Repository
Regards,
Jitesh Talreja

Similar Messages

Unable to mount MDM Console

Hi,
I am new to SAP MDM. I was just trying to mont the console(MDM_TestConsole) and was trying to start it by right clicking and start MDM Server. The system prompts me with this message below.
*Error Starting: MDMTestConsole(MDM Server): The machine 'MDM_TestConsole' is not Windows-based.The MDM server cannot start from this application;please use CLIX on the machine instead*_
Thank You,
KishoreJ.

Hi Krishore,
you get this error due to various reasons, one of which i faced. The problem i had was, my console and server not being in the same network, they were separated by an proxey. You make sure that they are in the same network.
Secondly please check whether you installed you MDM Server or not. Without which also u will be getting this error.
In case this are not the issues then please let us know.
Life Looking Long
CHERRY

Problem: Unable to retrieve workflow data from MDM repository

This is a new MDM installations scenario for version 5.5 SP05 (5.5.40.83).
After installing MS Visio, finding problems connecting it with the MDM Data Manager. After doing MDM workflow installations, able to initiate the MS Visio Workflow from MDM Data Manager and can see the Pane-MS Visio Workflow Stencil but not the able to see the Pane-MS Visio Workflow Stencil Details that appears below the Pane-MS Visio Workflow Stencil. Secondly geting a pop-up with the error message as - 'Unable to retrieve workflow data from MDM repository.'
I have added a parameter Mail Server=MailServerIPAddess (the existing IP addr), but it hasn't helped.
Can any one please help me in this !

Hi
As Felix mentioned, it might be a version compatibility problem.
You have also mentioned that mail server is not working for that do this
Mailserver = SMTP server.company.com ( ex. Mail.company(xxxxx).com)
MDM workflow notify task is working after rebooting the Machine. So the rule is after making changes to MDS.ini file reboot the machine ,to observe the consequence of configurable changes.
If u need anything this let me know.
Regards
Hari

How to Mount a repository in MDM

Hi,
I need to check the repository is mounted or not. If it is not mounted I need to mount the repository in the program.
Can anyone tell me any methods available to do this,.
Thanks & regards
Vijay

I believe you have posted this question in the wrong forum. I think you probably want the MDM forum. Even if you are working with the MDM ABAP APIs, there is nothing Web Dynpro specific there. I would suggest either the MDM or ABAP General Forums.

Unable to connect to MDM repository

Hi ,
I was able to create a new MDM repository by using my DB uid/pwd.The newly created repository appears under the MDM server in a locked state.When I try to connect using my admin uid/pwd,it says "Invlaid login credentials".I am able to login to other repository using the same uid/pwd on the same server.
Regards,
premjit

Hi,
There may be following issues :
1. in corrrect Login/PW: in case you don;t remember the login PW you need to retrieve the PW from Database. Or as suggested try with Admin/blank for MDM 5.5 and Admin/SAPMDM for MDM 7.1.
2. try to unmount and mount the server, then try loggin to the repos.
let us know if it worked.
Manish

MDM Repository not Connecting after Server shifting

Hi,
Here We have SAP MDM 7.1 06 on Windows Server 2008 R2 with Oracle.
Recently we have shifted our MDM Server from 1 Data Center to Another Data Center, After this change MDM Instances started successfully.
1st Problem:
Now the problem is, i am not able to connect repository (Error is: Repository connect failed, Invalid Object State). After i mount the MDM Server in console, repository not connecting.
2nd Problem:
when i right click on MDM Server in Console, even i am not able to connect Databse in DBMS Setting (Error is: Unable to connect with Database server).
Need Help to fix this issue at the earliest.
Did some searches on net and sdn forums but couldn't get right solutions.
Thanks in Advance
Thanks
Ahmed

Dear All,
Thanks For your support.
The issue has been solved.
Problem was: MDM Server and Repository was not connecting to DB, due to sever shifting to new location with different public IP.
Solution is: when i check the tnsnames.ora file in the below location Old public IP was given so, now i just changed the newly assigned public IP, (Under file path: <Drive>:\oracle\SID\product\11.2.0\dbhome_1\NETWORK\ADMIN).
After the change and update of new public IP in tnsnames.ora, we have restart the MDM instances and DB from OS Level.
After this activity, DB connection issue was solved, then now i am able to connect to existing MDM repository.
Thanks
Ahmed

Problem in mounting the repository

Hai expertise,
      When i try to mount repository or change database settings it is showing some error (The same thing is working previously) :
     1) I have not saved the list of mounted servers SAP MDM Servers.mcs while closing the MDM console (From that time the same problem is occuring)
     2) when i try to change the configuration -> database settings it is showing the following error even though i am giving proper database username and password
        <b>Error is like this " DBMS has not been initilialized for use with MDM. Leaev the feild blank to use the default DBMS paths.or use good paths to override the defaults.if the DBMS host has multiple path instances use unique paths to this instance.these paths may change later through DBMS setting options
Data File path and Transaction Log File Path ".
I created 2 folders in my Microsoft SQL Server folder and entered them in these two feilds. Then error pop up windows appear as
Unable to modify database
MDM repository list schema has not been created
cannot get DBMS settings from server</b>
3) Same error comes when i try to mount a repository to my MDM server
How to resolve the issue????

Hello Govada,
                     Lemme know are u specifying the database name to which u need to connect and then specifying the Database password.
Coz I was also having the same problem but after specifying the database name and password it got resolved.
Regards Tejas.................

"the MDM repository is invalid"

Hej All
Vi have updatered our MDM server with standard update from Microsoft. Later on we can't start MDM services, therefore after "a long fight" it was decided to restore repositories in that way:
we restored a backup of the MDM database on the newly installed server. Afterwards we copied the MDM directories from the old server. we changed the servername in all configuration files and started the MDM systems.
All seems to be fine but each time we log on to repository we got an error:
"the MDM repository is invalid"
can you help?
Thank you in advance.
BR
Rafal

Hi Rafal
just few questions to you
1) Have you checked the connection between your MS Sql and SAP MDM Server ?
2) If you have then are you able to create the repository manuallly?
if you have made the connection and still you are not able to create the repository manually then please reset the connection again, also plz check if the name of this particular repository you are trying the log in is ceated in your MDIS, MDS and MDSS.
if every thing seems to be right then please again import the schema of your old repository and then log with admin user and check if you are able to connect to the repository.
if still you are unable to log in please let us know.
Thanks and Regards
Praful

Unable to restart MDM Server

Hi All,
I am using MDM SP4. We have a repository Z_ATLAS_MATERIAL_P_TST in SP4. Yesterday I tried to rename this repository but I was not aware that in SP4 we can't rename repository...it's a bug. So, when I renamed this repository to Z_ATLAS_MATERIAL_P_TST1 it gave me error "MDM Repository is invalid" and after 2-3 mins the console window get closed.
Then I tried several times to mount that MDM server in new console session but everytime console gets terminated.
But in the background MDM server and SQL server were running.
Today, when I restarted the MDM server,it ran for 1-2 mins then it got terminated abrubtly.
Can any one of please suggest what could be the reason and how to resolve it.
Thanks,
Varun

Hi Varun,
We also faced with such problem. First try to re install MDM Console client, even though if it doesnt start then try to restart your services through services.msc in the RUN. Restart your MDM server, Listeners and Database Services.
Hope this solves your problem.
Reward points if helpful.
Prasad......

What is the clix command to mount a repository

I have a repository that was marked as invalid after an unarchive was done. The repository has been successfully unmounted via CLIX commands. The repository does not appear as an option in the Console for remount. I would remount it via CLIX but cannot get the syntax correct. Cllix does not seem to recognize the port, it gives me an error message saying to use ports > 2000.
Does anyone know the exact syntax for mount a repository via Clix? Very detailed answer, please.

Hi Rose,
Check the syntax for mounting the repository
CLIX repMount MDMHostSpec RepositorySpec port
where
- MDMHostSpec is the MDM Server name or the IP Address
- RepositorySpec is the repository name
- port is the port number on which the repository should be mounted (The port must be in the range 2000-9999)
Regards,
Jitesh Talreja

Error mounting MDM Server

Hi,
Error mounting MDM Server
We are unable to mount the MDM server, the error message saying
(The specified SAP instance does not exist on server mdm-sr)
mdm-sr : hostname of mdm server
FYI: The mdm server and mdm console running on the same host .
Thanks
Faris

Hi Deep,
restarted both DB and then MDM server, but still not working, giving same error message
(Error mounting MDM Server, The specified SAP instance does not exist on server mdm-srv)
FYI: The mdm server and mdm console running on the same host .
But the DB instance is runing on the diffrent server
Tx,
FSS

Unable to mount SD cards - SCSI disks

I have a generic, cheap, all in one usb card reader and am unable to mount sd cards on my system. I tried a few days back with a friends similar sort of card reader with the same outcome. I've got 3 sd cards to hand, one brand new, all of which seem to work fine on my Canon DSLR camera.
Some info:
dmesg | tail
[ 3.070959] scsi 6:0:0:0: Direct-Access Generic Mass-Storage 1.11 PQ: 0 ANSI: 2
[ 3.335877] sd 6:0:0:0: [sdd] Attached SCSI removable disk
[ 4.908578] r8169 0000:02:00.0 enp2s0: link up
[ 4.908586] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
[ 652.025211] usb 3-7: USB disconnect, device number 2
[ 657.544035] usb 3-8: new high-speed USB device number 5 using xhci_hcd
[ 657.718030] usb-storage 3-8:1.0: USB Mass Storage device detected
[ 657.718092] scsi host7: usb-storage 3-8:1.0
[ 658.721486] scsi 7:0:0:0: Direct-Access Generic Mass-Storage 1.11 PQ: 0 ANSI: 2
[ 658.986353] sd 7:0:0:0: [sdd] Attached SCSI removable disk
sudo fdisk -l /dev/sdd
fdisk: cannot open /dev/sdd: No medium found
After a few reboots I installed some tools in the official repos with scsi in the description in the hope something might happen:
pacman -Qs scsi
local/lsscsi 0.27-1
A tool that lists devices connected via SCSI and its transports
local/sdparm 1.08-1
An utility similar to hdparm but for SCSI devices
local/sg3_utils 1.39-1
Generic SCSI utilities
local/smartmontools 6.3-1
Control and monitor S.M.A.R.T. enabled ATA and SCSI Hard Drives
local/vhba-module 20140629-9
Kernel module that emulates SCSI devices
sudo hdparm /dev/sdd
/dev/sdd:
SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
multcount = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 1024/0/62, sectors = 0, start = 0
sudo hdparm -z /dev/sdd
/dev/sdd:
re-reading partition table
sudo sdparm /dev/sdd
/dev/sdd: Generic Mass-Storage 1.11
lsusb -v | grep sdd
Couldn't open device, some information will be missing
lsusb -v
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x8087 Intel Corp.
idProduct 0x8000
bcdDevice 0.04
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 12
Hub Descriptor:
bLength 11
bDescriptorType 41
nNbrPorts 8
wHubCharacteristic 0x0009
Per-port power switching
Per-port overcurrent protection
TT think time 8 FS bits
bPwrOn2PwrGood 0 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00 0x00
PortPwrCtrlMask 0xff 0xff
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0100 power
Port 3: 0000.0100 power
Port 4: 0000.0100 power
Port 5: 0000.0100 power
Port 6: 0000.0100 power
Port 7: 0000.0100 power
Port 8: 0000.0100 power
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 3.17
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x8087 Intel Corp.
idProduct 0x8008
bcdDevice 0.04
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 6
wHubCharacteristic 0x0009
Per-port power switching
Per-port overcurrent protection
TT think time 8 FS bits
bPwrOn2PwrGood 0 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0100 power
Port 3: 0000.0100 power
Port 4: 0000.0100 power
Port 5: 0000.0100 power
Port 6: 0000.0100 power
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 3.17
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 3
bMaxPacketSize0 9
idVendor 0x1d6b Linux Foundation
idProduct 0x0003 3.0 root hub
bcdDevice 3.17
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 31
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
bMaxBurst 0
Bus 003 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x093a Pixart Imaging, Inc.
idProduct 0x2510 Optical Mouse
bcdDevice 1.00
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 52
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 10
Bus 003 Device 005: ID 1908:0226 GEMBIRD
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1908 GEMBIRD
idProduct 0x0226
bcdDevice 1.11
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 150mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Bus 003 Device 004: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x045e Microsoft Corp.
idProduct 0x0750 Wired Keyboard 600
bcdDevice 1.10
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 59
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 65
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 106
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 3.17
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
uname -r
3.17.1-1-ARCH
Any ideas?
Last edited by Proinsias (2014-10-25 23:15:08)

Try udev. Is your reader OK? Is the card recongized - does it show in dmesg?
http://wiki.archlinux.org/index.php/USB_Storage_Devices
You should familiarize yourself with the wiki
http://wiki.archlinux.org/index.php/Asus_Eee_PC_701
http://wiki.archlinux.org/index.php/Asu … /xorg.conf
Last edited by karol (2010-07-09 14:02:36)

Error code: MapiExceptionJetDatabaseCorruption: Unable to mount database. (hr=0x80004005, ec=-338)

We are on Exchange 2007
We have one database that will not mount. Whenever we try to mount we get the below error
Exchange is unable to mount the database that you specified. Specified database: EXG01\SG3-DB\SG3-DB; Error code: MapiExceptionJetDatabaseCorruption: Unable to mount database. (hr=0x80004005, ec=-338)
I ran the eseutil /mh against the DB & found the database to be in clean shutdown state. I moved all the log files and chk files to another location and tried mounting the DB but the very same error.
Initiating FILE DUMP mode...
         Database: SG3-DB.edb
        File Type: Database
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,12
Engine ulVersion: 0x620,12
Created ulVersion: 0x620,12
     DB Signature: Create time:06/07/2011 00:22:54 Rand:482525 Computer:
         cbDbPage: 8192
           dbtime: 3942751903 (0xeb019e9f)
            State: Clean Shutdown
     Log Required: 0-0 (0x0-0x0)
    Log Committed: 0-0 (0x0-0x0)
   Streaming File: No
         Shadowed: Yes
       Last Objid: 877765
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
Please help us on how to clear this error and mount the database.

We are on Exchange 2007
We have one database that will not mount. Whenever we try to mount we get the below error
Exchange is unable to mount the database that you specified. Specified database: EXG01\SG3-DB\SG3-DB; Error code: MapiExceptionJetDatabaseCorruption: Unable to mount database. (hr=0x80004005, ec=-338)
I ran the eseutil /mh against the DB & found the database to be in clean shutdown state. I moved all the log files and chk files to another location and tried mounting the DB but the very same error.
Initiating FILE DUMP mode...
         Database: SG3-DB.edb
        File Type: Database
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,12
Engine ulVersion: 0x620,12
Created ulVersion: 0x620,12
     DB Signature: Create time:06/07/2011 00:22:54 Rand:482525 Computer:
         cbDbPage: 8192
           dbtime: 3942751903 (0xeb019e9f)
            State: Clean Shutdown
     Log Required: 0-0 (0x0-0x0)
    Log Committed: 0-0 (0x0-0x0)
   Streaming File: No
         Shadowed: Yes
       Last Objid: 877765
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
Please help us on how to clear this error and mount the database.

Kernel panic since upgrade to core. Unable to mount root fs on

kernel panic : not syncing; VFS; Unable to mount root fs on unknown-block (0,0)
I get that error since I upgraded archlinux to the latest version. The last time I upgraded before that was while the repos was still named current. Since I upgraded to core that happened.
What should I do? How could I fix this? I have this problem on the fallback kernel too.
Last edited by sokuban (2007-09-23 01:49:57)

Hello All,
I have two hard drives installed in my pc, one is ATA and the other one is a SATA.
ATA is /dev/sda 200GB
SATA os /dev/sdb 40GB
I have installed arch linux onto sdb. grub also is installed to sdb.
Whenever I do a pacman -Syu and reboot I get the kernel panic not synching attempted to kill init error message at boot
I then boot the pc using the fallback image and copied the fallback config to /etc/mkinicpio.conf and ran mkinitcpio -p kernel26 and rebooted. everything works fine. but just running the command pacman -Syu and rebooting will end up with the same problem. though pacman -Syu does not install any updates. what is it that I'm doing wrong?
Thanks
Last edited by xboxer21 (2007-09-28 18:11:36)

Error on install, CDROM not booting Kernel, unable to mount CDRM, what now?

Please help. I am new to this, so as many options as possible would be a help.
So far here are the steps I've taken to install Solaris 8 (Intel):
1. Checked HCL - I have two CD ROM's I've tried, both are on the list. (Mitsumi FX140S and Sony DVD DDU220E)
2. Set BIOS to boot CDROM - Boot failure..., I have set and changed jumpers back and forth from Master to Slave. I have moved CDROM drive from primary Slave to secondary Master and secondary Slave.
3. I have downloaded and used the Device Config Assistant boot floppy. It boots and checks devices. It also recognizes the CDROMs I have (both CDROMs are not have installed at the same time).
4. I have selected whichever CDROM I have installed as the default boot device (*) using F4_Boot Tasks. I have also adjusted timeouts from 0,1,2 and 3 seconds and have had autoboot ON/OFF.
5. I have entered F2 to continue and I receive this error:
Unable to mount a Solaris root file system from the device:
CD : (*) Target 1, MITSUMI CD-ROM FX140S !B e12 on Bus Mastering IDE controller on Board PCI bus 0, at Dev 4, Func 1
Error message from mount:
/pci@0,0/pci-ide@4,1/ide@0/sd@1,0:a: can't open - no hsfs VTOC
Press Enter to Continue.
I have inserted all 3 CD I have created with the same results from each. The CDs have the .iso extention and were created using Easy CD Creator.
Please, Please, Please, ANY suggestions!!
LL

First off you don't need to set your CDROM as the default boot device to install Solaris, that's why we have the Solaris DCA boot diskette. And also only the Solaris Installation CD and Software 1 of 2 are bootable CDs, the software 2 of 2 is NOT.
Once you finish downloading the images from Sun's website you need to not only add the .iso extension to the ending of each image file but use the option "Burn using CD image" under the File menu in Easy CD creator.
If you try and view the burned CD under Windows you will only see a small number of the actual files that are on the CD. And NO you will not see the .vtoc file and will not be able make one yourself.
My suggestion would be to try and burn a new CD with the above instructions and boot with the Solaris DCA and continue pressing F2 until you get to the point where it asks you select where you want to boot the kernel from. At that point put with ther Installation CD or Software 1 of 2 in your drive and attempt to boot from it.
Keep us updated on your progress.
Allen
Sun Develeper Technical Support

Unable to mount MDM repository

Similar Messages

Maybe you are looking for