Dev Team Assemble » Configuration

JDE BSSV Won’t Build…after package update…ummmm what?

Calvin — Mon, 06 Feb 2012 18:42:57 +0000

I have been working with jDeveloper and JDE (J.D.Edwards) for a little while. Mostly to build integration pieces for portals and custom applications. One of the strangest things happened to me after I did a package update (upgrade to local JDE application) the other day.

After the package update, I grabbed my project code from the OMW (object management workbench) and tried to go back to development. All of a sudden it had replaced my ValueObject classes with generated classes ( really...I have no idea why) and copied some other strange code articles to my computer.

This was really strange but good thing I managed to backup my code using an alternative source code control system just in case something bizarre like this happened....which of course it did. I copied my code back over the top of the JDE code and all was well, with the exception of some oracle.e1.bssvfoundation classes not working correctly (complaining that the method could not be found, etc). In order to build my code I needed to remove some new code (that showed up during the package build) in the c:\e812\dv812\java\source\oracle\e1\bssvfoundation folder. I think its safe to say you can delete that entire folder because it should not exist in your source code folder.

To try and make a confusing story short and understandable I guess what I am trying to say if you find that you have the folder c:\e812\dv812\java\source\oracle\e1\bssvfoundation you can delete it because you probably shouldn't have it....these are system functions that you don't need the source for, and chances are if you do have the source its not the right version :s. I am not sure why they are included in our package but they are.

If your still with me then I hope this helped...if you are confused then drop me a line and I will attempt to explain by adding more acronyms and file paths.

Calvin

Technorati Tags: J.D.E., JD Edwards, JDE, jDeveloper

SQL Server Recovery Model – Modification Script

Calvin — Thu, 20 Oct 2011 15:59:41 +0000

I often find in my sharepoint development environments that I have issues with transaction logs filling up. This gives me the "Error" page with no indication of what the problem is...yes I can go and change the tag to set the customer errors mode to off and add the callstack to the page but it still doesn't address the problem. I whipped this script up because the dev sql server we are using has well over a hundred db's on it and I didn't fell like manually typing the ALTER DATABASE [xxx] SET RECOVERY SIMPLE for each one or doing the clickity click thing either. Now the solution below probably breaks lots of best practices and such but it works for what I wanted it to do....which is modify all existing db's recovery mode. To modify new db's recovery mode, just set the model db's option to simple and voila..you are ready to go.

Quick note: YOU PROBABLY DO NOT WANT TO EVER...I MEAN EVER...USE THIS ON A PRODUCTION SYSTEM.

*/


	Modify th recovery model for all databases on your server
*/
	DECLARE @lasterror int
	DECLARE @sql nvarchar(max)
	DECLARE @dbname nvarchar(100)
	DECLARE @dbid int
	DECLARE @recModel int
	-- cycle the log
	exec sp_cycle_errorlog 
	CREATE Table #dbInfo
	(
		database_id int NOT NULL,
		dbName nvarchar(100) NOT NULL,
		recoveryModel int
	)
	--SELECT database_id, [name], recovery_model FROM sys.databases order by database_id
	SELECT TOP 1 @dbid = database_id FROM sys.databases where database_id > 4  ORDER BY database_id asc;
	SELECT @dbname = [name] FROM sys.databases where database_id = @dbid;
	SELECT @recModel = recovery_model FROM sys.databases where database_id = @dbid;
	-- begin backup process
	WHILE @dbid > 0
	BEGIN
		INSERT INTO #dbInfo (database_id, dbName, recoveryModel) VALUES (@dbid, @dbname, @recModel);
		IF @recModel = 1
		BEGIN
			SELECT @sql = 'ALTER DATABASE [' + @dbname + '] SET RECOVERY SIMPLE'
			EXEC sp_executesql @sql
			SELECT @lasterror = @@ERROR
			IF @lasterror <> 0
				-- log the error to the message console
				PRINT 'ERROR: Changing the recovery mode for database : ' + @dbname + ' with error number ' + CAST(@lasterror as nvarchar(25))
			ELSE
				PRINT 'Recovery mode changed to simple (3) for database : ' + @dbname
		END
		-- get a new record
		SELECT @dbid = 0;
		SELECT TOP 1 @dbid =  database_id FROM sys.databases where database_id > 4 and
			database_id NOT IN (SELECT DISTINCT x.database_id FROM #dbInfo x);
		SELECT @dbname = [name] FROM sys.databases where database_id = @dbid;
		SELECT @recModel = recovery_model FROM sys.databases where database_id = @dbid;
	END	
	DROP Table #dbInfo
	SELECT database_id, [name], recovery_model FROM sys.databases order by database_id
	GO

Technorati Tags: Configuration, Development, moss 2007, SharePoint, SQL Server

SharePoint 2007 FBA- Upload Mutiple Documents Missing From Menu

Calvin — Mon, 17 Oct 2011 15:14:40 +0000

Scenario: Forms Based Authentication on an external facing portal. Users are having trouble (as in not able too) uploading multiple documents at once.

This was a pretty easy fix....Enable Client Integration for the given website zone in Central Administration.

Technorati Tags: Configuration, FBA, moss 2007, SharePoint

Windows 2008 Server GPO – Force Allow Remote Desktop Connections

Calvin — Wed, 29 Sep 2010 18:00:07 +0000

Neat thing I figured out today...which I am 100% certain I will forget...to force allow remote desktop connections on a windows 2008 domain you need to set the following

Set windows Firewall to have a exception for the remote connection : computer >> admin templates >> network >> network connections >> windows firewall >> domain profile >> windows firewall: allow inbound remote desktop exceptions
Set the remote desktop services to allow connections: : computer >> admin templates >> windows components >> remote desktop services >> remote desktop session host >> connections >> Allow users to connect remotely using remote desktop services

Technorati Tags: Configuration, GPO, group policy, remote desktop, Security, Windows, windows 2008 r2

Help My Content Database is gone!!! – SharePoint Versions are Wrong

Calvin — Tue, 28 Sep 2010 13:20:06 +0000

So I was trying to restore a content db from production into my dev box the other day and got the following error:

Your backup is from a different version of Windows SharePoint Services and cannot be restored to a server running the current version. The backup file should be restored to a server with version '12.0.0.6510'

Ahh ok...so my dev box is out of sync no biggie, it was't a real pressing update anyway. So I figured I would go back to my site to finish up some dev tasks and to my dismay....the site was gone. Ummmm...hello?!?!?!

Turns out, the restore process (via 'stsadm -o restore -url http://omg.net -filename c:\arrggggh.bak') wipes out your content db. Great so now I HAVE to update my dev box to the version of the production server (which isn't a bad idea...just rather make that choice myself!).

Here is a great resource for figuring out which updates you need:

http://sharepointadminwiki.com/display/SharePointAdministrationWiki/SharePoint+Versions

To determine your version of SharePoint go to Central Admin > Operation > Servers in Farm

HTH

Technorati Tags: Content Database, SharePoint, Version

SharePoint, Webservices and URL Rewrite…

Calvin — Wed, 28 Jul 2010 12:55:01 +0000

So I was having a strange problem in SharePoint the other day trying to run a webservice from a client script. Every time I called the service (in this case and .asmx in the layouts dir) it was doing nothing...no communication at all with the service. What made this particularly strange is that this exact same setup was working fine for everyone else in my team...figures.

When I ran the web methods from the service page itself (which loaded just fine) I got the following error : Request format is unrecognized for URL unexpectedly ending in '/[webmethod_name]'. Didn't make sense...I checked my web configuration and compared it against the other people in my team and all was well. I tried following Microsoft's recommendation of adding the following snippet to the system.web section of the config file.

<webServices>
<protocols>
<add name="HttpGet"/>
<add name="HttpPost"/>
protocols>
webServices>

All the above did was give me a 500 error.

After spending waaaaaaaaay to much time on the problem...a colleague of mine and I finally discovered that it was due to the Lower case rewrite inbound rule (converts the entire address to lower case). Apparently webmethod names are case sensitive in the address bar (this was not a SharePoint problem)...the documentation is here on msdn: http://msdn.microsoft.com/en-us/library/0c515353(VS.71).aspx

So turning off the rule and everything started to work again.

Technorati Tags: SharePoint, url rewriter, WebServices

Great Post on ASP.NET Caching

Calvin — Wed, 14 Apr 2010 13:46:12 +0000

I came across a great post today that talks about ASP.NET caching (applies to SharePoint) and what to look for. Thanks to Gunnar Peipman for the great insight.

http://weblogs.asp.net/gunnarpeipman/archive/2010/04/02/measuring-asp-net-and-sharepoint-output-cache.aspx

Basically you need to setup the following performance counters in windows:

Total number of objects added
Total object discards
Cache hit count
Cache hit ratio

Technorati Tags: ASP.NET, IIS, Windows, windows 2008 r2

SharePoint 2007 on Windows 2008 R2 x64

Calvin — Tue, 01 Dec 2009 16:11:00 +0000

I was trying to install install SharePoint 2007 onto Windows 2008 r2 and was getting a strange error referencing KB article 962935. Funny enough this article is not live yet so it left me a little unhappy. Apprarently Microsoft does not support the distributed SP1 installation package of SharePoint for this version of the OS. Turns out Jei Li posting on his msdn blog detailing how to go about creating a slipstreamed installation for SP2 on this server Click here for the article. Basically the steps are (pretty much word for word from Jei Li's blog):

Install .Net Framework 3.5 SP1 in the features applet
Copy the installtion media contents to a folder on the computer (c:\install)
Download the WSS x64 SP package and the MOSS 2007 SP2 x64
Delete everything inside Updates folder in the install folder you setup.
Open a command prompt, change directory to the folder you put the downloaded patches, and run the following two commands:
- wssv3sp2-kb953338-x64-fullfile-en-us.exe /extract:[Path to installation bits]\Updates /quiet
- officeserver2007sp2-kb953334-x64-fullfile-en-us.exe /extract: [Path to installation bits]\Updates /quiet
Delete the wsssetup.dll filein the updates dir. This is a very important step so please don’t miss it.
If you also need the Cumulative Updates to be applied when install SharePoint, download the latest Windows SharePoint Services 3.0 and SharePoint Server 2007 Cumulative Update packages and extract them into Updates folder like step 4.
Your slipstream build of SharePoint Server 2007 is done!
Go and install it on your Windows Server 2008 R2 box, after the installation, the site version will show 12.0.0.6421 or possibly a higher version.

Please reference Jei Li's post for furthur instuctions. I only posted all the steps here because things have a mysterious way of dissappearing or not appearing at all on Microsofts site.

After doing all of this everything seems to be fine...seems to be

Links

Technorati Tags: Configuration, server, SharePoint, Windows, windows 2008 r2, x64

Building an ESXi 4 Virtual Environment with SSH enabled

Calvin — Thu, 19 Nov 2009 05:11:13 +0000

So a little while ago I was playing around with building a virtual environment using Windows 2008 Hyper-V and while this was an interesting experience I found Microsoft's lack of any Linux distro support beyond the SUSE to be a bit of a pain. That being said I wanted to increase the resources available on my Dell PowerEdge server and thought I would take this opportunity to rebuld it before I get started on building out a SharePoint 2010 beta 2 testing farm....whew, try saying that 10 times fast

I downloaded and installed the new VMWare ESXi 4. It looks like they are really streamlining this technology with the vSphere platform...blah blah blah means they are the same product with license key feature unlocks (from what I understand of it anyways). Not surprisingly this was a lightning fast install. I did have a couple of hiccups trying to figure out a) where to put my free license key in and b) getting SSH enabled.

License Key - like most normal people I thought that after installing the vsphere client onto my desktop that there would be a little section in the help menu for adding license keys (like most software). Turns out you need to click on the host, then the configuration tab and then the Licensed Features option under Software. (OK ... umm forgot to mention...click the edit button on the right hand side!!)

SSH - enabling this took some digging. Not much mind you because there are actual quite a few people out there writing about the same thing... here are a couple that I found:

I don't want to rehash it but here are the steps (in case they take down their postings!)

At the ESXi console ALT+F1 for new session at the console screen
enter the command "unsupported" and type your password
use vi to edit the inetd.conf file so type...vi /etc/inetd.conf
scroll to the areas where ssh is listed and remove the # sign (delete key works!)
type :wq to exit vi and save your changes
restart the server OR do the killing of the process number for inetd and using the correct switches (i just rebooted because I dont care that much

And after the machine comes back up you should be able to connect via Putty or whatever tool you are using no problem.

Technorati Tags: ESXi 4, virtualization, VMWare

Variations Failed: An error was encountered performing this operation. You may re-try the operation…

Calvin — Fri, 30 Oct 2009 20:16:27 +0000

So I got this error the other day when putting together a dev site collection usign varations:

An error was encountered performing this operation. You may re-try the operation, and you may need to clean up the half-created data first before re-trying. If the problem persists, please contact your system administrator

This was actually a fairly easy fix for me. I simply had to enable the publishing features in my site. Which is funny...because they should have been on but I must have overlooked that.

Technorati Tags: Configuration, error, moss 2007, SharePoint, variations