Post reply

MSSQL 2005 xp_cmdshell not functioning as expected.

  • July 13, 2008 at 7:38 pm

    #842159

    could it be pathing to isql? I've seen some strange behavior with sybase and MS isql programs and environment paths.

  • July 13, 2008 at 7:51 pm

    #842168

    I initially thought this as well. So I made the Sybase portion of the path variable the same on both machines (EDIT - in the same location within the PATH statement also). Sadly - no effect.

    I've been testing this on some other servers (Windows 2003, Windows 2000 / MSSQL 2005, MSSQL 2000) and have had it work successfully. However, these are all test servers. I can't leave my utility on a test server - it will eventually get nuked. The main reason I want it off my pc ;).

    Any thoughts are good thoughts - keep 'em coming folks :).

  • July 14, 2008 at 4:03 pm

    #842740

    Okay - I have found a solution and the cause of the fault. For those interested, details are below:

    When the server was built, it was a rushed build to replace an already crashed production box.

    During the haste, the server was not rebooted after the Sybase install. This is not entirely unusual however, as the install does not prompt you to reboot post install. Not only that, but the Sybase client tools are 99.9% functional, with the 0.1% non-functionality in the original post.

    Note - that running the isql.exe tool from the command-line is still successfull, and will enable you to connect to a Sybase database engine.

Viewing 3 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply