Image via Wikipedia

For developers who, like me, had set out on the wrong footing, the solution to the LOGON FAILED issue with Crystal Report in Visual Studio is non-trivial.

MSDN has comprehensive tutorials here - http://msdn.microsoft.com/en-us/library/ms225570.aspx .

All the best!

Q: I was not able to start the Oracle 11g Enterprise Manager service.

This happened after renaming my computer and although I reconfigured Oracle and my network settings (eg hosts file) for the new computer name it was not enough to get it working.

Basically, the Oracle Enterprise Manager service could not be started on the Windows Services management console. Alternatively, running ‘emctl start dbconsole’ on a command prompt did not do it either.

Checked for solutions on the Internet and found that several others had faced the same problem too.

A: Checking the log file OracleDBConsoleORCLsvc.log (in the oracle_home\computername\sysman\log directory) I found that Oracle had exited with a certain numeric exit code. The log further referred to the log file OracleDBConsoleorcl.nohup which contains a lot more detail on what happened.

In my case, the log file told me that the Java runtime could not find a particular directory (applib) and bombed the startup process. Finding a similar directory elsewhere (which actually contained another log file), I copied it over to where Oracle was looking for it, and this got the EM working again.

Lesson learnt: The OracleDBConsoleorcl.nohup log file contains a wealth of details about the Oracle Enterprise Manager service. It’s helpful to refer to it in solving problems of not being able to start the Oracle Enterprise Manager.

Related articles by Zemanta

Adoption of the right and relevant latest technologies is key to survival in the increasingly competitive world. Here’s a place to fast forward into the technological future:

Here are some short notes on how to use the .Net Repeater Control.

Templates

The Repeater Control consists of the following subcomponents:

• HeaderTemplate
• ItemTemplate
• AlternatingItemTemplate
• SeparatorTemplate
• Footer Template

Place codes and HTML elements in these templates to render complete DataRepeaters.

Binding Data

Data is bound through the DataSource property and the DataBind method. Valid data sources implement the ICollection, IEnumerable or IListSource interfaces.

Implementation

1. Add and configure a Data Source to the page
2. Add a DataRepeater Control to the page
3. Set the DataSource property of the Data Repeater Control to point to the Data Source
4. Add an ItemTemplate to the DataRepeater
   1. Add databound child controls (HTML markups or Server Controls) to the ItemTemplate
   2. Bind the child controls to the data using the Eval data-binding function

      <td><%#DataBinder.Eval(Container.DataItem, "DataItemName")%></td>

Here’s a quick note and reference point for programmers who are forgetful, like me.

All the Transact-SQL system functions @@IDENTITY, SCOPE_IDENTITY (which has no @@) and IDENT_CURRENT (also no @@) return the last auto-generated row identity  value. What’s the difference?

1. @@IDENTITY returns the last identity column value generated for any table during the current session regardless of whether the number was generated within the scope of the current stored procedure or not – Any table, current session, any scope

2. SCOPE_IDENTITY() returns the last identity column value generated for any table during the current session and within the current scope only – Any table, current session, current scope

3. IDENT_CURRENT(‘tablename’) returns the last identity column value auto-generated only for the current table regardless of session and scope – Current table, any session, any scope

I use SCOPE_IDENTITY to return identity values due to the following explanation from SQL Server 2008 Book Online -

“For example, there are two tables, T1 and T2, and an INSERT trigger is defined on T1. When a row is inserted to T1, the trigger fires and inserts a row in T2. This scenario illustrates two scopes: the insert on T1, and the insert on T2 by the trigger.

Assuming that both T1 and T2 have identity columns, @@IDENTITY and SCOPE_IDENTITY will return different values at the end of an INSERT statement on T1. @@IDENTITY will return the last identity column value inserted across any scope in the current session. This is the value inserted in T2. SCOPE_IDENTITY() will return the IDENTITY value inserted in T1. This was the last insert that occurred in the same scope. The SCOPE_IDENTITY() function will return the null value if the function is invoked before any INSERT statements into an identity column occur in the scope.”

Books Online further cautions that the value returned by these functions may be untrue if the INSERT operation has ended with an error -

“Failed statements and transactions can change the current identity for a table and create gaps in the identity column values. The identity value is never rolled back even though the transaction that tried to insert the value into the table is not committed. For example, if an INSERT statement fails because of an IGNORE_DUP_KEY violation, the current identity value for the table is still incremented. “

Powered by ScribeFire.

This is a tricky situation.The kind that we turn to runestones to unravel.

Problem - You can create a base User Control in a Windows Form project. Then, you can create another User Control that is inherited from the first quite easily by choosing Add New Item/Inherited User Control from your Solution Explorer (right click your project to get this menu). You cannot do the same for a Web User Control.

Now, why do you want to do this? Well, you’ll want to do this for the same reason you’ll want to create a base class in any other situation – you may wish to embed commonly used attributes and methods into the base class. Then, when you create sub-classes that inherit from it, you only need to write codes for pieces of specialized work that differ from the common functionalities.

Solution – The solution is actually quite simple. Follow these steps -

1. Create your base class in the App_Code folder (right-click App_Code folder, select to create a Class)
2. Ensure that your base class is implemented inside a namespace (begin the class declaration with a namespace.. statement and end it with an ..end namespace statement)
3. Create your sub class and inherit it from the base class (assuming that your sub-class is a visible Web User Control for a DotNetNuke module, right-click on the DesktopModules folder, then select to create a new Web User Control. After it has opened, modify the Class declaration code for the new We User Control by changing the … inherits clause).

I got this solution from a response to a question.

What do you do when you have a request for a new DNN module? These are my recommended first actions to take:

1. Get your basic DNN website running
2. Make sure your DotNetNuke Visual Studio solution can compile correctly
3. Create the Visual Studio directory framework for your new module
4. Right-click on your Website directory and choose new DotNetNuke Dynamic Module
5. Rename your App_Code and Desktop_Modules subdirectories
6. More here (a pretty good tutorial for creating modules in C#)
7. Create a basic test stub in your module. I recommend assessing a shared TEST table with some data in your DotNetNuke database. This forces you to
8. Create a Data Access test stub
9. Create a User Interface test stub
10. Define the new module on your DotNetNuke Host/Module definitions page
11. Run your test stubs in a page on your site

My recommendation is not to delay taking these steps even if you are busy. You are only ready to code when you have completed these steps properly. From my experience, when I delay taking these steps and the time to start coding creeps up on me, I find that sometimes I am taken by surprise that some of these things for the new modules do NOT work. Common problems, for some ghostly reason or another, are

1. The database tables mismatch against the ones in the Data Access codes
2. The DotNetNuke solution cannot be compiled (even though it used to be all okay!)
3. The new module cannot be placed on a page

And then I wish I had taken these assurances well in time.

checklist-initiating-dotnetnuke-module-project

Powered by ScribeFire.

You may wish to fully qualify all references to DataProvider in the Iframes module to DotNetNuke.Modules.IFrame.Data.DataProvider

These are unlike references to DataProvider in the other modules which refer to DotNetNuke.Data.DataProvider (in DNN 3.9 you may wish to fully qualify them as well for a successful compile).

You should successfully compile your DNN 3.9 website after making these changes:

Problem: I had this error compiling my DotNetNuke 3.9 website - The file 'x' and 'y' use a different language, which is not allowed since they need to be compiled together.

Solution: Here are instructions on how to add modules in non-VB languages to a DotNetNuke website, from the LinqThings4Sale tutorial

1. In the web.config file, add the line

<add directoryName="yourDirectoryName" /> to the section <codeSubDirectories>.

For example, the section in my web.config file looks like this

<!-- register your app_code subfolders to generate granular assemblies during compilation -->
      <codeSubDirectories>
        <add directoryName="LinqThings4Sale"/>
        <add directoryName="Template"/>
        <add directoryName="KLIMS"/>
        <add directoryName="CommonEntities"/>
        <add directoryName="Employment"/>
      </codeSubDirectories>

2. Then, refresh your App_Code folder. The folders added to the above section should now have changed folder icons to reflect that they are special folders.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Taskpool is a great, small application that helps you organize a to-do list and keep track of time spent on the to-do items. It runs on XULRunner, a revolutionary platform developed by the Mozilla community for executing lightweight XUL applications. See more sample XULRunner-based applications here.

Powered by ScribeFire.

Powered by ScribeFire.