|
Home > Archive > microsoft.public.exchange2000.admin > October 2002 > AutoDL Upgrade 2.1
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
AutoDL Upgrade 2.1
|
|
|
| I've upgraded from AutoDL 2.0 to AutoDL 2.1.
AutoDL 2.0 was working fine, including access to it's web interface
and I was able to run the DLAdmin tool successfully.
After upgrading to version 2.1 I have the following major
problems/observations:
1. When I try to run DLAdmin a dialog with this error pops up:
Error #-2147217900
[Microsoft][ODBC SQL Server Driver][SQL Server]RAISERROR could not
locate entry
for error 80155 in sysmessages.
(Source: Microsoft OLE DB Provider for ODBC Drivers)
and the only option is to click 'OK' to close DLAdmin, and I get
another dialog that says 'ERROR LOADING APPLICATION'.
2. The web interface is no longer functioning properly. I keep getting
the same message in the frames, along the lines of (actual domain name
and user id removed):
'The account 'domain\userid' is not recognized by the AutoDL
system.... "
3. After installing the ADLAGENT service the URL for the helpdesk that
gets entered at the command prompt does not appear on the web page.
My sense is that something is not right with the database after
running the scripts for SQL that came with the 2.1 upgrade, or there
is a problem with some of the entries in the ADLParameters table.
Has anyone else encountered this, and more importantly, does anyone
have any suggestions as to how to fix it? As I mentioned, everything
seemed to work ok w/ 2.0.
| |
|
| As a follow up, I noticed that the AutoDL Agent service is talking to
the Active Directory and that the DSObjects table in the AutoDL DB is
being populated/modified; there are AutoDL/Service Event 100 messages
showing up in the App Log, and I received a mail message (AutoDL:
Daily Change Report....) from the AutoDL Agent at midnight describing
any modifications that were made to the DLs that I had already created
w/ AutoDL version 2. That's the good news.
The bad news:
The same 3 problems that existed in my previous post are still
unresolved. Any helpful suggestions?
1. Web interface: User not recognized by system messages.
2. DLAdmin: Bombs when I try to run it with a SQL error.
3. Web interface: Helpdesk and AutoDL server URLs do not use the
entries that were given when I configured ADLAGENT.
As I mentioned, everything was working okay with version 2.0 of
AutoDL, but is no longer working after upgrading to 2.1.
| |
| David Eales 2002-10-05, 8:45 pm |
| Wow, you mean you actually got version 2.0 to work. I am having trouble like
everybody else trying to get the original verison to work. Can you remember
if you had to do anything special to get version 2.0 to work. I have gone
through the instructions many times now and I think all my sql stuff is
correctly configured as the adl_sync.cmd command works fine though like you
I get an SQL error when I try and use DL admin.
As soon as I can get version 2.0 going then I will look at trying to do 2.1
and see if I have any difficulties.
Hope you can help on this one....
Thanks
"Gerry" <syrreg@yahoo.com> wrote in message
news:4d9e16db.0209240446.7aab1ce1@posting.google.com...
> As a follow up, I noticed that the AutoDL Agent service is talking to
> the Active Directory and that the DSObjects table in the AutoDL DB is
> being populated/modified; there are AutoDL/Service Event 100 messages
> showing up in the App Log, and I received a mail message (AutoDL:
> Daily Change Report....) from the AutoDL Agent at midnight describing
> any modifications that were made to the DLs that I had already created
> w/ AutoDL version 2. That's the good news.
>
> The bad news:
>
> The same 3 problems that existed in my previous post are still
> unresolved. Any helpful suggestions?
>
> 1. Web interface: User not recognized by system messages.
> 2. DLAdmin: Bombs when I try to run it with a SQL error.
> 3. Web interface: Helpdesk and AutoDL server URLs do not use the
> entries that were given when I configured ADLAGENT.
>
> As I mentioned, everything was working okay with version 2.0 of
> AutoDL, but is no longer working after upgrading to 2.1.
|
|
|
|
|