AIM-CUE - Filesystem type unknown ?

Hi there,
I am studying IIUC and I am up to the CUE module. Im pretty sure I have done something stupid. I removed the 1GB CF from the AIM-CUE module, put it in my 2801 CF slot and did a format flash: (I dont know why, I just thought it would let me start fresh ) . Now when the AIM-CUE goes through the boot process I get the following output.
Initializing memory. Please wait....
256 MB SDRAM detected
BIOS Version: Cisco SE-AIM 01.02
BIOS Build date: 08/14/03
System Now Booting ...[BOOT-ASM]
Filesystem type unknown, partition type 0x1
kf: a1 : (hd0,0)/bzImage root=/dev/hda1 ro plat=aim
kf: a2 : (hd0,0)/bzImage root=/dev/hda1 ro plat=aim
in grub_open: (hd0,0)/bzImage root=/dev/hda1 ro plat=aim
kernel_func: kt: 0
in boot func: kt: 0ÿ
I can get into the bootloader and use the boot helper to re-install the CUE files, but I guess if they are on the wrong filesystem type they are useless.
I have searched around and it looks like I need to have the "Filesystem type is reiserfs, partition type 0x83".
Now the only way I can see to re-format the flash to the reiserfs file system is the put the 1GB CF into a card reader and format it with my PC. Im going to give it a try now, but I also read somewhere there needs to be 2 partitions, however Im unsure what size each partition should be.
This is a second hand AIM-CUE so I dont have any support for it. Have I rendered my AIM-CUE useless, or is there a way I can dig myself out of this hole I have created ??
Thanks in advance.
JP

Thanks for the reply paolo, however the boot loader / boot helper is the problem. Ive managed to get the right filsesystem type however now its stuck in this constant loop
Initializing memory. Please wait.
256 MB SDRAM detected
BIOS Version: Cisco SE-AIM 01.02
BIOS Build date: 08/14/03
System Now Booting ...[BOOT-ASM]
Please enter '***' to change boot configuration:
Filesystem type is reiserfs,partition type 0x83
kf: a1 : (hd0,0)/bzImage root=/dev/hda1 ro plat=aim
kf: a2 : (hd0,0)/bzImage root=/dev/hda1 ro plat=aim
in grub_open: (hd0,0)/bzImage root=/dev/hda1 ro plat=aim
in grub_open1: /bzImage root=/dev/hda1 ro plat=aim
in grub_open2: /bzImage root=/dev/hda1 ro plat=aim
in grub_open3: /bzImage root=/dev/hda1 ro plat=aim 1
in grub_open4: /bzImage root=/dev/hda1 ro plat=aim
kernel_func: kt: 0
in boot func: kt: 0ÿ <--when it gets to here it goes back to the "Initializing memory. Please wait." and just keeps looping.
Any ideas why boot helper keeps looping like this ??
EDIT: Now I am getting "Not a cisco supported CF. Please use cisco supported CF and reinstall the software. System Halted"
Im guessing the CF may have been on its way out and now it has gone faulty ?

Similar Messages

First boot fails - Filesystem type unknown, partition type 0x7

Just done a straight forward install of Arch onto it's own disk drive, however there are two other drives present in the system.
Grub menu comes up ok but then Arch errors with:
root (hd2,0)
Filesystem type unknown, partition type 0x7
Error 17: Cannot mount selected partition
Any suggestions?
Thanks,

