[SOLVED]gnome-volume-manager / hal 0.5.10 - can't deactivate automount

http://wiki.archlinux.org/index.php/HAL
I've created /etc/hal/policy/preferences.fdi
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
<device>
<match key="storage.hotpluggable" bool="false">
<match key="storage.removable" bool="false">
<merge key="storage.automount_enabled_hint" type="bool">false</merge>
</match>
</match>
</device>
</deviceinfo>
The article say "Policies" may be deprecated in hal 0.5.10. I doubt that, but i dont know what is deprecated though.
I did check the documentation out, and everything i did still seems to be valid.
http://people.freedesktop.org/~david/ha … ies-volume
Does gnome-volume-manager honor this setting in gnome 2.20?
Last edited by pelle.k (2008-02-04 20:12:51)

It would seem i solved it myself.
First of all, gnome-volume-manager need to be recompiled with a patch i found (ubuntu gutsy); http://patches.ubuntu.com/by-release/ex … hint.patch
Why this isn't included by default in gnome-volume-manager is beyond me!? You bad, bad, gnome devs!
Replace the PKGBUILD when building from ABS.
# Contributor: Link Dupont <[email protected]>
pkgname=gnome-volume-manager
pkgver=2.17.0
pkgrel=3
pkgdesc="GNOME daemon to auto-mount and manage media devices"
arch=(i686 x86_64)
license=('GPL')
url=http://www.gnome.org/
depends=('libgnomeui>=2.20.0' 'libnotify>=0.4.4' 'gnome-mount>=0.6')
makedepends=('nautilus>=2.20.0' 'perlxml' 'pkgconfig')
install=gnome-volume-manager.install
groups=('gnome-extra')
source=(http://ftp.gnome.org/pub/GNOME/sources/${pkgname}/2.17/${pkgname}-${pkgver}.tar.bz2
gvm-mount-async.patch
gvm-check-local.patch
http://patches.ubuntu.com/by-release/extracted/ubuntu/g/gnome-volume-manager/2.17.0-2ubuntu2/02_honour_automount_enabled_hint.patch)
md5sums=('104cec26e721e0bba69debd392367195'
'534b8b9633148bd975b2b9b518c41fb4'
'cb45810b2adb95d39e1272470f10a21a'
'7288a9dc57df321d6a379c9b6a7caaff')
build() {
cd ${startdir}/src/${pkgname}-${pkgver}
patch -Np0 -i ${startdir}/src/gvm-mount-async.patch || return 1
patch -Np0 -i ${startdir}/src/gvm-check-local.patch || return 1
patch -Np1 -i ${startdir}/src/02_honour_automount_enabled_hint.patch || return 1
./configure --prefix=/usr --sysconfdir=/etc \
--localstatedir=/var
make || return 1
make GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL=1 DESTDIR=${startdir}/pkg install
mkdir -p ${startdir}/pkg/usr/share/gconf/schemas
gconf-merge-schema ${startdir}/pkg/usr/share/gconf/schemas/${pkgname}.schemas ${startdir}/pkg/etc/gconf/schemas/*.schemas
rm -f ${startdir}/pkg/etc/gconf/schemas/*.schemas
Also, this is my /etc/hal/fdi/policy/preferences.fdi
<match key="storage.hotpluggable" bool="false">
<match key="storage.removable" bool="false">
<merge key="storage.automount_enabled_hint" type="bool">false</merge>
</match>
</match>
If you compare that to my first version, you'll note that it is *not* enclosed in <deviceinfo> and <device> tags, simply because that wouldn't work. Don't ask me why. i'm by no means a HAL expert...
Last edited by pelle.k (2008-02-04 20:12:00)

Similar Messages

  • [SOLVED] gnome-volume-manager is lazy

    Until some update that I missed all was fine. I boot, my volumes are mounted, I can see them in ROX (my main file management program).
    I insert a CD/DVD/whatever, its mounted and its all in /media/.:D
    But now it just does nothing, until I start Nautilus, then everything gets mounted.
    I close Nautilus, and it doesnt mount anything again.
    gnome-volume-manager process is up and running after login before running nautilus and after closing it too.
    How can I make it behave nicely without the nuisance that Nautilus is?
    Oh and Im running Openbox as the window manager in Gnome, Nautilus desktop handling disabled.
    Last edited by Hohoho (2008-05-28 20:21:12)

    i had the same problem.
    i looked in the changelog and it appears that from now on the automount function is disabled upstream because that function is to be handled by the nautilus ( http://ftp.gnome.org/pub/GNOME/sources/ … .3.changes ). For me it is a problem because i use openbox and thunar, so you just have to recompile the package with the option: "--enable-automount" .
    info from:
    ~/Desktop/gnome-volume-manager-2.22.3  $  ./configure --help
    then start it ( after recompiling with abs, for example ), but look that the path changed, now in my autostart file for openbox i have:
    /usr/lib/gnome-volume-manager/gnome-volume-manager --sm-disable --daemon=yes &
    hope it helps you, because this annoyed me for a long time and this is the only easy way to mount my partitions easily
    Last edited by Diaz (2008-05-28 20:04:56)

  • Mounting drives on a udev+hal+gnome-volume-manager setup

    Hi,
    I set up Arch Linux on a friends computer. The setup seems to work, for example gnome-cd is started when one inserts an Audio CD. However, everything that involves mounting does not work. The error message given by gnome-volume-manager is
    mount: wrong fs type, bad option, bad superblock on /dev/sda1,
    or too many mounted file systems
    * /bin/mount has sid set, 755, owner and file group are root
    * udev is set up correctly, so /dev/hdc for example does have write rights for the group disk, and the user is member of that group.
    What could be wrong?

    The problem was mainly about mounting, and not about /dev/sda or /dev/hdc. We found the solution:
    The "mount" binary in Arch's current is confused by the entry "managed" that hal puts in /etc/fstab. You can correct this by
    a) Adding a policy file in /usr/share/hal/fdi/95userpolicy named, for example, local.fdi that hinders hal from doing so:
    <?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
    <deviceinfo version="0.2">
    <!-- Default policies merged onto computer root object -->
    <device>
    <match key="info.udi" string="/org/freedesktop/Hal/devices/computer">
    <merge key="storage.policy.default.managed_keyword.primary" type="string">user</merge>
    </match>
    </device>
    </deviceinfo>
    Then restart hal by typing
    /etc/rc.d/hal restart
    as root
    b) Patching "mount" as described in Arch Linux bug #1930.[/code]

  • Dbus/hal/gnome-volume-manager problem

    I've got hal and dbus running but it doesnt even seem that gnome-volume-manager is started. I added it to my gnome session but that didnt seem to do the trick. I'm trying to be able to just plug in my usb key and ipod and have them automount. It works if I restart hal or run gnome-volume-manager from the command line but then work work again unless I restart that stuff again. Here is a cut from my fstab:
    /dev/sda1 /mnt/usb auto user,noauto 0 0
    /dev/sda2 /mnt/ipod auto user,noauto 0 0

    Hi lhoerste,
    I had this problem with automount as well. The way I fixed it was adding
    dbus hal to daemons line in /etc/rc.conf. You probably did this already.
    Next, when you are in the gnome desktop, stick in a cd. Nothing happens right?
    Now go to preferences=>removable drives and media (I think this is what it is called. I'm not sitting infront of my computer at the moment). Then make sure that the checkboxes pertaining to "mount automatically" are checked.
    Close window.
    Now your cd should automount and appear on the desktop. Eject the cd by right clicking on the icon and choosing eject.
    Now, restart and ***make sure you save settings*** before leaving.
    Get back into the gnome desktop and plug your cd back in. It should automount now.
    This is how I got automount to work for me.

  • Suggestion for dbus, hal. new gnome-volume-manager-version.

    Heya,
    I just installed dbus, hall from cvs and gnome-volume-manager from tarball and have some suggestions:
    dbus:
    the default during configure seems to be to detect if you have the necessary things installed and based on that enable a component.
    To disbale qt-bindings add:
    --disable-qt
    to configure, else it will try to compile the qt-bindings and without a libGL.la it won't work ... (and this isn't in the Mesa package or wasn't anyway as far as I can tell).
    hal:
    could you add the option "--enable-fstab-sync" to configure in the new versions? It seems to be usefull . It can be it wasn't available earlier ...
    gnome-volume-manager:
    I just upgraded to 0.9.9 If anyone wants to have the binary just tell me where to upload.
    greetz,
    Michel

    Michel wrote:
    Heya,
    I just installed dbus, hall from cvs and gnome-volume-manager from tarball and have some suggestions:
    dbus:
    the default during configure seems to be to detect if you have the necessary things installed and based on that enable a component.
    To disbale qt-bindings add:
    --disable-qt
    to configure, else it will try to compile the qt-bindings and without a libGL.la it won't work ... (and this isn't in the Mesa package or wasn't anyway as far as I can tell).
    there are solutions on this forum to fix the libGL.la. this file will be included with future builds of xorg/xfree86. NVIDIA drivers should also provide this file. this file is only an issue for building.
    file a bug report feature report to add this build option to the package
    hal:
    could you add the option "--enable-fstab-sync" to configure in the new versions? It seems to be usefull . It can be it wasn't available earlier ...
    if this package is in one of the three official repos file a feature request.
    gnome-volume-manager:
    I just upgraded to 0.9.9 If anyone wants to have the binary just tell me where to upload.
    if a package has just fallen out of date up to about two week leave time for the maintainer to upgrade it .  you can flage the package out of date via the web page. this is way better than offering it to people or uploading it somewhere.
    the flag otu of date feature is always a better option to cluttering the list with update requests and the bug tracker is the best way to convey your wanted build changes. alot of the developers do not frequent this forum but all are member of the bug tracker notification system.

  • Hal/Dbus/gnome-volume-manager mount permission problem

    Hello,
    I have hal/dbus/gnome-volume-manager installed (of course I use gnome as DE).
    I need help in configuring the permissions for automatically mounted disk/partitions.
    When I connect an external USB HDD having 1 NTFS and 1 partition, these partitions are auto-mounted and the desktop icons appear for the both.
    As a normal user I am able to read/write FAT partition (I think, not because I have configured anything properly, but because FAT does not support permissions on filesystem), but I am not even able to read (browse) NTFS filesystem (ERORR: You do not have permission...).
    Yes, I have NTFS filesystm support enabled, because I am able to access that same NTFS partition as root.

    Well, Thanks for the reply but I had not put any static entry in fstab for this external USB HDD.
    Anyway, I figured out something (havn't tested it yet)
    When an external USB HDD is attached ... depending storage.policy and volume.policy rules in /usr/share/hal .. the hal daemon (hald) calls fstab-sync with appropriate parameters.
    fstab-sync, then, generates /etc/fstab enteries automatically (with comment=managed keyword).
    I have added a user policy so that umask and gid value is set correctly. I'll test is as soon as I'll get time.
    In the meanwhile if anybody have any other suggestions, please post it here.

  • Firewire and gnome-volume-manager

    I have a firewire scanner, when hotplugged, nothing happens in gnome. I have 'run when scanner is plugged' checked, but I get nothing.
    Does gnome-volume-manager work with firewire devices? or is it just my scanner? (Canon 2540 photo)

    I don't know about scanners, but my firefire external HD is recognised perfectly by gnome-volume-manager. So it does listen for firewire devices. Maybe you'll need to add something to udev to make gnome-volume-manager know it's a scanner?
    I have a scsi scanner, so I won't try hotplugging it

  • Gnome-volume-manager doesn't work, nor another automounter

    Hi there,
    I have installed gnome-volume-manager but it apparentely does not work. I've followed the instructions from the FAQ - Arch Linux, and I have tried also recompiling it with --enable-automounting. I have tried also having Nautilus opened at the same time but it didn't work. My WM is IceWM.
    //ivman works for the cdrom but not for usb devices. And I don't like AutoFS.
    Last edited by jmcejuela (2009-04-10 15:06:34)

    I had this problem and it was related to ConsoleKit not being initialized properly. I was using SLIM as login manager and had to add ck-launch-session to my .xinitrc when starting the gnome session.
    Last edited by iBertus (2009-04-10 17:21:33)

  • Gnome-volume-manager freezes xfce4 on logout

    Hi there,
    I configured gnome-volume-manager to automatically mount drives (esp. usbsticks and so on) and it is working quite smoothly.
    But one side effect is bothering me a little:
    As suggested in a gnome-volume-manager HowTo, the volume manager is loaded on startx in the following form
    <.xinitrc>
    exec startxfce4 & exec gnome-volume-manager
    </.xinitrc>
    as soon as I try to quit my Xfce session the session hangs and will not terminate properly, i.e. logfoff-screen appears but session is not ended.
    I waited for quite a while (about an hour  :shock: )...
    As I didn't change too much over the last few days, I quickly found out that the gnome-volume-manager is the culprit. As soon as the 'exec gnome-volume-manager' part is removed, Xfce will shut down normally.
    Has anyone else encountered this side effect? Is there a solution?
    Greez and Thx
    Bernhard

    JGC wrote:I wouldn't start gnome-volume-manager that way, I would configure xfce4 to add gnome-volume-manager to the session when it starts up. Putting it in your .xinitrc makes xfce4 unaware of gnome-volume-manager.
    Sounds logical.
    It was the way described in the HOwTo, though. That's why I started the volume-manager like this. I would have preferred a more general approach, starting the gnome-volume-manager someplace more general (and not separately for each user)
    I guess the correct place would be somewhere in ~/.config/xfce4??
    I would have thought maybe the xinitrc that resides there... (Maybe along with xftaskbar4...)
    Or is there a more suitable file??
    Greez
    bernhard

  • [SOLVED] GNOME Power Manager Icon

    Hello,
    With the recent influx of GNOME 2.22 packages, gnome-power-manager has begun to behave strangely on my system.
    In gnome-power-preferences, I have specified that the notification area icon should only be displayed when my laptop battery is charging or discharging. Since I upgraded my GNOME packages, the icon has always appeared in my notication area upon login -- even if I am running on AC power. In that situation, the tooltip for the icon reads as follows:
    Computer is running on AC power
    Laptop batteries discharging (100%)
    Battery discharge time is currently unknown
    If I unplug the power cord from my computer,  the icon (strangely) disappears. If I then proceed to plug the cord back in, the icon will appear briefly (I assume to indicate that what little power was drained from the battery is being replenished) and then disappear once more.
    This problem is occurring on a Dell Inspiron 6400 (E1505). I feel that I might need to report this issue as a bug, but I'd first like to know if anyone else has noticed this oddity since the upgrade.
    Thanks!
    Edit:
    It seems as if gnome-power-manager thinks that I have two laptop batteries (though I have only one). Clicking on the notification icon lists two batteries: one with the usual "on AC power" icon and the other with the "discharging" (standard battery) icon.
    I do not think that there are any problems with ACPI: running acpi yields the following:
    Battery 1: charged, 100%
    I'm not quite sure where gnome-power-manager procures its information about the batteries)....
    Last edited by ssjlegendx (2008-04-20 18:34:53)

    I just updated to HAL 0.5.11rc2-2, and it seems that my problem has been solved!
    I didn't see the related bug report before starting this thread.... Thanks, JGC!
    Last edited by ssjlegendx (2008-08-02 20:44:41)

  • Gnome-volume-manager and plugdev

    I'm trying to work out some kinks in gnome-volume-manager0--namely, that I cannot unmount disks as a regular user.  Everything I have found says that a user must be a member of the plugdev group for such things to work, so I looked around and found that I should be able to add myself to the plugdev groups like so:
    usermod -G plugdev isez2001
    But upon giving this command, I receive an error saying that the plugdev group is unknown.
    Do I have to create the plugdev group myself?  If so, why?  It really seems like something that should be made to just work.

    Alright, I'm a member of the storage group already.
    Upon further investigation, I find that my USB flash drive is autmounted in /media under the group "root," and my DVD drive automounts under the group "-1".
    I am unable to unmount either of these as a normal user.
    Is there something I should do that will make disks mount under the storage group?

  • [SOLVED] gnome-power-manager issues since update?

    Since maybe an update (I'm not sure), gnome-power-manager isn't launched anymore. No battery applet, suspend and hibernation buttons.
    acpid, pm-utils are on.
    By launching it in terminal, it gives:
    ~$ gnome-power-manager
    (gnome-power-manager:3238): libupower-glib-WARNING **: Couldn't enumerate devices: Launch helper exited with unknown return code 127
    TI:17:42:09 TH:0x10cf090 FI:gpm-engine.c FN:gpm_engine_coldplug_idle_cb,834
    - failed to get device list: Launch helper exited with unknown return code 127
    Traceback:
    gnome-power-manager() [0x419a64]
    gnome-power-manager() [0x41904e]
    /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1f3) [0x7f72b683abf3]
    /usr/lib/libglib-2.0.so.0(+0x423d0) [0x7f72b683b3d0]
    /usr/lib/libglib-2.0.so.0(g_main_loop_run+0x182) [0x7f72b683ba42]
    gnome-power-manager() [0x40f11b]
    /lib/libc.so.6(__libc_start_main+0xfd) [0x7f72b6239c3d]
    gnome-power-manager() [0x407a49]
    So would libupower-glib bug?
    Last edited by feNNec (2011-01-16 19:03:59)

    yes there is:
    $ ./upowerd start
    ./upowerd: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory
    libusb-1.0.8-1 is installed
    What's this daemon for?

  • [SOLVED] gnome-power-manager ignores dpms_method_ac

    There's no way (it seems ) to make gnome-power-manager 2.26.3-1 to work fine...
    i'd like to put my monitor in standby after a while instead of simply blank and so i set dpms_method_ac  in gconf accordingly... but with no success...
    i don't know where to find a solution...
    my laptop is a HP pavillion dv5 1210el and thisi is my actual xorg.conf:
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 1.0 (buildmeister@builder63) Wed May 27 03:15:36 PDT 2009
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Synaptics Touchpad" "SendCoreEvents"
    InputDevice "USB Mouse" "CorePointer"
    EndSection
    Section "InputDevice"
    Option "Device" "/dev/input/mice"
    Option "Protocol" "Auto"
    Option "ZAxisMapping" "4 5"
    Identifier "USB Mouse"
    Driver "mouse"
    Option "Emulate3Buttons" "true"
    EndSection
    Section "InputDevice"
    Identifier "Synaptics Touchpad"
    Driver "synaptics"
    Option "SendCoreEvents" "true"
    Option "Device" "/dev/psaux"
    Option "Protocol" "auto-dev"
    Option "SHMconfig" "on"
    Option "LeftEdge" "1700" # x coord left
    Option "RightEdge" "5300" # x coord right
    Option "TopEdge" "1700" # y coord top
    Option "BottomEdge" "4200" # y coord bottom
    Option "FingerLow" "25" # pressure below this level triggers release
    Option "FingerHigh" "30" # pressure above this level triggers touch
    Option "MaxTapTime" "180" # max time in ms for detecting tap
    Option "VertEdgeScroll" "true" # enable vertical scroll zone
    Option "HorizEdgeScroll" "true" # enable horizontal scroll zone
    Option "CornerCoasting" "true" # enable continuous scroll with finger in corner
    Option "CoastingSpeed" "0.30" # corner coasting speed
    Option "VertScrollDelta" "100" # edge-to-edge scroll distance of the vertical scroll
    Option "HorizScrollDelta" "100" # edge-to-edge scroll distance of the horizontal scroll
    Option "AccelFactor" "0.0020" # acceleration factor for normal pointer movements
    Option "VertTwoFingerScroll" "true" # vertical scroll anywhere with two fingers
    Option "HorizTwoFingerScroll" "true" # horizontal scroll anywhere with two fingers
    Option "EmulateTwoFingerMinZ" "120" # this may vary between different machines
    Option "TapButton1" "1"
    Option "TapButton2" "2"
    Option "TapButton3" "3"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbModel" "hpdv5"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Unknown"
    HorizSync 28.0 - 33.0
    VertRefresh 43.0 - 72.0
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    Option "RenderAccel" "true"
    Option "DamageEvents" "True"
    Option "NoLogo" "true"
    Option "AddARGBGLXVisuals" "True"
    Option "DisableGLXRootClipping" "True"
    Option "OnDemandVBlankInterrupts" "True"
    Option "RegistryDwords""PowerMizerEnable=0x1; PerfLevelSrc=0x2233; PowerMizerDefault=0x3"
    Option "BackingStore" "True"
    Option "TripleBuffer" "True"
    Option "DPMS" "true"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    Section "Module"
    Load "glx"
    Load "synaptics"
    EndSection
    thanx!
    Last edited by euLinux (2009-07-29 07:02:14)

    hi miau!
    i changed my xorg.conf to match your suggestions... Option "DPMS" "true" moved in Monitor section and blanking and dpms settings in ServerLayout:
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Synaptics Touchpad" "SendCoreEvents"
    InputDevice "USB Mouse" "CorePointer"
    Option "BlankTime" "0"
    Option "StandbyTime" "10"
    Option "SuspendTime" "15"
    Option "OffTime" "20"
    EndSection
    i guess you suggested me to do this way, isn't it?
    unfortunately it still doesn't work!
    it seems that after login gnome-power-manager resets all the settings about dpms in xorg.conf... every section i put them in...
    this is part of the output of xset q just after login:
    Screen Saver:
    prefer blanking: yes allow exposures: yes
    timeout: 0 cycle: 600
    Colors:
    default colormap: 0x20 BlackPixel: 0 WhitePixel: 16777215
    Font Path:
    /usr/share/fonts/misc,/usr/share/fonts/100dpi:unscaled,/usr/share/fonts/75dpi:unscaled,/usr/share/fonts/TTF,/usr/share/fonts/Type1,built-ins
    DPMS (Energy Star):
    Standby: 0 Suspend: 0 Off: 0
    DPMS is Enabled
    Monitor is On
    any other idea?
    thanx

  • Gnome-volume-manager can't automount removable media any more

    Strange,  I don't know why, it worked perfectly, but now it lost functionability. Anyone with any suggestion? Thanks in advance.

    Strange,  I don't know why, it worked perfectly, but now it lost functionability. Anyone with any suggestion? Thanks in advance.

  • Kde-volume-manager .. cause manual click on eject on cdrom..

    ...doesnt work anymore...
    Is somewhere kde-volume-manager?? Graphical UI for KDE users ...??
    Because Gnome-volume-manager has the worst support for automount...
    This is stupid  that I want to eject my cdrom and I can't manual click on eject button on cdrom.. beacuse it's locked... <confused>
    Even subfs [submount] or supermount has this implementation...
    Any help??
    post scriptum.... Rest HAL&DBUS work fine..

    ...doesnt work anymore...
    Is somewhere kde-volume-manager?? Graphical UI for KDE users ...??
    Because Gnome-volume-manager has the worst support for automount...
    This is stupid  that I want to eject my cdrom and I can't manual click on eject button on cdrom.. beacuse it's locked... <confused>
    Even subfs [submount] or supermount has this implementation...
    Any help??
    post scriptum.... Rest HAL&DBUS work fine..

Maybe you are looking for

  • Windows server 2012 and windows 7 direct access

    I am looking for some decent documentation on how to get direct access in windows 2012 to work with windows 7 Can anyone point me the right direction?

  • ASO physical clear increases cube size?

    I am testing out performance and feasibility of a physical clear and have noticed that the cube size actually INCREASES after doing a physical delete. The cube size increased from 11.9 GB to 21.9 GB. Anyone know why? Our ASO cube is used as a forecas

  • How to set Content-Disposition to "application/json;"

    Using System.Net.Http.Httpclient, I am trying to do a multipart post in C# and with a wp8. This is a snippet of my code: varclient = newHttpClient();                 client.DefaultRequestHeaders.TryAddWithoutValidation( "Content-Type", "application/j

  • Male to order and Make to stock

    Hi, what are the various  config settings and master data maintenance to be done in SD for Make to order and  Make to stock scenario. what integration points with other modules to be kept in mind for the above two scenarios. regards sachin

  • Cfmx 7 wont connect to MS SQL server

    Hi there, can anyone give me some help with connecting to a DB in MS SQL Server? i'm trying to connect via the cfadmin but i keep getting the following error when verfiying the DB connection: Connection verification failed for data source: sitedirect