MELL version 2.0

I have Microsoft eLearning Library Desktop Edition v2.0 installed on a web server. I can view the reports viewer without any error messages, but the database seems to be empty. It doesn't update the database when a user starts training. Any suggestions
?
Hi,
Would you please show me by what you are looking into the data in database?
You could open a Profiler to trace what MELL is doing with SQL Server. I
think the trace will help us much on determining whether the data is
available in database
Anyway, I am not an expert on MELL so that I will try to find some expert
on this to give you reply.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||It doesn't see the database at all. When I open the reports viewer which connects to the database, it says that the database doesn't exist, but it does.
""Mingqing Cheng [MSFT]"" wrote:

> Hi,
> Would you please show me by what you are looking into the data in database?
> You could open a Profiler to trace what MELL is doing with SQL Server. I
> think the trace will help us much on determining whether the data is
> available in database
> Anyway, I am not an expert on MELL so that I will try to find some expert
> on this to give you reply.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||Hi,
Here is the reply from specialist on MELL
===================================
It looks like this issue is related to the ASP application not being set.
If they are unable to get the Collections to show up under the
collections.asp page, and they are only getting certain reports in the
Reports Wizard. Here is how to set this:
1. Open up IIS Services Manager and navigate to the MELL directory.
2. Expand MELL, then ENG, then Viewer. You will see an ASP directory
3. Right click on the ASP directory and choose Properties
4. Under the first tab (Directory), and under the Applications settings
you will see Application Name which should be grayed out. Click Create to
set the ASP application. Select Apply and OK to exit the Properties page.
After doing this they should be able to navigate to
http://<servername>//mell/eng and see all Collections installed on the
machine. It should also fix the Reports page.
===================================
Would you please have a try on the steps above and then tell me whether it
works?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||I tried it and now it is saying that it can't connect to the MELL database.
Any suggestions?
""Mingqing Cheng [MSFT]"" wrote:

> Hi,
> Here is the reply from specialist on MELL
> ===================================
> It looks like this issue is related to the ASP application not being set.
> If they are unable to get the Collections to show up under the
> collections.asp page, and they are only getting certain reports in the
> Reports Wizard. Here is how to set this:
> 1. Open up IIS Services Manager and navigate to the MELL directory.
> 2. Expand MELL, then ENG, then Viewer. You will see an ASP directory
> 3. Right click on the ASP directory and choose Properties
> 4. Under the first tab (Directory), and under the Applications settings
> you will see Application Name which should be grayed out. Click Create to
> set the ASP application. Select Apply and OK to exit the Properties page.
> After doing this they should be able to navigate to
> http://<servername>//mell/eng and see all Collections installed on the
> machine. It should also fix the Reports page.
> ===================================
> Would you please have a try on the steps above and then tell me whether it
> works?
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>
>
|||Hi,
The most likely cause of this is that there is something wrong with the
File DSN. The username and password that were entered during setup must be
a SQL username and password, it can't be a Windows name (by default is asks
for SA)
If that is not the problem, then you need to manually edit the File DSN.
Windows 2000 and 2003 Server strip out the password in the File DSN which
breaks the connection. To correctly fix this problem, open the MELL File
DSN (mell2.dsn or mell25.dsn) manually with a text editor.
The default location of the File DSN is c:\\program files\common
files\odbc\data sources. You will notice the password is not included.
Edit the file so that it includes a password entry. The file should look
like this:
[ODBC]
DRIVER=SQL Server
UID=username
PWD=password
Network=DBMSLPCN
DATABASE=MELL
WSID=MELLSERVER
APP=Microsoft Open Database Connectivity
SERVER=MELLSERVER
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Ok, I can connect to the database now, but when I run any one of the reports,
I get this error:
ADODB.Recordset error '800a0bcd'
Either BOF or EOF is True, or the current record has been deleted. Requested
operation requires a current record.
Any Ideas?
""Mingqing Cheng [MSFT]"" wrote:

> Hi,
> The most likely cause of this is that there is something wrong with the
> File DSN. The username and password that were entered during setup must be
> a SQL username and password, it can't be a Windows name (by default is asks
> for SA)
> If that is not the problem, then you need to manually edit the File DSN.
> Windows 2000 and 2003 Server strip out the password in the File DSN which
> breaks the connection. To correctly fix this problem, open the MELL File
> DSN (mell2.dsn or mell25.dsn) manually with a text editor.
> The default location of the File DSN is c:\\program files\common
> files\odbc\data sources. You will notice the password is not included.
> Edit the file so that it includes a password entry. The file should look
> like this:
>
> [ODBC]
> DRIVER=SQL Server
> UID=username
> PWD=password
> Network=DBMSLPCN
> DATABASE=MELL
> WSID=MELLSERVER
> APP=Microsoft Open Database Connectivity
> SERVER=MELLSERVER
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>
>
>
|||Hi,
It seems the following documents would be a lot of help
FIX: Data Queries Sporadically Return Empty Recordsets
http://support.microsoft.com/?id=230101
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||I tried everything in this article, but without any success. Any ideas?
Thanks.
""Mingqing Cheng [MSFT]"" wrote:

> Hi,
> It seems the following documents would be a lot of help
> FIX: Data Queries Sporadically Return Empty Recordsets
> http://support.microsoft.com/?id=230101
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||Hi,
Have you contacted PSS for that hotfix? It will be a free case asking
hotfix.
If the hotfix doesn't resolve your issue, would you please take the
following steps gathering more information
1. Using Profiler tracing the SQL Server and be sure to include the events:
Errors and Warnings: Exception; Attention
TSQL: SQL:StmtStarting and Completed
Have them include all the data columns and make a note of the date/time
when they run the report and the hostname (machine name) from where they
are running the MELL Report so that it can traced back in the Profiler
trace for further investigation.
2. try to connect to the same instance of SQL Server and the database that
they are trying to connect via the report directly using isql or osql using
the same credentials as in the DSN from the *same* machine as the machine
from where they are running the report to see if
there is any problem on the SQL end. If they are able to connect just fine
using SQL tools, this indicates the problem might be on the
application-end, in which case you would have to work with a MELL expert to
troubleshoot further.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

MELL version 2.0

I have Microsoft eLearning Library Desktop Edition v2.0 installed on a web s
erver. I can view the reports viewer without any error messages, but the da
tabase seems to be empty. It doesn't update the database when a user starts
training. Any suggestions
?Hi,
Would you please show me by what you are looking into the data in database?
You could open a Profiler to trace what MELL is doing with SQL Server. I
think the trace will help us much on determining whether the data is
available in database
Anyway, I am not an expert on MELL so that I will try to find some expert
on this to give you reply.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||It doesn't see the database at all. When I open the reports viewer which co
nnects to the database, it says that the database doesn't exist, but it does
.
""Mingqing Cheng [MSFT]"" wrote:

> Hi,
> Would you please show me by what you are looking into the data in database
?
> You could open a Profiler to trace what MELL is doing with SQL Server. I
> think the trace will help us much on determining whether the data is
> available in database
> Anyway, I am not an expert on MELL so that I will try to find some expert
> on this to give you reply.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi,
Here is the reply from specialist on MELL
===================================
It looks like this issue is related to the ASP application not being set.
If they are unable to get the Collections to show up under the
collections.asp page, and they are only getting certain reports in the
Reports Wizard. Here is how to set this:
1. Open up IIS Services Manager and navigate to the MELL directory.
2. Expand MELL, then ENG, then Viewer. You will see an ASP directory
3. Right click on the ASP directory and choose Properties
4. Under the first tab (Directory), and under the Applications settings
you will see Application Name which should be grayed out. Click Create to
set the ASP application. Select Apply and OK to exit the Properties page.
After doing this they should be able to navigate to
http://<servername>//mell/eng and see all Collections installed on the
machine. It should also fix the Reports page.
===================================
Would you please have a try on the steps above and then tell me whether it
works?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I tried it and now it is saying that it can't connect to the MELL database.
Any suggestions?
""Mingqing Cheng [MSFT]"" wrote:

