are you running both from the same path? You are using quite an old version of the API - it's not inconceivable that the path is important in that version (where it's not in the current for sure).
Are you talking about the path the asp/vbs scripts are located? Yes, it's the same.
Do we have to update the whole server installation to update the api to the latest version?
yes, you won't be able to use a 5.2 API with a 5.1 install - the minor version is not so important, but you can't mix 5.1 and 5.2
Do you have the sdmcfg.ini file in the same directory as the com object? Not sure why it would matter but who knows...
Yes, ist all in c:\Program Files\SBAdmin
I would specify a database tag on both scripts - the error means that the specified db does not exist.
is the DB local, or is it on a network share? Your script should really be referencing the dbserver, not the db itself.
if I add the correct database name
nothing changes. Works in vbs, gives an error in asp:<ResultCode>0xdb000002</ResultCode><ResultDescription>The database has not been created or initialised yet</ResultDescription>If I use a wrong database name<Database>foobar</Database>both scripts result in:<ResultCode>0xc1000005</ResultCode><ResultDescription>Database entry not found</ResultDescription>The scripts are executed on the Safeboot-Server.Obviously the COM object finds the database but is not able to connect to it when called in asp.
Must be some funky rights issue with IIS them preventing it getting to sdmcfg.ini
Sorry - I am out of ideas, it's a windows problem it seems if you are running vbs and the asp page from the exact same folder on the IIS server. Maybe use filemon etc from sysinternals to watch what files the ASP page opens when it runs the code?