Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Master Page Error
jtbob
#1 Posted : Tuesday, 16 June 2009 5:35:48 PM(UTC)
Rank: Member

Joined: 7/02/2008(UTC)
Posts: 26
Location: La Jolla, CA

Hi Roger,

We were trying a master page with the Gallery Server Pro 2.3 version and we were getting a server response error. If we leave default.aspx alone, everything works fine. But if we define a master page and place the GSP object in a container, we get a timeout and an ASP.NET unexpected stop.

Is there something we need to do with master pages, or should we go with an iframe instead?

Let me know if you want me to supply the master page and default.aspx code.

Thanks,
Robert
Roger Martin
#2 Posted : Wednesday, 17 June 2009 12:19:34 AM(UTC)
Roger Martin

Rank: Administration

Joined: 3/08/2007(UTC)
Posts: 3,300
Location: Fort Atkinson, WI

Are you placing the user control inside the master page, or inside a .aspx page that uses a master page?

I think either should work, but I haven't tested it directly in a master page.

If you provide more detail about the error and maybe your master page content, I can help you get to the bottom of this.
Roger Martin
Creator and Lead Developer of Gallery Server Pro
jtbob
#3 Posted : Wednesday, 17 June 2009 3:54:17 AM(UTC)
Rank: Member

Joined: 7/02/2008(UTC)
Posts: 26
Location: La Jolla, CA

Hi Roger,

Here's the code from the master page file:
Code:

<%@ Master Language="C#" AutoEventWireup="true" CodeBehind="GSPMaster.master.cs" Inherits="GalleryServerPro.Web.GSPMaster" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
<title>Untitled Page</title>
    <style type="text/css">
        html, body { margin:0;padding:2px; }
        body { background-color:#f5f5f5; }
    </style>
</head>
<body>
<form id="form1" runat="server">
<div>
<asp:ContentPlaceHolder ID="ContentPlaceHolder1" runat="server">
</asp:ContentPlaceHolder>
</div>
</form>
</body>
</html>


And here is the code from the default.aspx page:

Code:

<%@ Page Language="C#" MasterPageFile="~/GSPMaster.Master" AutoEventWireup="true" CodeBehind="default.aspx.cs" Inherits="Website._Default" %>

<%@ Register TagPrefix="gsp" Namespace="GalleryServerPro.Web" Assembly="GalleryServerPro.Web" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">
        <table border="0" cellspacing="0" cellpadding="0" width="800px">
            <tr>
                <td width="800px">
                    <form id="form1" runat="server">
                        <asp:ScriptManager ID="sm" runat="server" EnableScriptGlobalization="true" />
                        <gsp:Gallery ID="g" runat="server" />
                    </form>
                </td>
            </tr>
        </table>
</asp:Content>


We get a "Server Application Unavailable" error on the browser, and in the event log I get "aspnet_wp.exe (PID: 3524) stopped unexpectedly". It looks like it's timing out. If I return the default.aspx page back to its original configuration, the gallery works fine. We were looking to use a master page so would use that to define place holders for our web sites headers and left side menu.

Thanks,
Robert
Roger Martin
#4 Posted : Wednesday, 17 June 2009 5:03:25 AM(UTC)
Roger Martin

Rank: Administration

Joined: 3/08/2007(UTC)
Posts: 3,300
Location: Fort Atkinson, WI

Do you see any other clues in the event log? I searched google for your error message and there were a lot of hits where this entry was accompanied by other, more specific, entries.

If you remove "<gsp:Gallery ID="g" runat="server" />", does the page work?

I have occasionally seen GSP time out on very slow servers the first time it is run. There is a lot of initialization code that checks for and automatically corrects common issues. When this happens I just try again and it usually goes through the second time. Not sure if this is related to your situation but I thought I would throw it out there.
Roger Martin
Creator and Lead Developer of Gallery Server Pro
jtbob
#5 Posted : Wednesday, 17 June 2009 8:24:55 AM(UTC)
Rank: Member

Joined: 7/02/2008(UTC)
Posts: 26
Location: La Jolla, CA

Hi Roger,

Nope, that's it. The event viewer just show the asp.net stopped unexpectedly error.

Yep, removed the reference to the GSP call and the master page worked showing just the container and the title.

The original default.aspx page worked great, probably took about 10 seconds to load everything initially. But when used with the master page, it will eventually come up with the "Server Application Unavailable" response. Tried bringing up the page multiple times, but no luck, same error response.

Thanks,
Robert
Roger Martin
#6 Posted : Wednesday, 17 June 2009 1:09:38 PM(UTC)
Roger Martin

Rank: Administration

Joined: 3/08/2007(UTC)
Posts: 3,300
Location: Fort Atkinson, WI

You said the original default.aspx worked. Was that in the same web application you are using now? In other words, are you using the same web.config and galleryserverpro.config settings, same support files in the gs directory, etc, so that the *only* difference between working and not working is that one page is stand-alone and the other is inside a master page?

Boy, I don't have any very good ideas, but here are a few troubleshooting ideas:

1. Google the error and see if anything jumps out at you.
2. Download the source code for GSP, compile it and run through the install wizard. Once it is working with the stand-alone default.aspx, add a master page and a new .aspx page that uses the master page. Add the GSP control and see what happens. I can't think of any reason why that wouldn't work.
Roger Martin
Creator and Lead Developer of Gallery Server Pro
jtbob
#7 Posted : Thursday, 18 June 2009 4:27:06 AM(UTC)
Rank: Member

Joined: 7/02/2008(UTC)
Posts: 26
Location: La Jolla, CA

Hi Roger,

Yes, everything else stayed the same. We have the source code, added a master page, modified default.aspx to use the master page file. Recompiled with no errors, but we get the server not responding error.

This is the same error we got when we tried to use a user control with 2.3 that had worked with 2.2. Same error on the web page and same error in the event log.

When I did a Google search the last time for the ASP.NET error, I found a few pages that talked about reinstalling ASP.NET, changing permissions, and running some pretty obscure programs. All of this seemed strange when the gallery alone works great. Add a master page or user control and it dies.

Just curious, did you try the master page and default.aspx code I gave to see if it fails on you end as well? We're trying to find if this problem can be replicated.

We'll keep plunking away to see what we can come up with.

Thanks again,
Robert
Roger Martin
#8 Posted : Thursday, 18 June 2009 6:35:50 AM(UTC)
Roger Martin

Rank: Administration

Joined: 3/08/2007(UTC)
Posts: 3,300
Location: Fort Atkinson, WI

No, I didn't try your code. Maybe I will depending on your answer to this question: Instead of modifying default.aspx, can you add a new web page and have it implement the master page? (Choose Web Content Form from the Add File Dialog.)
Roger Martin
Creator and Lead Developer of Gallery Server Pro
jtbob
#9 Posted : Monday, 22 June 2009 3:14:33 AM(UTC)
Rank: Member

Joined: 7/02/2008(UTC)
Posts: 26
Location: La Jolla, CA

Hi Roger,

Yes, I was able add a new page and have it implement the master page, basically a simple page to show title and some page text. I also added the Gallery Server Pro link and got the same error again.

As a side thing, we loaded the source code (downloaded clean from the download page), and tried just running that from the Visual Studio environment, using our current web.config and galleryserverpro.config files. It would build fine, but keep giving us an error when running saying that SQLite reference was missing even though the web.config file specifies SQL Server. Could this be related to the problem we're having?

Thanks again for your help,
Robert
Roger Martin
#10 Posted : Monday, 22 June 2009 5:24:28 AM(UTC)
Roger Martin

Rank: Administration

Joined: 3/08/2007(UTC)
Posts: 3,300
Location: Fort Atkinson, WI

That might have something to do with it. To remove all traces of SQLite, you need to remove the references in the config files (connection string *and* the provider definitions) AND delete the following dll's from your bin directory:

System.Data.SQLite.DLL
GalleryServerPro.Data.SQLite.dll
Roger Martin
Creator and Lead Developer of Gallery Server Pro
Rss Feed  Atom Feed
Users browsing this topic
Guest
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.