> Hi,
> Here is the reply from specialist on MELL
> ===================================
> It looks like this issue is related to the ASP application not being set.
> If they are unable to get the Collections to show up under the
> collections.asp page, and they are only getting certain reports in the
> Reports Wizard. Here is how to set this:
> 1. Open up IIS Services Manager and navigate to the MELL directory.
> 2. Expand MELL, then ENG, then Viewer. You will see an ASP directory
> 3. Right click on the ASP directory and choose Properties
> 4. Under the first tab (Directory), and under the Applications settings
> you will see Application Name which should be grayed out. Click Create to
> set the ASP application. Select Apply and OK to exit the Properties page.
> After doing this they should be able to navigate to
> http://<servername>//mell/eng and see all Collections installed on the
> machine. It should also fix the Reports page.
> ===================================
> Would you please have a try on the steps above and then tell me whether it
> works?
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>
>|||Hi,
The most likely cause of this is that there is something wrong with the
File DSN. The username and password that were entered during setup must be
a SQL username and password, it can't be a Windows name (by default is asks
for SA)
If that is not the problem, then you need to manually edit the File DSN.
Windows 2000 and 2003 Server strip out the password in the File DSN which
breaks the connection. To correctly fix this problem, open the MELL File
DSN (mell2.dsn or mell25.dsn) manually with a text editor.
The default location of the File DSN is c:\\program files\common
files\odbc\data sources. You will notice the password is not included.
Edit the file so that it includes a password entry. The file should look
like this:
[ODBC]
DRIVER=SQL Server
UID=username
PWD=password
Network=DBMSLPCN
DATABASE=MELL
WSID=MELLSERVER
APP=Microsoft Open Database Connectivity
SERVER=MELLSERVER
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Ok, I can connect to the database now, but when I run any one of the reports
,
I get this error:
ADODB.Recordset error '800a0bcd'
Either BOF or EOF is True, or the current record has been deleted. Requested
operation requires a current record.
Any Ideas?
""Mingqing Cheng [MSFT]"" wrote:

> Hi,
> The most likely cause of this is that there is something wrong with the
> File DSN. The username and password that were entered during setup must b
e
> a SQL username and password, it can't be a Windows name (by default is ask
s
> for SA)
> If that is not the problem, then you need to manually edit the File DSN.
> Windows 2000 and 2003 Server strip out the password in the File DSN which
> breaks the connection. To correctly fix this problem, open the MELL File
> DSN (mell2.dsn or mell25.dsn) manually with a text editor.
> The default location of the File DSN is c:\\program files\common
> files\odbc\data sources. You will notice the password is not included.
> Edit the file so that it includes a password entry. The file should look
> like this:
>
> [ODBC]
> DRIVER=SQL Server
> UID=username
> PWD=password
> Network=DBMSLPCN
> DATABASE=MELL
> WSID=MELLSERVER
> APP=Microsoft Open Database Connectivity
> SERVER=MELLSERVER
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>
>
>|||Hi,
It seems the following documents would be a lot of help
FIX: Data Queries Sporadically Return Empty Recordsets
http://support.microsoft.com/?id=230101
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I tried everything in this article, but without any success. Any ideas?
Thanks.
""Mingqing Cheng [MSFT]"" wrote:

> Hi,
> It seems the following documents would be a lot of help
> FIX: Data Queries Sporadically Return Empty Recordsets
> http://support.microsoft.com/?id=230101
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi,
Have you contacted PSS for that hotfix? It will be a free case asking
hotfix.
If the hotfix doesn't resolve your issue, would you please take the
following steps gathering more information
1. Using Profiler tracing the SQL Server and be sure to include the events:
Errors and Warnings: Exception; Attention
TSQL: SQL:StmtStarting and Completed
Have them include all the data columns and make a note of the date/time
when they run the report and the hostname (machine name) from where they
are running the MELL Report so that it can traced back in the Profiler
trace for further investigation.
2. try to connect to the same instance of SQL Server and the database that
they are trying to connect via the report directly using isql or osql using
the same credentials as in the DSN from the *same* machine as the machine
from where they are running the report to see if
there is any problem on the SQL end. If they are able to connect just fine
using SQL tools, this indicates the problem might be on the
application-end, in which case you would have to work with a MELL expert to
troubleshoot further.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!sql

