Could not allocate space for object in database 'BizTalkMsgBoxDb

The following stored procedure call failed: " { call [dbo].[bts_InsertTrackingData]( ?, ?, ?, ?, ?, ?, ?, ?, ?)}". SQL Server returned error string: "Could not allocate space for object 'dbo.TrackingData_1_3'.'PK_TrackingData_1_3' in database 'BizTalkMsgBoxDb' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup."

The Messaging Engine failed while writing tracking information to the database. Details:"A database failure occurred due to an unexpected failure. ".

Could not allocate space for object 'dbo.TrackingData_1_0'.'PK_TrackingData_1_0' in database 'BizTalkMsgBoxDb' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

This error is very common and many times, I have seen affect of this error as Suspected Database, Database Operation Ceased, Database Stopped transactions. Solution to this error is simple but very important.

Fix/Solution/WorkAround:

1) If possible add more hard drive space either by removing of unnecessary files from hard drive or add new hard drive with larger size.

2) Check if the database is set to Autogrow on.

3) Check if the account which is trying to access the database has enough permission to perform operation.

4) Make sure that .mdf and .ldf file are not marked as read only on operating system file system level.

Export - Import Sharepoint List 2007

How to Import and Export SharePoint 2007 Task List with Attachments

 

SharePoint 2007 can be a monster to administer and if you have run into some of the weird issues that I have in the past few years you know what I am talking about. Well again I found a very simple thing that wasn't working within SharePoint 2007, I was trying to move a Task List from one SharePoint 2007 website to another and it wouldn't export the Task List and import it just fine but the problem was it wouldn't move the attachments with the Task List. So I started trying to find a method to make this work and found a great STSADM command that would do it but ran into some other problems. The STSADM command I found was a great little tool that was written by someone very smart but they don't explain how to actually use the command. So in this guide I will walk you through the STSADM command and ALL of the steps to get it to work.

So first the commands you will run are simple STSADM commands on your SharePoint 2007 server. To run these commands you have to be an admin on the server and an admin for the sites you are exporting and importing the Task List to. There are two commands you will use they are listed below:

Export Command

stsadm -o gl-exportlist -url "http://yoursite/Documents/TaskList/AllItems.aspx" -filename "c:\docs" -includeusersecurity -versions 4 -nofilecompression

Import Command

stsadm -o gl-importlist -url "http://yoursite/" -filename "c:\docs" -includeusersecurity -updateversions 2 -nofilecompression -retargetlinks -sourceurl http://yoursite/Documents/TaskList/AllItems.aspx

You of course have to change the URLS to match your sites and the file names and locations to where you want to save the file. These two commands work perfectly to move a task list from one site to another; you can even move them cross domain or from one farm to another. The only catch is you have to install a WSP file that was written to make these two commands work. Without installing the WSP files these two commands do nothing other than come back with an error. The WSP file you have to install is just an extension of the STSADM commands that was written specifically for these two commands.

So to download and install the WSP file so that you can use the commands to move the Task List and attachments follow these steps:

Download the WSP file HERE

Put the file on the server you want to deploy the solution on (the server where the task list is located)

Open a command prompt to STSADM (I wrote an article how to add STSADM to your path, it might help)

Run the command stsadm -o addsolution -filename Lapointe.SharePoint.STSADM.Commands.wsp (make sure you are in the directory where you put the WSP file on the server, in my case C:\test)

Run the command stsadm -o deploysolution -name Lapointe.SharePoint.STSADM.Commands.wsp -immediate -allowgacdeployment

Run the command stsadm -o execadmsvcjobs

Once you have completed the commands and it didn't throw any errors then you are now ready to run the commands to export your Task List. To do this, follow these steps:

Login to the server you need to export the task list from (should be same server you just deployed the WSP file to)

Open a command prompt to STSADM (I wrote an article how to add STSADM to your path, it might help)

Run the command stsadm -o gl-exportlist -url "http://yoursite/Documents/TaskList/AllItems.aspx" -filename "c:\docs" -includeusersecurity -versions 4 -nofilecompression

Now if this completed with no errors you should be able to go to the file location C:\docs and see all of the files for the task list. Now you can go to any SharePoint Farm in any environment and import this task list with all of its attachments. Remember if you are importing the Task List to a different server you have to run through the install of the WSP file again on the new server before you can import the Task List and its attachments.

To import the task list follow these steps:

First if it's a new server make sure you go back through the WSP install steps above

Copy the files from where ever you exported the list ("C:\docs" was my example) to the new server

Open a command prompt to STSADM (I wrote an article how to add STSADM to your path, it might help)

Run the command stsadm -o gl-importlist -url "http://yoursite/" -filename "c:\docs" -includeusersecurity -updateversions 2 -nofilecompression -retargetlinks -sourceurl http://yoursite/Documents/TaskList/AllItems.aspx

Now you can go to the site where you imported the task list and all of your tasks should be there and more importantly all of your attachments will be there as well. I hope this guide helps you to get around the issue of exporting and importing Task Lists where the attachments don't import/export properly.

Ref : http://voices.yahoo.com/how-import-export-sharepoint-7367026.html

Enabling change password in OBIEE 10g

Enabling change password in OBIEE 10g

To enable this option we have to do a small workaround.


Go the OBIEE Installed BI folder and open the Controlmessages.xml. In my case the path is like below:


    C:\OracleBI\web\msgdb\messages\controlmessages.xml


Once you opened the file, you will get the message like below picture.


Just remove the command tag which indicated in the red rectangle in the screen shot to enable the 'Change Password' Option and save the file and restart the Oracle Java Host, Oracle BI Server and Oracle BI Presentation Server. 

Now you login to presentation services and Go to My Account. You can see the 'Change Password' option available there. By clicking that we can change the password. 

----------------------------------------------------------------

Replace the line

<WebMessage name=”kmsgChangePasswordLink”><!–<HTML><a insert=”1″><sawm:messageRef name=”kmsgUIChangePassword”/></a></HTML>–></WebMessage>

*** WITH:

<WebMessage name=”kmsgChangePasswordLink”><HTML><a insert=”1″><sawm:messageRef name=”kmsgUIChangePassword”/></a></HTML></WebMessage>

This requires restarting the BI server, After restarting the BI server successfully, users should be able to see the “Change Password” link on their OBIEE My Account page.

But it wont work in obiee11g kindly refer the below reason:

The ability to change password is not possible in OBIEE11g. With 11g, OBIEE essentially uses the 10g notion of external authentication. By default, this is the WLS (Weblogic)LDAP identity store, but may be any defined Authenticator either within WLS, or in the OBIS metadata (i.e. Custom Authenticator or LDAP). As such, OBIEE proper no longer has any control over user passwords - this is why the steps referenced in Doc ID 1102353.1do not apply to 11g OBIEE

See Change Passsword Link In Answers/Dashboard Obiee 11g (Doc ID 1302091.1)

OBIEE 11g : (Workaround Method from Venkat Blog)

http://www.rittmanmead.com/2011/10/changing-your-password-in-obiee-11g/

500 Internal Server Error .Too many open files....

500 Internal Server Error . Client was getting following error while accessing the form application.

 The OC4J log file shows

formsweb: Servlet error  Or web: Servlet error

java.io.IOException: Too many open files

Cause
On Windows systems , there is a limit to the number of files that can be simultaneously opened : about 2000.
This limit applies to all the servlets running in the OC4J_BI_Forms : The forms Servlets and the Reports Servlets. 
Solution
To increase the parameter numprocs for the OC4J_BI_Forms : 

1. Edit the file ORACLE_HOME\opmn\conf\opmn.xml 

2. Locate the following lines :
....
process-type id="OC4J_BI_Forms" module-id="OC4J">
....
process-set id="default_island" numprocs="1"/>
/process-type>
.....


3. Replace :
numprocs="1"
by
numprocs="2"

4. Execute the command : 
$ORACLE_HOME/bin/opmnctl reload 
in order to reload the file opmn.xml

The modification will be taken into account the next time the OC4J_BI_Forms will be restarted.

When numprocs > 1 , several processes will be started for the OC4J OC4J_BI_Forms. It means that the requests will be "load-balanced" between the 2 processes.
So, the number of files opened will be divided by 2 (if numprocs=2) and the limit will no more be reached.

My experience with the Installation of SQL Server 2005 on Windows Server 2008

As part of the SQL upgrade process i had to create an alternate setup for SQL Server on Windows Server 2008 . I had two choices
option1: install SQL Server 2005 Enterprise on windows Server 2008 R2 Standard
option2: install SQL Server 2008 Enterprise R2 on Windows Server 2008 R2 Standard
i choose option1 as i wanted to test the upgrade process to SQL Server 2008 later
so i started the installation of SQL Server 2005, during system configuration check i got the warning
-----------
IIS Feature Requirement (Warning) :

Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.

For installation IIS on Windows 2008 follow the article
http://support.microsoft.com/kb/920201/en-us and http://learn.iis.net/page.aspx/29/installing-iis-7-on-windows-server-2008-or-windows-server-2008-r2/
another reference http://blogs.technet.com/b/seanearp/archive/2008/07/01/installing-sql-server-2005-on-windows-server-2008.aspx
--------------
you can ignore the warning as IIS is required only for reporting services.the reason is because Windows Server 2008 have just been released and the operating system information on the page is not fully up to date .

According to Microsoft, SQL Server 2005 requires Microsoft SQL Server 2005 Service Pack 2 (SP2) to run on Windows Server 2008 and Windows Vista SP1. And the full release version of SQL Server 2005 has to be first installed before the SP2 can be applied.

After the successfull installation of SQL Server 2005 , i was able to install SP1 got a warning for analysis services to install hotfix 2047. i didnot do that as i am on the way to install SP2, hoping it will remove the warning. as expected the installation was successfull without any warning. did the SQL provisioning and restarted the server.so far good. tried to open database with SQL Server management studio, there comes the error. No instance, No database is shown. checked with ODBC data source database and instance exist.

followed the article http://decoding.wordpress.com/2008/04/18/how-to-install-sql-server-2005-on-windows-server-2008/
downloaded the hotfix from http://support.microsoft.com/kb/950636
no luck.got the message the update is not applicable to your computer .
installed the backup feature still the same error.
now the next option for me is to do an upgrade to sql server 2008 r2. the upgrade advisor tells me no reporting services is installed. ofcourse its not. will do it later.now continuing with upgrade.upgrade was successfull. but the sql server management studio cannot find the instances.

Now i did not want to spent more time on this process . so removed all installation of SQL 2005 and SQl 2008 and went for the option2. to those who don't have option2 can check the below reference as well

List of known issues when you install SQL Server 2005 on Windows Server 2008 :
http://support.microsoft.com/kb/936302

Open Task Manager on Remote Desktop

recently i was stuck with a problem on remote desktop that the programs are hanged and i cannot click on anything, task manager is not accessible to end the processes. now how to open task manager in a remote desktop. if you can't do it then you haveto login to the remote machine locally or restart the machine manually. this is not a good option

so here is a command to open the task manager on remote desktop

CTRL+SHIFT+ESC - work same as right click taskbar and open task manager
CTRL+ALT+END - work same as CTRL+ALT+DEL

guess this post was useful!!

Login problem with MSDE

recently i came across a problem with MSDE (Microsft SQL Server Desktop engine) which gets installed mostly with third party software which do not require Standard SQL Server.

MSDE does not have its own user interface as it is primarily designed to run in the background.Users interact with MSDE through the program in which it is embedded. The only tool that is provided with MSDE is the osql utility. The executable file, osql.exe, for me is located in the C:\Program Files\Microsoft SQL Server\80\Tools\Binn\osql.exe

more information about osql.exe utility is available at
http://support.microsoft.com/kb/325003
http://support.microsoft.com/kb/325022
now the problem where i have to dig in is when my program which i downloaded was asking for a database username/password which i never entered during installation. i am able to see MSDE is started from the icon on the right hand side of the windows taskbar.but what is the username and password to connect to MSDE and how to connect to. once the program prompted for username as 'sa' .

to reset the password for user 'sa' since you have no idea about password, there is a way with osql utility.
go to start-run and type osql -U sa (here you are trying to connect to MSDE with username sa) and press enter. the command prompt for password .
do not type anything -----press enter (you came to know password is null for sa at this point)
to reset password type sp_password null 'yournewpassword','sa' ----press enter
type go -----press enter.you get a message Password chnaged
now you can use the sa/yournewpassword to connect from your application or from osql.exe