MELL 2.5 and SQL errors

I recently installed the SA versions of several MELL 2.5 collections. I can
access the start page and the training with no issues; everything appears to
work perfectly. The problem is, I also installed the SQL database and
Reporting to monitor users and usage, but there appears to be nothing being
written to the database. Also, on the Reports start page, it does not list
any report options pertaining to users. I'm not even sure if the database
installed correctly, but I did not receive any setup errors. Here is the
error I'm getting when I try to access a report:
Microsoft OLE DB Provider for ODBC Drivers error '80040e37'
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object na
me 'node'.
/mell/eng/reports/inc/reportfunctions.inc, line 185
I've noticed that at least two or three others have this same issue, but can
find no solutions listed any where. I am running MELL on IIS 6.0 on Windows
Server 2003 againist SQL 2000 SP3 running on Windows Server 2003.
Any help would be appreciated.No one solve this issue yet?
"swampthing" wrote:

> I recently installed the SA versions of several MELL 2.5 collections. I ca
n
> access the start page and the training with no issues; everything appears
to
> work perfectly. The problem is, I also installed the SQL database and
> Reporting to monitor users and usage, but there appears to be nothing bein
g
> written to the database. Also, on the Reports start page, it does not list
> any report options pertaining to users. I'm not even sure if the database
> installed correctly, but I did not receive any setup errors. Here is the
> error I'm getting when I try to access a report:
> Microsoft OLE DB Provider for ODBC Drivers error '80040e37'
> [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object
name 'node'.
> /mell/eng/reports/inc/reportfunctions.inc, line 185
>
> I've noticed that at least two or three others have this same issue, but c
an
> find no solutions listed any where. I am running MELL on IIS 6.0 on Window
s
> Server 2003 againist SQL 2000 SP3 running on Windows Server 2003.
> Any help would be appreciated.|||If it helps swampthing I can confirm I too have the same problem. It is
preventing me from tracking MELL access.|||Yeah, I saw that at least two or three others had reported this issue, but
could find no resolution. I'm surprised this thread hasn't been responded to
,
since I am using my technet ID for managed newsgroups which is supposed to
answered by Microsoft within something like 24 or 48 hours (can't remember a
t
the moment). I may have to start a new threard if this one doesn't get a
response.
"Welshbloke" wrote:

> If it helps swampthing I can confirm I too have the same problem. It is
> preventing me from tracking MELL access.
>|||Yes, I'm getting the same sort of thing with the same setup as the OP excep
t
the db server is also the IIS server.
I noticed when I installed the first Mell module that reporting appeared to
be working in that I oculd do a view of what was installed, but after
installing the complete Mell system of Desktop, Dev and IT Pro that if I try
to get to reports I just get a jscript popup about the database being
unpopulated (well that would be what it says if the constant was able to be
read to say it).
At this stage I have tried a few things to get it working but nothing has
had any effect, but then again I can't even find where users get created to
allow themselves to track their progress even though there are the tables in
the db and not feeling too confident about the whole product at this stage.
"swampthing" wrote:
[vbcol=seagreen]
> Yeah, I saw that at least two or three others had reported this issue, but
> could find no resolution. I'm surprised this thread hasn't been responded
to,
> since I am using my technet ID for managed newsgroups which is supposed to
> answered by Microsoft within something like 24 or 48 hours (can't remember
at
> the moment). I may have to start a new threard if this one doesn't get a
> response.
> "Welshbloke" wrote:
>|||I am also having the same problems. After 54 hours of installations, doing
each edition seperately, I thought I had done something wrong. I deleted th
e
database, removed each course via the control panel (another 10 hours), and
then started over ... doing 2.0 in each addition, 2.1 in each addition and
then 2.2 in each addition. I still have 2.3 through 2.7 to go, but the
Tracking for 2.0 to 2.2 isn't working ... arrrghghgh. Any help would be nic
e
... documentation on this piece of it is seriously lacking.
"swampthing" wrote:

> I recently installed the SA versions of several MELL 2.5 collections. I ca
n
> access the start page and the training with no issues; everything appears
to
> work perfectly. The problem is, I also installed the SQL database and
> Reporting to monitor users and usage, but there appears to be nothing bein
g
> written to the database. Also, on the Reports start page, it does not list
> any report options pertaining to users. I'm not even sure if the database
> installed correctly, but I did not receive any setup errors. Here is the
> error I'm getting when I try to access a report:
> Microsoft OLE DB Provider for ODBC Drivers error '80040e37'
> [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object
name 'node'.
> /mell/eng/reports/inc/reportfunctions.inc, line 185
>
> I've noticed that at least two or three others have this same issue, but c
an
> find no solutions listed any where. I am running MELL on IIS 6.0 on Window
s
> Server 2003 againist SQL 2000 SP3 running on Windows Server 2003.
> Any help would be appreciated.|||Hey guys,
I resolved my problem with this issue. It turned out to be the sort order of
the SQL installation. We had installed SQL with a binary sort order because
of a requirement of a third-party application. Because of this, I had issues
with MELL, Diskeeper Administrator database, McAfee ePolicy Orchestrator
database, etc., etc. I finally uninstalled everything, reinstalled SQL with
the default sort order and all the applications, including MELL, installed
and worked correctly. So I would suggest looking at your database sort order
;
you may need to change it for the MELL database and reinstall MELL.
This was my solution and I'm not suggesting anyone else do the same, but it
worked for me.
"Craig French" wrote:
[vbcol=seagreen]
> I am also having the same problems. After 54 hours of installations, doin
g
> each edition seperately, I thought I had done something wrong. I deleted
the
> database, removed each course via the control panel (another 10 hours), an
d
> then started over ... doing 2.0 in each addition, 2.1 in each addition and
> then 2.2 in each addition. I still have 2.3 through 2.7 to go, but the
> Tracking for 2.0 to 2.2 isn't working ... arrrghghgh. Any help would be n
ice
> ... documentation on this piece of it is seriously lacking.
> "swampthing" wrote:
>|||I finally resolved mine as well ... mine turned out to be an IIS
configuration issue ... something the installation should have taken care,
but didn't ... here is what needs to happen:
Make sure that the ASP directory is set as an Application directory. Open
up IIS Service Manager and navigate to the ASP directory. The ASP directory
is located at \MELL\ENG\Viewer\ASP. Right click the ASP directory and choos
e
Properties. On the Directory Tab under Application Settings there will be a
n
Application name entry. If this is grayed out click on the Create button
next to it and set it. OK out of ASP Properties. If it is not grayed out
and "asp" is in the space, then it is something else.
"swampthing" wrote:
[vbcol=seagreen]
> Hey guys,
> I resolved my problem with this issue. It turned out to be the sort order
of
> the SQL installation. We had installed SQL with a binary sort order becaus
e
> of a requirement of a third-party application. Because of this, I had issu
es
> with MELL, Diskeeper Administrator database, McAfee ePolicy Orchestrator
> database, etc., etc. I finally uninstalled everything, reinstalled SQL wit
h
> the default sort order and all the applications, including MELL, installed
> and worked correctly. So I would suggest looking at your database sort ord
er;
> you may need to change it for the MELL database and reinstall MELL.
> This was my solution and I'm not suggesting anyone else do the same, but i
t
> worked for me.
> "Craig French" wrote:
>