Error when connecting for the first time

Hi, I get the below error (after clicking login in my home page, so home page works well) when I open my website for the first time after I restart my server or my client machine.

" Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."

From the next time onwards it is connecting without any problems.

can anyone figure out what could be the problem here?

Are you running SqlExpress?

Did you set the service to start when the server starts? Otherwise it may be getting started on first call and that adds overhead (time) and may be the issue.

|||

Yes I use SQLExpress.

Services are fine. It is in autostart mode and so running automatically everytime i restart.

|||

Hmm... more then likely either some service or some precompilation is in need of being done.

If you leave your site untouched for an hour and come back, does it timeout again? Trying to see if it's a service or simply the first-hit drain on the system thats causing the issue.

|||

this happens only when i use for the first timewww.XXXXXX.com...

I missed the below in my first post and added now

"after clicking login in my home page, so home page works well"

|||

Sounds like that's the first call to the DB... so that's most likely the issue.

You may want to hit up the SqlExpress forum...perhaps someone who watches that one will know more but I know I've had it happen in the past but not with regularity... try prefiring a call to the DB from the Application_Start in the global.asax perhaps, to take that initial hit...

Error when clicking OK on edit of task

I've got a package that was imported from SQL 2000 into SQL 2005. I'm trying to edit it in Business Int. Dev Studio. When I open what used to be a data pump step in 2000, I'm able to edit items. However, when I click OK, it puts an error right below the buttons:

"" is not a value type

And it won't let me save my changes. I have no idea where this error is coming from. All the data pumps in this package cause the same error. Your help is appreciated.Found the solution thanks to our server support staff: They noticed that all the global variables (now referred to as inner variables) were missing their type. They had names and values, but no type. To give them a type, we just needed to change the name of the variable and then change it back -- this caused the type dropdown to become active. Then we had a type for each variable as well. I hope this helps others who run into this same issue.|||

arc_dev wrote:

Found the solution thanks to our server support staff: They noticed that all the global variables (now referred to as inner variables) were missing their type. They had names and values, but no type. To give them a type, we just needed to change the name of the variable and then change it back -- this caused the type dropdown to become active. Then we had a type for each variable as well. I hope this helps others who run into this same issue.

Well done for picking this up. Did you use the migration wizard? If so, this is a bug in the migration wizard. Could you report it at Microsoft Connect?

-Jamie

|||I just created a bug report with screen captures of what it does.