hokasch wrote:
What you still did not really tell us - how are you booting up? I.e. where is your first grub stage installed? How did you manage things with the debian install? Your problem is the root(x,x) line, not the kernel line. This line specifies the boot partition (grub's root/ where to find the kernel).
Coming from the windows world where for years we have just relied on changing the boot order of drives in the BIOS to choose which MBR to boot from I simply assumed it was just as easy in the Linux world, this is obviously not the case.
If you want to continue that way, just install grub to the MBR of each disk with a linux install and configure grub to use that drive as the first drive (e.g. set the root line to hd(0,0) if /boot is the first partition). IIRC, changing the boot order in the Bios will pull the selected drive to the beginning. That would fit your inital error (but you did not say how you booted into grub then...). You can double-check that behaviour by using the find commands in the grub shell (see my earlier post).
Going with grub2/grub's root by uuid only really makes sense if you put grub2 on the MBR of a drive which is always installed and selected as primary in Bios (obviously, all other grub2 files must be on that drive too).
Just done another completely clean install and noticed that even though I select 'Partition access method - uuid' it doesn't seem to actually work that way, at least checking menu.lst showed no signs of any uuids. What is the point of having an install option if it is then ignored.
This refers to your fstab, not the bootloader config.
Sorry hokasch, it got a bit difficult to answer your earlier post as by the time I read it Debian had been trashed and I think I had redone the Arch install a few times by then as well.
If I have understand you correctly what you are saying is that if I were to install arch on a drive which at install time is the only drive in the machine then root(x,x) would refer to hd0 in my case root (hd0,1) as I have an NTFS partition at the beginning of the drive. Alternatively I could just edit grub's menu.lst afterwards. That way as long as the drive is first in the BIOS boot order it will boot ok. My mistake seems to have been trying to install the first grub stage to somewhere other than the MBR, I may have missunderstood the capabilities of partition identification by uuid.
Ok lets go back to a single drive environment
hd0,0 = NTFS boot partition
hd0,1 = Arch /Boot - this contains grub & vmlinuz-linux
hd0,2 = Arch swap
hd0,3 = Arch /
If I want to boot Windows I set hd0,0 as active/bootable, if I want to boot arch I set hd0,1 as active/bootable. Actually not sure how to change the active partition to a linux one but come back to that later. For the moment hd0,1 is the bootable partition. This is the only drive in the system. I have a by-uuid entry in menu.lst which allows me to boot if the other entries fail. menu.lst looks like this:
# (0) Arch Linux
title Arch Linux
root (hd0,1)
kernel /vmlinuz-linux root=/dev/sda4 ro
initrd /initramfs-linux.img
Now I see part of the confusion, as you advised, the root (hdx,x) line actually refers to the 'grub root' / 'linux boot' not the 'linux root'. And the other confusion is that the kernel line root= does not refer to the location of /vmlinuz-linux but to the actual linux root. Now I think I understand that bit.
Now to add another disk to the system. Change drive order in BIOS so that arch disk is top of the boot order.
Fails to boot: Unable to find root device /dev/sda4!
Boot to knoppix to see the disk & partition layout:
hd0,0 = NTFS
hd0,1 = NTFS
hd0,2 = NTFS
hd0,3 = NTFS
hd0,4 = NTFS
hd0,4 = NTFS
hd0,4 = NTFS
hd1,0 = NTFS boot partition
hd1,1 = Arch /Boot - this contains grub & vmlinuz-linux
hd1,2 = Arch swap
hd1,3 = Arch /
So clearly /dev/sda4 is now an NTFS partition.
If appears that grub & linux do not see disk drives in the same order as the BIOS boot order causing /dev/sda4 to point towards the wrong partition.
Off at a bit of a tangent here but while I think of it is there a way of regenerating the menu.lst to search for instances of windows on NTFS partitions now that I have access to ntfs-3g.
Thanks,
Last edited by NickC_UK (2012-02-21 14:25:04)

Can't boot after system update: unknown filesystem type

After running a system update, including updating the kernel, I can't boot to the new kernel.
On booting, grub loads the kernel image, runs/loads udev, but then fails to mount the root partition with error:
mount: unknown filesystem type 'ext4'
I have tried reinstalling the 'linux' package via packman several times, also trying the --recursive argument to make sure all my dependencies were there, and after days of googling and tweaking my system, I'm at a loss.
Thank goodness I happened to keep a spare kernel laying around in /boot.
Thanks in advance.
Last edited by jackrabbit (2012-03-22 23:25:28)

The OP can read their partition initially though, it's only after udev that they can't.
Also, try adding "rootfstype=ext4" to your grub kernel line. Is your /boot on a separate partition or part of your / partition?

[SOLVED] mount: unknown filesystem type 'ext2'

I probably have the most complicated first-time arch setup that you'll ever hear a n00b post. XD
I just finished setting up an encrypted arch box with a usb boot drive (it contains the key-file), but when I go to boot, the system reports the following:
mount: unknown filesystem type 'ext2'
Of all the things to break! Ext2???!
This is for the default boot mode, when boot into the fallback initramfs mode, the arch box boots up fine (although it takes 2 whole minutes). I think that the issue is that I'm missing a module in my mkinitcpio.conf file.
/etc/fstab file:
UUID=1245ASDF / btrfs discard,autodefrag,compress=lzo,rw,relatime,ssd,space_cache 0 0
UUID=2245ASDF /boot ext2 rw,noatime 0 2
UUID=3245ASDF none swap defaults 0 0
/etc/mkinitcpio.conf file:
HOOKS="base btrfs udev autodetect modconf block encrypt lvm2 filesystems keyboard fsck"
/etc/default/grub file:
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda:enc cryptkey=/dev/sdb2:ext2:/keyfile crypto=sha512:twofish-xts-plain64:512:0:"
Last edited by a-jamesregan (2015-04-13 19:15:48)

Wow, there was literally a note about the exact issue I was having on the wiki...
https://wiki.archlinux.org/index.php/Mkinitcpio#MODULES
Note: If using reiser4, it must be added to the modules list. Additionally, if you will be needing any file system during the boot process that is not live when you run mkinitcpio — for example, if your LUKS encryption key file is on an ext2 file system but no ext2 file systems are mounted when you run mkinitcpio — that file system module must also be added to the MODULES list. See Dm-crypt/System configuration#cryptkey for more details.
PS: How do I mark an issue as solved?
Last edited by a-jamesregan (2015-04-13 10:28:20)

Mounting problem, mount: unknown filesystem type 'vfat'

Can't mount vfat partition.
Mounting problem, mount: unknown filesystem type 'vfat'

takavar wrote:sorry for the necromancy, but this is the top result on Google search with no answer.
I am going to close this thread because (a) the thread is more than two years old, abd (b) may or may not be related to your problem.
Please open a new thread detailing your problem. Define what is "Solved" by rebooting. Does the drive mount during a reboot? Tell us how you are trying to mount the drive, and provide us your /etc/fstab. You may want to share the the output of sudo fdisk -l /dev/sda
If you still think it relevant. provide a link back to this thread.
Thanks

Unknown filesystem type crypto_LUKS

Hi, I have spare space on my HD so I decided to experiment with encryption following this wiki:
https://wiki.archlinux.org/index.php/dm-crypt_with_LUKS
In summary:
created boot (sda6) and root (sda7) partitions
formatted boot as ext2 and root with passphrase and then with ext4
installed the base system
generated a new initramfs as explained in the wiki:
MODULES="dm_mod ext4"
HOOKS="base udev autodetect modconf block keymap encrypt filesystems keyboard fsck"
added cryptdevice=<device>:<dmname> to kernel boot options:
linux /vmlinuz-linux cryptdevice=/dev/sda7:cryptroot root=UUID=d3505fe1-4a29-4841-8e80-e953442d8d30 ro quiet
restarted pc
On boot it asks for passphrase, but after that it stops with an error regarding crypto_LUKS; here the complete message:
A password is required to access the cryptroot volume:
Enter passphrase for /dev/sda7
fsck: fsck.crypto_LUKS: not founf
fsck: error 2 while executing fsck.crypto_LUKS for /dev/sda7
ERROR: fsck failed on '/dev/sda7'
********************* WARNING ***********************
* The root device is not configured to be mounted *
* read-write! It may be fsck'd again later. *
mount: unknown filesystem type 'crypto_LUKS'
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs /]#
Here it is my fstab: http://pastebin.archlinux.fr/474004
and lsblk output: http://pastebin.archlinux.fr/474005
Any idea about the problem?
Thanks for your time.

