Problem with SQL Server Express

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
7/10/2006 11:24:20 AM
Gravatar
Total Posts 68

Problem with SQL Server Express

Hi! I was trying using mojoportal with a sql server express 2005 on my own computer. I got the latest version from svn. Running first time i got a "Time limit exeded" error. I dont know really what i should do to fix this, if it is a sql server thing or maybe on the connection string. How should that look like? Thanks, Christian Fredh
7/11/2006 4:08:02 AM
Gravatar
Total Posts 68

Re: Problem with SQL Server Express

This problem is fixed now. I did not do anything special, I think, but that works now anyway. The database got the default data. Anyway, I got another prolem with getting access to the cashe files (i guess the hole Data folder). I have made this before and I dont see what im doing wrong, how do I configure so the application or ASPNET get access to the Data folder? Thanks, Christian Fredh
7/11/2006 4:16:00 AM
Gravatar
Total Posts 18439

Re: Problem with SQL Server Express

Hi Christian,

Give write permission to ASPNET user and if using Win 2003 server also to IISWPG user for the Data folder and all child objects. After that, type a space in webconfig and save to restart the app.

Right click the folder and chose Properties, then the Security tab. If you don't see the security tab you need to enable simple file sharing. I don't remember off the top of my head where that setting is but google can find it.

Click the Add button then click Advanced then Find to find these users

Hope it helps,

Joe
7/11/2006 5:39:27 AM
Gravatar
Total Posts 18439

Re: Problem with SQL Server Express

Thanks you Joe, i have done that now. I actually had to _disable_ simple file sharing and then i could give the write permission to Data folder. Dont know how I got it working before... I didnt do like this anyway :) Thanks, Christian
7/11/2006 5:45:12 AM
Gravatar
Total Posts 68

Re: Problem with SQL Server Express

I found a bug(?) now... when i post the last message. You are not able to post replies when not logged in, but I was logged out while i was writing the message.. so it got posted as guest.
7/11/2006 6:15:34 AM
Gravatar
Total Posts 68

Re: Problem with SQL Server Express

Hi, another thing. When build is ready i get a message about SampleExternalWebPart.DLL, it was build eather with optimizations enabled or without debug information. Wats that about? I can turn this message off by disable "Warn if no user code on launch" on the debugger settings. Christian
7/11/2006 6:38:09 AM
Gravatar
Total Posts 18439

Re: Problem with SQL Server Express

Hi Christian,

I will look into both of those issues though I have not seen the issue about the samplewebpart it is likely just a build configuration issue.

Joe
You must sign in to post in the forums. This thread is closed to new posts.