Friday, March 23, 2012

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!

No comments:

Post a Comment