There are two discrepencies between your kernel parameters and fstab:
1) The kernel parameter UUID for real root differs from the UUID given for /dev/mapper/cryptroot in your fstab; if cryptroot is your real root partition, the UUIDs should be the same.
2) Your fstab instructs the system to mount the root partition as read-write, while the kernel parameters specify read-only. (the kernel parameter should be read-write, which is what the warning in the output above is about).
Change those and see if it helps.

BTRFS not mounting (unknown filesystem type)

Hi everyone,
From a USB drive I have been trying to install Arch in the fashion given in https://wiki.archlinux.org/index.php/In … Btrfs_root, I have upgraded the system to the newest kernel (3.3.6) and using the instructions created 2 partitions on /dev/sda. One being for Grub to boot the system, and the other being the btrfs.
I have been unable to mount the btrfs device (/dev/sda2), I keep getting the error
[root@archiso ~]# mount -o defaults,noatime /dev/sda2 /mnt/btrfs-root
mount: unknown filesystem type 'btrfs'
mount, i.e. util-linux is the newest version 2.21.1
any help is really appreciated

Well, I think the problem is caused by the loaded kernel being unable to find it's modules (the btrfs module included) because they got uninstalled when you upgraded the kernel package. You could try manually loading the module with modprobe (using -f if you get errors regarding versions), but I can't recommend that course of action, nor can I guarantee that it will fix your mounting problem.