MELL 2.5 Reports - Cannot Connect to a MELL database

Although the MELL content seems to be working properly, I'm receiving the
following error when attempting to load MELL reports at
http://<servername>/mell/eng/reports/
Could not connect to a MELL database
Microsoft? eLearning Library - Reports Viewer cannot query a MELL database.
This is due to the following:
The DSN pointing to the SQL server is missing from the web server.
The DSN on the web server contains incorrect logon credentials.
The SQL server being referenced does not contain a MELL database.
The SQL services on the SQL server being referenced are not started.
The SQL server being referenced is not available due to network outage or
other condition.
Please contact your network or training administrator.
My environment consists of these two servers:
[MellServer]
Windows 2003 Server, SP1
IIS 6.0
[MellDatabaseServer]
Windows 2000 Server
SQL Server 2000
My reasons for believing the listed causes are incorrect are:
The DSN pointing to the SQL server is missing from the web server.
-- I have a DSN on the web server that's pointing to the correct SQL server
The DSN on the web server contains incorrect logon credentials.
-- The DSN tests successfully
The SQL server being referenced does not contain a MELL database.
-- A database named MELL does exist and has populated tables
The SQL services on the SQL server being referenced are not started.
-- SQL services are started... DSN tests okay
The SQL server being referenced is not available due to network outage or
other condition.
-- Again, DSN tests okay. Plus, I can see a connection coming from the web
server in my netstat -a output.
Any help is greatly appreciated.
--SK--
Evidently my DSN file was not saving my password. If this is happening with
your MELL installation, check C:\Program Files\Common Files\ODBC\Data
Sources\mell25.dsn
Directly below the line beginning with "UID=", there should be a line that
reads:
PWD=yourpassword
If this line isn't present, add it.
Hope this helps someone else.
SK
--SK--
"ShaneK" wrote:

> Although the MELL content seems to be working properly, I'm receiving the
> following error when attempting to load MELL reports at
> http://<servername>/mell/eng/reports/
> Could not connect to a MELL database
> Microsoft? eLearning Library - Reports Viewer cannot query a MELL database.
> ----
> This is due to the following:
> The DSN pointing to the SQL server is missing from the web server.
> The DSN on the web server contains incorrect logon credentials.
> The SQL server being referenced does not contain a MELL database.
> The SQL services on the SQL server being referenced are not started.
> The SQL server being referenced is not available due to network outage or
> other condition.
> ----
> Please contact your network or training administrator.
> My environment consists of these two servers:
> [MellServer]
> Windows 2003 Server, SP1
> IIS 6.0
> [MellDatabaseServer]
> Windows 2000 Server
> SQL Server 2000
> My reasons for believing the listed causes are incorrect are:
> The DSN pointing to the SQL server is missing from the web server.
> -- I have a DSN on the web server that's pointing to the correct SQL server
> The DSN on the web server contains incorrect logon credentials.
> -- The DSN tests successfully
> The SQL server being referenced does not contain a MELL database.
> -- A database named MELL does exist and has populated tables
> The SQL services on the SQL server being referenced are not started.
> -- SQL services are started... DSN tests okay
> The SQL server being referenced is not available due to network outage or
> other condition.
> -- Again, DSN tests okay. Plus, I can see a connection coming from the web
> server in my netstat -a output.
> Any help is greatly appreciated.
> --
> --SK--
|||Did you ever get a response to the IP address showing in the report ? I went
through some similar SQL problems and was able to resolve them, but havent
found a thing on the reports showing IP address' (granted finding anything on
MELL has been tough)
"ShaneK" wrote:
[vbcol=seagreen]
> Glad to know this helped you!! Now, I'm only seeing IP addresses in the
> reports where I'd prefer to see the names of my Active Directory users. I've
> got a support case in progress with Microsoft and expect an answer this week.
> If you'd like to know how that one turns out let me know and I'll post a
> followup here.
> --
> --SK--
>
> "Erpara" wrote:

MELL 2.5 Reports - Cannot Connect to a MELL database

