Attatching ASPNETDB to remote server

Hi there ;

I uploaded my app to host but crashed during membership activities, and i figured out it's cause of ASPNETDB.mdf that is not accessible in remote server, & it's driving me crazy.

As a solution i wanted to know :

is it possible to attatch my db in App_Data to remote server and make use of it just like before?

Please take it into concideration that i've already tried 'aspnet_regsql.exe' and the server gives me error:40 (only local access allowed ).

thanks in advance

No, for the AttacheDBFilename property, currently remote server, HTTP, and UNC path names are not supported. In other words the attached database file must be on the local disk of the SQL machine.|||

thanks lori ,

but i didn't say that i'm goin to set a http or sth alike as db File name . my problem is that my host company doesn't allow remote connections so that i can't use aspnet_regsql.exe .so i just wanted to know that if i send ASPNETDB.mdf to remote server (not necessarily to App_Date folder ) and ask admins to attach it in there, does it work just like the aspnet_regsql.exe ?so that i can then change my connectionstring to the one that my host offers after attaching.

thanks for any help

|||Sorry for misunderstanding Yes, aspnet_sql has nothing to do with database connection for your website, we use aspnet_regsql.exe to create database objects in specified database which can be used for membership. So just make sure connection can be made to the remote SQL Server.|||

So i'll do it .

really thanks for the help

|||

i did that, one final job is to set LocalSqlServer to the new one in the remote server, to do so, follow steps:

ControlPanel > Administrative Tools > Internet Information Services > here choose your website's virtual directory that is somewhere under "Default Web Site"

then right click and choose Properties, on the rightmost tab named "ASP.NET" click the button named "Edit Configuration..." .

on the window that will open, you see the "LocalSqlServer" under "Connection string manager", and it's value is set to the ASPNETDB.mdf that is in the App_Data directory, click on it & edit it to point to the one that is on the remote server .

Generally for those, who aren't allowed to access the db remotely, the best job, i think, is to generate a copy of "ASPNETDB.mdf" locally (In case there is someone else that has taken the name ASPNETDB, change its name) & send it to your remote server and ask them to attach it, then, with the connection string they offer you can have sth like "ASPNETDB.mdf" working remotely.

Thanks lori for the help

attaching DB using single MDF file

Hi there,
I'm trying to attach a DB using a single MDF file. The file was not properly detached as our server had crashed suddenly neither was the a proper backup done..When I try to attach it says
"the file you've specified is not a valid sql server database file" . But another database was restored using a MDF file without any problems ?
Please do get back if anyone may get what the problem likely is ? It'd be of great help. Let me know if my problem was clear or if I've to put it in a different fashion.

Cheers
GaneshOriginally posted by gans_sr
Hi there,
I'm trying to attach a DB using a single MDF file. The file was not properly detached as our server had crashed suddenly neither was the a proper backup done..When I try to attach it says
"the file you've specified is not a valid sql server database file" . But another database was restored using a MDF file without any problems ?
Please do get back if anyone may get what the problem likely is ? It'd be of great help. Let me know if my problem was clear or if I've to put it in a different fashion.

Cheers
Ganesh

what do u mean by
other database was restored using a MDF file without any problems ?
was it the same file which u r trying to restore again??
to me it seems that the database file is corrupted and u will have to look for the most recent backup for the database.|||Harshal,
Its not the same file and its a differnt one . I also reckon it could be corrupt, but do you think it can be repaired by any chance ?
About backup, somehting had happened to hte server it seems , may be some virus and it stopped job schedule on sql server also.
Thanks for any ideas
Ganesh|||Originally posted by gans_sr
Harshal,
Its not the same file and its a differnt one . I also reckon it could be corrupt, but do you think it can be repaired by any chance ?
About backup, somehting had happened to hte server it seems , may be some virus and it stopped job schedule on sql server also.
Thanks for any ideas
Ganesh

In that case u r in a real problem! I haven't heard of repairing a corrupt database file yet.The only solution that I see is to get the latest workable backup from the backup sets and restore them. I hope you have some backups before the job stopped running.
and also once every thing is running, do configure an alert for all the jobs so that their status is mailed to u every time they run.
regards,
Harshal.|||Thanks Harshal .Looks like thats the only option available now.

Attach subscription MDF

Hi,
Our subscriber crashed and they had a quite a bit of work captured after the
last synch up to the publisher. We salvaged the MDF and LDF.
I have tried attaching this subscriber to a new machine which worked fine,
now I want to synch that data with publisher. Is this possible? I cant
seem to get this to work.
Any ideas?
Thanks in advance
Warren Patterson.
it should work. As long as the agents are in place you should be able to
start them up again. I'd take a backup before you do anything however.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Warren Patterson" <des@.newsgroups.nospam> wrote in message
news:e9jzmMJ9EHA.3756@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Our subscriber crashed and they had a quite a bit of work captured after
the
> last synch up to the publisher. We salvaged the MDF and LDF.
> I have tried attaching this subscriber to a new machine which worked fine,
> now I want to synch that data with publisher. Is this possible? I cant
> seem to get this to work.
> Any ideas?
> Thanks in advance
> Warren Patterson.
>
>
|||Thanks Hilary.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uFh%23UUL9EHA.2452@.TK2MSFTNGP14.phx.gbl...[vbcol=seagreen]
> it should work. As long as the agents are in place you should be able to
> start them up again. I'd take a backup before you do anything however.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "Warren Patterson" <des@.newsgroups.nospam> wrote in message
> news:e9jzmMJ9EHA.3756@.TK2MSFTNGP14.phx.gbl...
> the
fine,
>