Mount: unknown filesystem type 'LVM2_member'

I recently did a pacman -Syu with some consequences. I still had grub1 running and it was automatically upgraded to grub2, which is fine, but apparently grub-install was run on the mbr (I really think that was very inappropriate as that did break my system). Anyhow, on to chroot, I update /etc/default/grub as I have an LVM on top of an encrypted root and add this:
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda5:VGarch"
and this to mkinitcpio.conf:
HOOKS="base udev autodetect fsck modconf block encrypt lvm2 filesystems"
then update both:
mkinitcpio -p linux
grub-mkconfig -o /boot/grub/grub.conf
and then update again for good measure while we're still in the chroot. However, upon reboot I get the ominous error message:
mount: unknown filesystem type ‘LVM2_member’
EDIT: i moved fsck behind filesystems in hooks with no effect
Last edited by thoth (2013-07-03 01:31:06)

Post the entire kernel command line you are using (/proc/cmdline).
Note that the upgrade to grub2 will not have automatically installed grub to disk. So if you have not installed grub to disk, you need to do that in order to configure it correctly.
i.e. grub-install was *not* run on the mbr as part of the package upgrade.
See /var/lib/pacman/local/grub-2.00.5043-2/install.
But your config file for the old grub will have been moved to a .pacsave when that package was removed by pacman.
Last edited by cfr (2013-07-07 23:28:53)

AIM-CUE never get up

hi all
i have a new AIM-CUE module that installed in C2811 router.
the problem that the int service-Engine 0/0   protocol never get up as seen below
CME_CUE_LAB#sh int service-Engine 0/0
Service-Engine0/0 is up, line protocol is down
Hardware is I82559FE, address is 58bc.2739.d20a (bia 58bc.2739.d20a)
Interface is unnumbered. Using address of FastEthernet0/0 (10.0.0.1)
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
     reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:09, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     67 packets output, 5876 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 unknown protocol drops
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out
the configuration for the interface :
interface Service-Engine0/0
ip unnumbered FastEthernet0/0
service-module ip address 10.0.0.10 255.255.255.0
service-module ip default-gateway 10.0.0.1
end
i really need your help

Hi
Thanks for your reply .
The problem that because the line protocol is down in the interface ,I cannot open a session on it and I cannot see any logs on the AIM-CUE.
Is there any action that I can make it
Also I noticed that upon the AIM daughter board there are 3 pins without any jumper, is it correct ?
Best regards,
Mohamed Ibrahim Omran
Network Section Head
Dialup and VOIP Unit
A11-B90, Smart Village,
KM 28 Cairo-Alex Desert Road,
6 October 12577, Egypt
T: +20 (2) 33 32 0700 | Ext: 1122
F: +20 (2) 33 32 0800 | M: 010-3532153
E: [email protected]
www.tedata.net

IDVD: Files exported from iMovie 11, one works, one "Unsupported File Type : Unknown format"

I used footage from the same camera (taken on the same weekend using the same settings) in several different iMovie "projects". All were shared from iMovie 11 as "File" using the quality setting "SD 480p".
In Quicktime Player, all ".mp4" files will play and they show the following info in its inspector:
Format: H.264, 854 x 480
AAC, 48000 Hz, Stereo (L R)
FPS: 29.97
One exported file will drag, drop, and burn in iDVD just fine. The other two files show the error "Unsupported File Type : Unknown format" as soon as I try and drag them into iDVD.
The only difference I can find is that the one file that works is about 803MB, while the files that don't work are 1.87GB and 3.98GB.
All files and the iDVD project are in the same folder on my startup volume. I've tried deleting com.apple.idvd but that didn't help. I've tried rebooting and starting the iDVD project from scratch but I get the same results.
Mac OS 10.9.1
iMovie 10.0.1
iDVD 7.1.2
Any ideas?

Hello Bengt and thank you again for the replies.
As I mentioned in my previous posts, I'm using iMovie 10.0.1 which has very limited quality adjustments. In every case I chose the smallest size, which iMovie 10.0.1 calls "SD 480p (854 x 480)". I used this same setting on all exports.
I still have iMovie HD (6.0.4) and iMovie '11 (9.0.9) on my iMac so I tried both of them. In both cases, they could import only the file that works in iDVD. Both older versions of iMovie choked on the longer movies shared from iMovie 10.0.1.
I have many many hours into the editing of these clips and I do not want to have to go back and redo everything in an older version of iMovie. Might I be better off going with a different DVD creation software? Or am I out of luck? Because I can't really change iMovie 10.0.1's export settings, I'm afraid there's nothing I can do to get it to export it as something that iDVD can use (really, I can't even tell why it's different and why iDVD doesn't like it).
The software "WonderShare DVD Creator" has no issue with any of the files I've exported from iMovie 10.0.1.

AIM/CUE not Picking-up in-bound external calls

I have a 2811 router with an AIM/CUE (12-VM) card. All of the telephony-service stuff works fine:
-All calls in house work fine
-All outbound calls work fine, to PSTN
-All inbound calls work fine, from PSTN
-Each phone can access it's VM internally
-the CME gui and the Unity-Express gui's are accessible on the LAN.
But, when I call from outside into the PRI with a DID number, I get four rings, then a pause, and then it never goes to voicemail. Sometimes; depending if I call with my celr or a land line, I get the message "Sorry your call cannot be completed as dialed, 000-000." Any clue why the vm does work for internal or external calls.
Here's a sample of the config.
interface FastEthernet0/0
no ip address
no ip mroute-cache
duplex full
speed 100
interface FastEthernet0/0.100
description SUB-IF for VOICE VLAN
encapsulation dot1Q 100
ip address 10.1.100.1 255.255.255.0
interface FastEthernet0/0.101
description GW FOR VOICEMAIL MODULE AIM/CUE
encapsulation dot1Q 101
ip address 10.1.101.1 255.255.255.0
interface Service-Engine0/1
discription AIM/CUE VOICEMAIL MODULE
ip unnumbered FastEthernet0/0.101
service-module ip address 10.1.101.2 255.255.255.0
service-module ip default-gateway 10.1.101.1
ip route 10.1.101.2 255.255.255.255 Service-Engin0/1
dial-peer voice 40 voip
description ** cue voicemail pilot **
destination-pattern 6000
session protocol sipv2
session target ipv4:10.1.101.2
dtmf-relay sip-notify
codec g711ulaw
no vad
dial-peer voice 41 voip
description ** cue auto attendant **
destination-pattern 6001
session protocol sipv2
session target ipv4:10.1.101.2
dtmf-relay sip-notify
codec g711ulaw
no vad
dial-peer voice 1 pots
description ** T1 PRI Emergency 911 **
destination-pattern 9911
port 0/0/0:23
forward-digits 3
dial-peer voice 2 pots
description ** T1 PRI OutBnd Calls **
destination-pattern 9T
port 0/0/0:23
dial-peer voice 3 pots
description ** T1 PRI InBnd Calls**
incoming called-number .
direct-inward-dial
port 0/0/0:23

Problem has to do with how many Digits are getting sent to voice mail on the router when it tries to make the call. You should be seeing 10 digits in the debug.
Next question when one ephone calls another ephone locally does voice mail work?
Try the following commands. This will create a translation-rule that will strip incoming 10 digits to the 4 digits you need. I assume you do not need all 10 digits.
voice translation-rule 1
rule 1 /^650$....$/ /\1/
voice translation-profile digitstrip
translate called 1
voice-port 0/0/0:23
translation-profile incoming digitstrip
*************Voice port were you Telco Line comes in Port 0/0/0:23 based on your config*************
telephony-service
no dialplan-pattern 1 6503926... extension-length 4
Ronnie

Error Type unknown address 00083578

Hi,
Does anyone know what "Error Type unknown address 00083578" means?
Thanks

Hi,
As for the other error message I posted, It's happens apparently randomly (although nothing is random, it's just that I can't identify the pattern) when I use "debug VBS script".
I didn't save a print screen, if I get it again I'll post a print screen

ERROR: /dev/archiso found but the filesystem type is unkown

My problem is now solved in the previous thread on this topic. I apologize for a double post! The previous topic was marked [Solved] and I assumed no one would respond there.
I had the problem trying to boot from usb: boot device not showing up after 30 seconds and thrown into ramfs$. The other topic w/ this problem is marked solved so I'm posting my problem again (sorry).
cat /proc/scsi/scsi shows that device is detected...
did:
ln -sf /dev/sdb1 /dev/archiso
and logged out ("exit")
but immediately a new error, and kernel panic, so I can't copy/paste output:
"ERROR: /dev/archiso found but the filesystem type is unkown"
Sorry about ridiculous pic but it does show kernel panic, just trying to help... couldn't copy output. I can post dmesg from prior to kernel panic if you want (but it doesn't include errors).
Thank you for your help.
I just did:
cat /lib/udev/rules.d/00-archiso-device.rules
ACTION=="add|change", SUBSYSTEM=="block", IMPORT{program}="vol_id --export $tempnode"
ENV{ID_FS_LABEL_ENC}=="ARCHISO_OINGAE2I", SYMLINK+="archiso"
"SYMLINK+=" ... is "+=" typo?
Last edited by jaf777 (2009-08-12 17:13:36)

