Print Page | Close Window

After upgrading to 3.4 my IIS deployment did not work

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce Classic
Forum Discription: For .NET 2.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=150
Printed Date: 01-Apr-2025 at 9:29am


Topic: After upgrading to 3.4 my IIS deployment did not work
Posted By: Customer
Subject: After upgrading to 3.4 my IIS deployment did not work
Date Posted: 12-Jul-2007 at 11:51am

After upgrading to 3.4 my IIS deployment did not work i.e �unable to connect to remoting server. The server or connection may be down�. I made sure I replaced all the dll references in the solution and in the IIS target directory. I spent quite a lot of time to figure out the error but did not succeed. I removed 3.4 and installed the prev. version 3.3 and is working fine. Trust me I did not change anything other than refreshing the refrences and during my troubleshooting I reinstalled/repaired .Net framework 2.0, reinstalled IIS 6.0 and restarted the system many times.

This was the debug log and it did not proceed further.


Replies:
Posted By: IdeaBlade
Date Posted: 12-Jul-2007 at 11:52am
 
This reply to another customer who had a similar problem may help: 

We renamed a few classes in the IdeaBlade.Persistence namespace in version 3.4.0, and also modified the ServerConsole.exe and ServerService.exe modules.  I�m not sure how you�ve deployed your BOS, so I�ll describe in general what you need to look at.

1) If you�re not using IIS, and you�re not using an app.config on either client or server, make sure that the ServerConsole or ServerService executable on your BOS is from the 3.4.0.3 release.

2) If you�re using IIS, or a client or server side app.config, check that the remoting information in the config file is correct for the renamed classes:

Here�s what the <wellknown> element should look like in the server config file:

<service>

    <wellknown

        mode="Singleton"

        type="IdeaBlade.Persistence.RemotingPersistenceService,

          IdeaBlade.Persistence"

        objectUri="PersistenceServer.rem"

    />

</service>

The type=�� attribute has changed to reflect the new correct class name.  Check the �BreakingChanges� section of the Release Notes for more information on the client-side app.config.

If neither of these options works for you, please let me know.


Print Page | Close Window