Although the MELL content seems to be working properly, I'm receiving the
following error when attempting to load MELL reports at
http://<servername>/mell/eng/reports/
Could not connect to a MELL database
Microsoft® eLearning Library - Reports Viewer cannot query a MELL database.
----
This is due to the following:
The DSN pointing to the SQL server is missing from the web server.
The DSN on the web server contains incorrect logon credentials.
The SQL server being referenced does not contain a MELL database.
The SQL services on the SQL server being referenced are not started.
The SQL server being referenced is not available due to network outage or
other condition.
----
Please contact your network or training administrator.
My environment consists of these two servers:
[MellServer]
Windows 2003 Server, SP1
IIS 6.0
[MellDatabaseServer]
Windows 2000 Server
SQL Server 2000
My reasons for believing the listed causes are incorrect are:
The DSN pointing to the SQL server is missing from the web server.
-- I have a DSN on the web server that's pointing to the correct SQL server
The DSN on the web server contains incorrect logon credentials.
-- The DSN tests successfully
The SQL server being referenced does not contain a MELL database.
-- A database named MELL does exist and has populated tables
The SQL services on the SQL server being referenced are not started.
-- SQL services are started... DSN tests okay
The SQL server being referenced is not available due to network outage or
other condition.
-- Again, DSN tests okay. Plus, I can see a connection coming from the web
server in my netstat -a output.
Any help is greatly appreciated.
--
--SK--Evidently my DSN file was not saving my password. If this is happening with
your MELL installation, check C:\Program Files\Common Files\ODBC\Data
Sources\mell25.dsn
Directly below the line beginning with "UID=", there should be a line that
reads:
PWD=yourpassword
If this line isn't present, add it.
Hope this helps someone else.
SK
--
--SK--
"ShaneK" wrote:
> Although the MELL content seems to be working properly, I'm receiving the
> following error when attempting to load MELL reports at
> http://<servername>/mell/eng/reports/
> Could not connect to a MELL database
> Microsoft® eLearning Library - Reports Viewer cannot query a MELL database.
> ----
> This is due to the following:
> The DSN pointing to the SQL server is missing from the web server.
> The DSN on the web server contains incorrect logon credentials.
> The SQL server being referenced does not contain a MELL database.
> The SQL services on the SQL server being referenced are not started.
> The SQL server being referenced is not available due to network outage or
> other condition.
> ----
> Please contact your network or training administrator.
> My environment consists of these two servers:
> [MellServer]
> Windows 2003 Server, SP1
> IIS 6.0
> [MellDatabaseServer]
> Windows 2000 Server
> SQL Server 2000
> My reasons for believing the listed causes are incorrect are:
> The DSN pointing to the SQL server is missing from the web server.
> -- I have a DSN on the web server that's pointing to the correct SQL server
> The DSN on the web server contains incorrect logon credentials.
> -- The DSN tests successfully
> The SQL server being referenced does not contain a MELL database.
> -- A database named MELL does exist and has populated tables
> The SQL services on the SQL server being referenced are not started.
> -- SQL services are started... DSN tests okay
> The SQL server being referenced is not available due to network outage or
> other condition.
> -- Again, DSN tests okay. Plus, I can see a connection coming from the web
> server in my netstat -a output.
> Any help is greatly appreciated.
> --
> --SK--|||Thank you so much for posting this! You've saved me a lot of heartache...
erpara
"ShaneK" wrote:
> Evidently my DSN file was not saving my password. If this is happening with
> your MELL installation, check C:\Program Files\Common Files\ODBC\Data
> Sources\mell25.dsn
> Directly below the line beginning with "UID=", there should be a line that
> reads:
> PWD=yourpassword
> If this line isn't present, add it.
> Hope this helps someone else.
> SK
> --
> --SK--
>
> "ShaneK" wrote:
> > Although the MELL content seems to be working properly, I'm receiving the
> > following error when attempting to load MELL reports at
> > http://<servername>/mell/eng/reports/
> >
> > Could not connect to a MELL database
> > Microsoft® eLearning Library - Reports Viewer cannot query a MELL database.
> > ----
> > This is due to the following:
> > The DSN pointing to the SQL server is missing from the web server.
> > The DSN on the web server contains incorrect logon credentials.
> > The SQL server being referenced does not contain a MELL database.
> > The SQL services on the SQL server being referenced are not started.
> > The SQL server being referenced is not available due to network outage or
> > other condition.
> > ----
> > Please contact your network or training administrator.
> >
> > My environment consists of these two servers:
> > [MellServer]
> > Windows 2003 Server, SP1
> > IIS 6.0
> >
> > [MellDatabaseServer]
> > Windows 2000 Server
> > SQL Server 2000
> >
> > My reasons for believing the listed causes are incorrect are:
> >
> > The DSN pointing to the SQL server is missing from the web server.
> > -- I have a DSN on the web server that's pointing to the correct SQL server
> >
> > The DSN on the web server contains incorrect logon credentials.
> > -- The DSN tests successfully
> >
> > The SQL server being referenced does not contain a MELL database.
> > -- A database named MELL does exist and has populated tables
> >
> > The SQL services on the SQL server being referenced are not started.
> > -- SQL services are started... DSN tests okay
> >
> > The SQL server being referenced is not available due to network outage or
> > other condition.
> > -- Again, DSN tests okay. Plus, I can see a connection coming from the web
> > server in my netstat -a output.
> >
> > Any help is greatly appreciated.
> > --
> > --SK--|||Glad to know this helped you!! Now, I'm only seeing IP addresses in the
reports where I'd prefer to see the names of my Active Directory users. I've
got a support case in progress with Microsoft and expect an answer this week.
If you'd like to know how that one turns out let me know and I'll post a
followup here.
--
--SK--
"Erpara" wrote:
> Thank you so much for posting this! You've saved me a lot of heartache...
> erpara
> "ShaneK" wrote:
> > Evidently my DSN file was not saving my password. If this is happening with
> > your MELL installation, check C:\Program Files\Common Files\ODBC\Data
> > Sources\mell25.dsn
> > Directly below the line beginning with "UID=", there should be a line that
> > reads:
> > PWD=yourpassword
> > If this line isn't present, add it.
> >
> > Hope this helps someone else.
> >
> > SK
> >
> > --
> > --SK--
> >
> >
> > "ShaneK" wrote:
> >
> > > Although the MELL content seems to be working properly, I'm receiving the
> > > following error when attempting to load MELL reports at
> > > http://<servername>/mell/eng/reports/
> > >
> > > Could not connect to a MELL database
> > > Microsoft® eLearning Library - Reports Viewer cannot query a MELL database.
> > > ----
> > > This is due to the following:
> > > The DSN pointing to the SQL server is missing from the web server.
> > > The DSN on the web server contains incorrect logon credentials.
> > > The SQL server being referenced does not contain a MELL database.
> > > The SQL services on the SQL server being referenced are not started.
> > > The SQL server being referenced is not available due to network outage or
> > > other condition.
> > > ----
> > > Please contact your network or training administrator.
> > >
> > > My environment consists of these two servers:
> > > [MellServer]
> > > Windows 2003 Server, SP1
> > > IIS 6.0
> > >
> > > [MellDatabaseServer]
> > > Windows 2000 Server
> > > SQL Server 2000
> > >
> > > My reasons for believing the listed causes are incorrect are:
> > >
> > > The DSN pointing to the SQL server is missing from the web server.
> > > -- I have a DSN on the web server that's pointing to the correct SQL server
> > >
> > > The DSN on the web server contains incorrect logon credentials.
> > > -- The DSN tests successfully
> > >
> > > The SQL server being referenced does not contain a MELL database.
> > > -- A database named MELL does exist and has populated tables
> > >
> > > The SQL services on the SQL server being referenced are not started.
> > > -- SQL services are started... DSN tests okay
> > >
> > > The SQL server being referenced is not available due to network outage or
> > > other condition.
> > > -- Again, DSN tests okay. Plus, I can see a connection coming from the web
> > > server in my netstat -a output.
> > >
> > > Any help is greatly appreciated.
> > > --
> > > --SK--|||Did you ever get a response to the IP address showing in the report ' I went
through some similar SQL problems and was able to resolve them, but havent
found a thing on the reports showing IP address' (granted finding anything on
MELL has been tough)
"ShaneK" wrote:
> Glad to know this helped you!! Now, I'm only seeing IP addresses in the
> reports where I'd prefer to see the names of my Active Directory users. I've
> got a support case in progress with Microsoft and expect an answer this week.
> If you'd like to know how that one turns out let me know and I'll post a
> followup here.
> --
> --SK--
>
> "Erpara" wrote:
> > Thank you so much for posting this! You've saved me a lot of heartache...
> >
> > erpara
> >
> > "ShaneK" wrote:
> >
> > > Evidently my DSN file was not saving my password. If this is happening with
> > > your MELL installation, check C:\Program Files\Common Files\ODBC\Data
> > > Sources\mell25.dsn
> > > Directly below the line beginning with "UID=", there should be a line that
> > > reads:
> > > PWD=yourpassword
> > > If this line isn't present, add it.
> > >
> > > Hope this helps someone else.
> > >
> > > SK
> > >
> > > --
> > > --SK--
> > >
> > >
> > > "ShaneK" wrote:
> > >
> > > > Although the MELL content seems to be working properly, I'm receiving the
> > > > following error when attempting to load MELL reports at
> > > > http://<servername>/mell/eng/reports/
> > > >
> > > > Could not connect to a MELL database
> > > > Microsoft® eLearning Library - Reports Viewer cannot query a MELL database.
> > > > ----
> > > > This is due to the following:
> > > > The DSN pointing to the SQL server is missing from the web server.
> > > > The DSN on the web server contains incorrect logon credentials.
> > > > The SQL server being referenced does not contain a MELL database.
> > > > The SQL services on the SQL server being referenced are not started.
> > > > The SQL server being referenced is not available due to network outage or
> > > > other condition.
> > > > ----
> > > > Please contact your network or training administrator.
> > > >
> > > > My environment consists of these two servers:
> > > > [MellServer]
> > > > Windows 2003 Server, SP1
> > > > IIS 6.0
> > > >
> > > > [MellDatabaseServer]
> > > > Windows 2000 Server
> > > > SQL Server 2000
> > > >
> > > > My reasons for believing the listed causes are incorrect are:
> > > >
> > > > The DSN pointing to the SQL server is missing from the web server.
> > > > -- I have a DSN on the web server that's pointing to the correct SQL server
> > > >
> > > > The DSN on the web server contains incorrect logon credentials.
> > > > -- The DSN tests successfully
> > > >
> > > > The SQL server being referenced does not contain a MELL database.
> > > > -- A database named MELL does exist and has populated tables
> > > >
> > > > The SQL services on the SQL server being referenced are not started.
> > > > -- SQL services are started... DSN tests okay
> > > >
> > > > The SQL server being referenced is not available due to network outage or
> > > > other condition.
> > > > -- Again, DSN tests okay. Plus, I can see a connection coming from the web
> > > > server in my netstat -a output.
> > > >
> > > > Any help is greatly appreciated.
> > > > --
> > > > --SK--

