New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot create db if RoundhousEFluentDiffingType is InitialDevelopment #12

Closed
codeprogression opened this Issue Jul 16, 2011 · 6 comments

Comments

Projects
None yet
2 participants
@codeprogression

codeprogression commented Jul 16, 2011

(Using roundhouse.lib 0.8.0.332 from nuget.)

Getting this error when running with initialdevelopment on a local database with trusted connection.

INFO: Running RoundhousE v0.8.0.332 against (local) - Settlers.Specs.
INFO: Looking in ......\CP.Settlers.Migrations for scripts to run.

INFO: Setup, Backup, Create/Restore/Drop

INFO: Creating Settlers.Specs database on (local) server if it doesn't exist.
[WARN]: roundhouse.databases.sqlserver.SqlServerDatabase with provider System.Da
ta.SqlClient does not provide a facility for creating a database at this time.
A transport-level error has occurred when sending the request to the server. (pr
ovider: Shared Memory Provider, error: 0 - No process is on the other end of the
pipe.)
[ERROR]: RoundhousE encountered an error.

If I create the db first, RH can drop it but still ends up not being able to recreate.

@ferventcoder

This comment has been minimized.

Show comment
Hide comment
@ferventcoder

ferventcoder Jul 17, 2011

Member

I was having this issue at some point as well, but was able to get past it. That was version 331 though... can you do me a favor and go to where it is setting the console logger and in the parentheses put true for debug. Curious if it is trying twice and getting that issue still.

Member

ferventcoder commented Jul 17, 2011

I was having this issue at some point as well, but was able to get past it. That was version 331 though... can you do me a favor and go to where it is setting the console logger and in the parentheses put true for debug. Curious if it is trying twice and getting that issue still.

@codeprogression

This comment has been minimized.

Show comment
Hide comment
@codeprogression

codeprogression Jul 21, 2011

Looks like it is running more than once. Tried to get log from ProgramData folder, but it is copying an older log rather than using the log just generated. Log copied from console is here: http://dl.dropbox.com/u/15068453/rh.log

codeprogression commented Jul 21, 2011

Looks like it is running more than once. Tried to get log from ProgramData folder, but it is copying an older log rather than using the log just generated. Log copied from console is here: http://dl.dropbox.com/u/15068453/rh.log

@codeprogression

This comment has been minimized.

Show comment
Hide comment
@codeprogression

codeprogression Jul 23, 2011

Rob, I found that if I specify my connection via connectionstring rather than servername/databasename, that is when I get the issue.

codeprogression commented Jul 23, 2011

Rob, I found that if I specify my connection via connectionstring rather than servername/databasename, that is when I get the issue.

@ferventcoder

This comment has been minimized.

Show comment
Hide comment
@ferventcoder

ferventcoder Jul 23, 2011

Member

Turn off app pooling in your connection string. With app pooling, sql server holds onto a connection that no longer has a database when the drop runs. Then it gives it to you, and even though you just successfully recreated the database, the connection was already corrupted.

Member

ferventcoder commented Jul 23, 2011

Turn off app pooling in your connection string. With app pooling, sql server holds onto a connection that no longer has a database when the drop runs. Then it gives it to you, and even though you just successfully recreated the database, the connection was already corrupted.

@codeprogression

This comment has been minimized.

Show comment
Hide comment
@codeprogression

codeprogression Jul 23, 2011

That did the trick. Thanks!

codeprogression commented Jul 23, 2011

That did the trick. Thanks!

@ferventcoder

This comment has been minimized.

Show comment
Hide comment
@ferventcoder

ferventcoder Oct 27, 2011

Member

I believe I finally fixed the issue! cf9ebbd

Member

ferventcoder commented Oct 27, 2011

I believe I finally fixed the issue! cf9ebbd

@ferventcoder ferventcoder modified the milestone: 0.8.5 Jun 3, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment