Search This Blog

Thursday, September 19, 2013

Creating a Jenkins Build machine


Recently, I had to recreate a Jenkins build server due to a hardware failure.
The process was straightforward but not without issues...


VM started with
WIN2008 R2 server
VS 2010 Pro

Software to be installed:
1) TortoiseSVN 1.7.6, Build 22632 - 64 Bit , 2012/03/08 18:29:39
2) Winrar - wrar420.exe
3) Jenkins 1.531 from  http://jenkins-ci.org/


Steps:
1) Installed TortoiseSVN
2) Pulled local project code in SVN down
3) Install ASP.net/MVC3 (its a MVC3 ASP.NET App)
4) Install IIS 6 Metabase and IIS 6 Configuration Compatibility
         (Needed to for 3 projects in the solution)
        http://technet.microsoft.com/en-us/library/bb397374(v=exchg.80).aspx
5) Install WIF files (Windows Identity Foundation) (used by the project)
a. Windows6.1-KB974405-x64
b. WindowsIdentityFoundation-SDK-4.0
6) Install Jenkins 1.531.
a. Add Text Finder Plugin to Jenkins install.
b. Downgrade SVN plugin to version 1.45
c. Install Active Directory Plugin
d. Give anonymous read access
e. Define other users.
f. Add SVN login as /
g. Manually added subversion.credentials file to 'My Project' task folder  and restarted jenkins
C:\Program Files (x86)\Jenkins\jobs\My Project

7) Turn firewall off.

Issues entered:
1) VS 2012 cannot be used to build 'My Project' .
a. Solution contains is a .net deployment project which is no longer supported by current versions of Visual Studio.  Last supported in VS2010 
b. Had to uninstallVS2012 Pro and install VS2010 Pro
2) After configuring Jenkins and confirming that project code could be fetched from SVN locally on the build server and manually compiled, attempts to set user credentials for SVN resulted in failure: with code SVN E175002
a. Manually added subversion.credentials file to 'My project folder task folder and restarted jenkins

C:\Program Files (x86)\Jenkins\jobs\My Project

Thursday, August 8, 2013

Link servers from SQL 2008 R2 to SQL 2000 (32bit)


Solutiion is from http://sqlblog.com/blogs/roman_rehak/archive/2009/05/10/issue-with-64-bit-sql-server-using-sql-2000-linked-server.aspx


Issue with 64-bit SQL Server using SQL 2000 linked server

Recently we started adding SQL Server 2008 64-bit servers to our production set and we ran into the following issue. When we ran queries on a linked 2000 server, we were getting the following error:
OLE DB provider "SQLNCLI10" for linked server "XXXXXX" returned message "The stored procedure required to complete this operation could not be found on the server. Please contact your system administrator.".
Msg 7311, Level 16, State 2, Line 1
Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO" for OLE DB provider "SQLNCLI10" for linked server "XXXXXX". The provider supports the interface, but returns a failure code when it is used.

This article from MS website describes the issue pretty well, although it says the issue applies to 2005 but we are using 2008. As suggested, we ran the Instcat.sql file on our development system first, and we ended up getting errrors left and right, so we didn't dare to run it on our main production server. In the end, this workaround worked for us - we needed to create a procedure in the master database on the linked 2000 server. The proc is called sp_tables_info_rowset_64 and it is needed because it is called by 64-bit servers when running remote queries.
 Here is the text of the proc in case you ever need to do the same, create it in the master database:
create procedure sp_tables_info_rowset_64
      @table_name sysname,
      @table_schema     sysname = null,  
      @table_type nvarchar(255) = null
as
  declare @Result int set @Result = 0
  exec @Result = sp_tables_info_rowset @table_name, @table_schema, @table_type
go

Wednesday, June 19, 2013

Checking your outgoing mail server (Is Port 25 blocked?)

Checking your outgoing mail server (Is Port 25 blocked?):

'via Blog this

In a comment Prompt:
telnet example.com 25

or

telnet example.com 587


If unblocked...
220 cl34.gs01.gridserver.com ESMTP Exim 4.63 Tue, 24 Jun 2008 13:45:04 -0700
If blocked...
Trying 64.13.192.208... telnet: connect to address 64.13.192.208: Connection refused telnet: Unable to connect to remote host

Saturday, June 8, 2013

Two questions about the modern Internet?

Why does every browser now hate the Home button?

  - I know why Google hates the home button by why does everyone else follow suit. Too bad, Chrome on many levels is a the best browser out there but Google's business models will eventually render Chrome useless.

   - Mozilla thinks they are smarter than everyone or they are smoking alot of something during UI design sessions.

    - Apple who cares... the moment a major browser release broken basic http authentication I was done.  Apple almost had to produce the iPhone and iPad because no one in their right minds would say I want to develop a web app for Safari.

 - Microsoft - IE9/10 does not suck. But still IE has its challenges, try create ASP.NET/MVC app that shows embedded PDFs also use html dialogs watch the job of staying in focus.  Opposite behavior of everyone else.  

Why can't I find a file sharing site allows me to share a file with URL and then allow the file to be downloaded with a simple WebClient?

  - Skydrive - No.  I tried to use SkyDrive 5 years ago. No Published API at the time, constant UI changes, and file linking schemes.

  - DropBox - You think so...  until some actually uses the link.  DropBox, you're done you just don't know it yet.

  - All of the various sites hosted for nefarious but legal file sharing....
 I just can't do it...  

A thief is always a liar first...Can't trust a user agreement or mission statement for  sites used primarily dumping ground for porn and photos of ex-wives and girl friends.
     Yes includes you Tumblr and Flickr...

Maybe for my next rant, I'll discuss how blogger is now the walking dead....

Wednesday, March 27, 2013

Find open ports in Windows


From http://www.techrepublic.com


Microsoft Windows XP
Microsoft Windows also offers anetstatcommand that can be executed from the command line to get a list of open ports. The standard MS Windows version ofnetstatis slightly more limited than its Unix-like system counterparts, but still suffices to get a listing of listening services:
  netstat -a | find "LISTENING"
The output of this command should look something like this:
TCP    hostname:epmap           hostname:0               LISTENING
TCP    hostname:microsoft-ds    hostname:0               LISTENING
TCP    hostname:10110           hostname:0               LISTENING
TCP    hostname:netbios-ssn     hostname:0               LISTENING
. . . with “hostname” replaced by the system’s hostname, of course.