MELL 2.5 Reports - Cannot Connect to a MELL database

Although the MELL content seems to be working properly, I'm receiving the
following error when attempting to load MELL reports at
http://<servername>/mell/eng/reports/
Could not connect to a MELL database
Microsoft? eLearning Library - Reports Viewer cannot query a MELL database.
----
--
This is due to the following:
The DSN pointing to the SQL server is missing from the web server.
The DSN on the web server contains incorrect logon credentials.
The SQL server being referenced does not contain a MELL database.
The SQL services on the SQL server being referenced are not started.
The SQL server being referenced is not available due to network outage or
other condition.
----
--
Please contact your network or training administrator.
My environment consists of these two servers:
[MellServer]
Windows 2003 Server, SP1
IIS 6.0
[MellDatabaseServer]
Windows 2000 Server
SQL Server 2000
My reasons for believing the listed causes are incorrect are:
The DSN pointing to the SQL server is missing from the web server.
-- I have a DSN on the web server that's pointing to the correct SQL server
The DSN on the web server contains incorrect logon credentials.
-- The DSN tests successfully
The SQL server being referenced does not contain a MELL database.
-- A database named MELL does exist and has populated tables
The SQL services on the SQL server being referenced are not started.
-- SQL services are started... DSN tests okay
The SQL server being referenced is not available due to network outage or
other condition.
-- Again, DSN tests okay. Plus, I can see a connection coming from the web
server in my netstat -a output.
Any help is greatly appreciated.
--
--SK--Evidently my DSN file was not saving my password. If this is happening with
your MELL installation, check C:\Program Files\Common Files\ODBC\Data
Sources\mell25.dsn
Directly below the line beginning with "UID=", there should be a line that
reads:
PWD=yourpassword
If this line isn't present, add it.
Hope this helps someone else.
SK
--SK--
"ShaneK" wrote:

> Although the MELL content seems to be working properly, I'm receiving the
> following error when attempting to load MELL reports at
> http://<servername>/mell/eng/reports/
> Could not connect to a MELL database
> Microsoft? eLearning Library - Reports Viewer cannot query a MELL databas
e.
> ----
--
> This is due to the following:
> The DSN pointing to the SQL server is missing from the web server.
> The DSN on the web server contains incorrect logon credentials.
> The SQL server being referenced does not contain a MELL database.
> The SQL services on the SQL server being referenced are not started.
> The SQL server being referenced is not available due to network outage or
> other condition.
> ----
--
> Please contact your network or training administrator.
> My environment consists of these two servers:
> [MellServer]
> Windows 2003 Server, SP1
> IIS 6.0
> [MellDatabaseServer]
> Windows 2000 Server
> SQL Server 2000
> My reasons for believing the listed causes are incorrect are:
> The DSN pointing to the SQL server is missing from the web server.
> -- I have a DSN on the web server that's pointing to the correct SQL serve
r
> The DSN on the web server contains incorrect logon credentials.
> -- The DSN tests successfully
> The SQL server being referenced does not contain a MELL database.
> -- A database named MELL does exist and has populated tables
> The SQL services on the SQL server being referenced are not started.
> -- SQL services are started... DSN tests okay
> The SQL server being referenced is not available due to network outage or
> other condition.
> -- Again, DSN tests okay. Plus, I can see a connection coming from the we
b
> server in my netstat -a output.
> Any help is greatly appreciated.
> --
> --SK--|||Did you ever get a response to the IP address showing in the report ' I wen
t
through some similar SQL problems and was able to resolve them, but havent
found a thing on the reports showing IP address' (granted finding anything o
n
MELL has been tough)
"ShaneK" wrote:
[vbcol=seagreen]
> Glad to know this helped you!! Now, I'm only seeing IP addresses in the
> reports where I'd prefer to see the names of my Active Directory users. I
've
> got a support case in progress with Microsoft and expect an answer this we
ek.
> If you'd like to know how that one turns out let me know and I'll post a
> followup here.
> --
> --SK--
>
> "Erpara" wrote:
>

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:
>

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 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 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 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 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 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.|||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 at
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 except
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:
> 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:
> > If it helps swampthing I can confirm I too have the same problem. It is
> > preventing me from tracking MELL access.
> >
> >|||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 the
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 nice
... documentation on this piece of it is seriously lacking.
"swampthing" wrote:
> 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 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 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.|||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:
> 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 the
> 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 nice
> ... documentation on this piece of it is seriously lacking.
> "swampthing" wrote:
> > 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 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 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.|||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 choose
Properties. On the Directory Tab under Application Settings there will be an
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:
> 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:
> > 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 the
> > 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 nice
> > ... documentation on this piece of it is seriously lacking.
> >
> > "swampthing" wrote:
> >
> > > 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 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 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.sql

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 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 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 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 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 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.
|||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 at
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 except
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 the
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 nice
... documentation on this piece of it is seriously lacking.
"swampthing" wrote:

> 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 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 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.
|||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, doing
> each edition seperately, I thought I had done something wrong. I deleted the
> 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 nice
> ... 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 choose
Properties. On the Directory Tab under Application Settings there will be an
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 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: