The Exclaimer Community

Hi,

I installed the Mail Archiver onto our Exchange 2003 box. The install went ok, but when it was running through the automated steps (creating the accounts, installing the services, ect) it errors out when trying to create the database and stops. The database will be located on our SQL 2000 box. Here is the error it gives:

 Error - There was a problem performing the selected operation (Configuring SQL Server). The following information is available on the error: Syntax error. Expected '##' for macro name at #

 Anyone have any thoughts on what might be causing this? I have tried using multiple accounts to create the DB (administrator, sa, ect) but I still get the same error.

 Thanks for your help!

Hi,

Can you confirm that you have the full version installed and not the msde?

Regards

Richard 

---

Richard Rae
Exclaimer Support

Richard,

 Yes, we have the full version of SQL 2000 Server Standard running. I think it has something to do with the account that is automatically created trying to access SQL. I backed up and ran through the manual setup and changed the service account to the administrator account and it is able to communicate with the SQL server..... now I'm getting a different error. It creates the SQL database, starts to process mail, and withing a couple minutes errors out with the following:

 There was a problem (Error executing SQL statement

usp_InsertMessage

COM Error: 0x80040E14 - IDispatch error #3092 Could not find server 'EXADSI' in sysservers. Execute sp_addlinkedserver to add the server to sysservers.

SQL Error #80040e14

Could not find server 'EXADSI' in sysservers. Execute sp_addlinkedserver to add the server to sysservers.

Source: Microsoft OLE DB Provider for SQL Server

SQL State: 42000

Native Error: 7202

 I looked at the tables and there isn't a sysservers table in either the database or the config database. The only DB that I can find that table in is the master DB.

Any ideas on that? Thanks!

Yep, the linked server is missing

under security then linked server there should be an entry for EXADSI. If it is not htere, please create the following

Name EXADSI

Product name Active Directory Services 2.5

data source: adsdatasource

 

security tab, select Be made using this seurity context at the bottom, and put the admin account in there

Server options,

Ensure that the data access and the use remote collation is enabled.

Regards

Richard

---

Richard Rae
Exclaimer Support

Richard,

 Which selection should I choose for the Provider Name (OLE DB Provider):

-Microsoft Jet 4.0
-Data Mining Service
-DTS Packages
-Indexing Sevices
-Microsoft Search
-OBDC Drivers
-OLAP Services
-Olap Services 8.0
-Oracle
-SQL Server
-Simple Provider
-Microsoft Directory Services


Thanks!

I have ADSDSOObject here.....

 

Richard

---

Richard Rae
Exclaimer Support

I don't have that option on my end. I'm not much of a SQL guy, I wonder what I need to do to add that in as a provider.

Richard,

 

I think I figured that part out, I used the Microsoft Directory Services after reading an artice on Microsofts website and created the Linked Server. It got me farther along. Now the error I get is:

 There was a problem (Error executing SQL statement

usp_InsertMessage

COM Error: 0x80040E14 - IDispatch error #3092 OLE DB error trace [OLE/DB Provider 'ADsDSOObject' ICommandPrepare::Prepare returned 0x80040e14].

SQL Error #80040e14

OLE DB error trace [OLE/DB Provider 'ADsDSOObject' ICommandPrepare::Prepare returned 0x80040e14].

Source: Microsoft OLE DB Provider for SQL Server

SQL State: 01000

Native Error: 7300

 

I see that you were working on this a couple months ago in another thread, but I don't see a solution posted(http://forums.exclaimer.com/forums/thread/1002.aspx)

Any progress with that? Thanks for your continued help!

Ok, figured it out. I had to use the domain admin account and I had to specify the domain name in the account (domain\user). That solved the error above. I am now up and running! Thanks for your help Richard!