Same issue:
The specified store provider cannot be found in the configuration, or is not valid. ---> System.ArgumentException: Unable to find the requested .Net Framework Data Provider. It may not be installed.
You mention "Sounds like the client system doesn't have an Oracle client installed."
I am using Win Server 2008 R2. I have installed what i think is the right client. How do i tell?
What is the right client? Where do i get it?

AIM-CUE module

Hi
I have installed an AIM-CUE into my 2801 router, but there are some files which am not sure which will work with this AIM-CUE which l have installed into the router 2801. These are files that l have and l need an advise concerning these files because l have the nme and the aim files but the device that l have installed into my router 2801 is AIM-CUE. Advice me on which ones to use pls.
Ojay
1 cue-installer.nme.7.0.3
2 cue-vm-installer-k9.nme.7.0.3.prt1
3 cue-vm-k9.nme.7.0.3pkg
4 cue-vm-licence_50mbx_ccm_7.0.3pkg
5 cue-vm-en_US-langpack.nme.7.0.3prt1
6 cue-vm-full-k9.nme.7.0.3.prt1
7 cue-vm-langpack.nme.7.0.3.pkg
8 cue-installer.nm-aim.7.0.3

Hi Ojay,
Here we go
For NM-CUE, NM-CUE-EC, and AIM-CUE (cue-vm-k9.nm-aim.7.0.x.zip)
•cue-installer.nm-aim.7.0.x
•cue-vm-k9.nm-aim.7.0.x.pkg
•cue-vm-full-k9.nm-aim.7.0.x.prt1
•cue-vm-installer-k9.nm-aim.7.0.x.prt1
•cue-vm-langpack.nm-aim.7.0.x.pkg
http://www.cisco.com/en/US/docs/voice_ip_comm/unity_exp/rel7_0/install/boothelp.html#wp1142398
And;
cue-vm-en_US-langpack.nm-aim.7.0.6.prt1
Release Date: 05/OCT/2010
Package payload containing all US English language data and prompt files associated with the Cisco Unity Express with VoiceMail application on the AIM-CUE, NM-CUE, and NM-CUE-EC service modules.
Size: 27537.68 KB (28198577 bytes)
Cheers!
Rob
Please remember to tag your threads and help support "Teachers without Borders"
https://supportforums.cisco.com/community/netpro/idea-center/communityhelpingcommunity

Unhandled token type: Unknown token: 0x45 converting sqlserver smalldatetime to oracle timestamp

Hi!
I'm using ODI 12c to migrate some data from MS Sql server DB to Oracle 12c DB.
I'm using LKM SQL to Oracle and IKM Oracle Update.GLOBAL.
In conversion, i'm using CAST(<smalldatetime field> AS TIMESTAMP).
In step Load Data of LKM SQL to Oracle i'm getting the following error:
8000 : 08006 : java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]Unhandled token type: Unknown token: 0x45
java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]Unhandled token type: Unknown token: 0x45
I think it could be caused by the use of LKM SQL to Oracle instead of LKM MSSQL to Oracle. I use SQL to Oracle because I have no agent configured.
Can you help please? Has anyone experienced this error?
Thanks!

this appears to be an api management issues, not AAD. Its not appropriate to punt this to the AAD team.
debugging what api management token request on the (AAD) STS sends, in the posted form body, we see
grant_type=authorization_code
code=AAABAAAAvPM1KaPlrEqdFSBzjqfTGKuDarHWcVaE_gAW-T8bBEhryxGinvUkA66Jt-uxbmRl8J5rjUc0aFJi94eDUoO9Bnt-6NR2sXVQYRXhygLUhjdLYrV9UmlBKZu2U_WZFSXO1_6oeIr-1Phz7VoooKJm0Vmh-N4lfUYdPTsbpgbWMhqA60jkFdiGbAwL0ocUrPw-4V8-8PwddLb1mcFOcGERx1jKa62ffZ9L22tJwkAgHhQPvk4K4TDAq60YY1JMWMgUeL9zc3oT_C6AXv6BkiK-cDm6mE9vx3ZTqz6oHP6LdUqE4QO6hukp7ptcr2Tl15WpJus-Ro4hM4gmdXer7hlwBVM22RLdPBKKZOsm649q12SokmOTdhgHcUX0y2aDxqNPhcTwy0z1QNj6pdZ4PiEVJ9i-qxvZrdB2MUSUNrJ7Lw5bEvzD1rM_eSOPjx-rKwu6gSWqYTNFbXcaBgEoQA6m8PULBdItUNwVwjcyeXTHvEhqrYJLBGdhjpucFGTDYqiteM5zyhFj-GiRkS--9x0kv4vg9TbYl0fLFv8bJwjkG19yZIwVKCVelzZ3TVvsQfyT9srcFCCv6BGu2QnLgA-la0Vksu9NnXHh1hpnO1drt7QLXj6p2FTHhCIDEKv1EobQJwFol8yrsTSdi4wJnYa-dvObvFmXn_8nBw57qKFRp-ogAA
redirect_uri=https%3a%2f%2frapmlsqa.portal.azure-api.net%2fdocs%2fservices%2f54e4f45e73c60f106453dac3%2fconsole%2foauth2%2fauthorizationcode%2fcallback
client_id=0bc904ae-3f2c-4ec7-8b71-40f7207112f0
client_secret=fV1OJsfRFOTDdIqTzs%2fdZCRJkHvcPr9fZGJhWo1dQNg%3d
the (Azure) token endpoint receiving this objects to a missing resource parameter, which is admittedly marked as option in the documentation
https://msdn.microsoft.com/en-us/library/azure/dn645542.aspx
it makes perfect sense that in a confidential client flow that the STS would requires nomination of the intended consumer of the token (i.e the api manager endpoint).
This seems to be case where AAD needs two application definitions : one for the requesting all (the developer console) and one for the API manager endpoint itself, whose entity name can be configured so that the subject console app (registration in
AAD) can be granted access to the object endpoint (registration in AAD) with some permission declared in the permission model of the API.

AIM-CUE - Filesystem type unknown ?

Similar Messages

Maybe you are looking for