I have followed the instructions here.
To cut a long story short, I just cannot connect to:
https://machine/site/virtual directory/replisapi.dll?diag
I get:
HTTP Error 500.0 - Internal Server Error
Module IsapiModule
Notification ExecuteRequestHandler
Handler ISAPI-dll
Error Code 0x800700c1
Requested URL https://machine:443/site/virtual directory/replisapi.dll
Physical Path C:\inetpub\SQLReplication\replisapi.dll
Logon Method Basic
Logon User machine\user
When browsing to the DLL it does ask for my username and password then shows this error.
We're using a self signed certificate as this is just for testing.
I'm not really a server person so don't know what is going on? There's nothing in the event logs.
Does anyone have any bright ideas of things I could try?
P.S.
I also ran the wizard through SQL 2008 R2 which said it was successful (the wizard only works with IIS6) could there be a conflict between IIS6 and 7 now I have tried to set it up on both?
Ok, this was me being dumb.
After I retraced my steps backwards and unregistered replisapi.dll and moved into a backup directory.
I then removed my module mappings from IIS7.
I then ran the SQL wizard again, which copied replisapi.dll back to the directory.
I noticed it was a different size to the one I was using.
This was because I had got it from "Program Files" but being a 64bit machine the wizard got it from "Program Files(x86)" and now it works.
How simple yet frustrating!
I had to install the 32bit version of the DLL for this to work
I solved this (IIS8 and sql server 2008 x64) by entering ApplicationPool advanced settings and changing "Enable 32-bit Applications" to "True".
Hope this helps. This topic (web sync) is really bad documented
Related
Running SSMS 18.6 causes the program to launch, hang, and then crash. There is no error message given, the program simply terminates before any action is taken and nothing is connected.
I've uninstalled and deleted all files for SSMS, Visual Studio, and SQL Complete.
I tried the 18.6 and 18.5.1 versions of SSMS to no avail.
From https://dba.stackexchange.com/questions/237086/sql-server-management-studio-18-wont-open-only-splash-screen-pops-up/237087#237087 :
I have tried copying the Interop.8.0.dll file from privateassemblies into public. No effect. The line in the config file mentioned here is already commented out in the recent release of SSMS.
From Sql Server Management Studio closes immediately after startup :
I have tried renaming or deleting the package file listed here and removed the relevant registry key. This causes SSMS not to open at all and Windows to issue an alert sound. No other effect.
From https://social.msdn.microsoft.com/Forums/silverlight/en-US/9d0e2459-eb74-46e8-a983-05ae2ba18977/ssms-crashes-on-startup?forum=sqltools :
I tried to repair .NET framework. No effect.
I was only able to install and successfully connect on SSMS version 17.9.1
I can provide Event Viewer details if anyone is willing to help me troubleshoot. I have a .NET Runtime error and two application errors- one is event name CLR20r3 and the other is APPCRASH. Happy to provide more information if needed.
While I can't speak to the exact reason it happened, I found a solution. Whatever the issue was, I discovered it was user specific and limited to my machine. Other users were able to access SSMS as normal on my machine as was I on theirs.
I happened to remember that the AppData folder exists and is just hidden, so I used an administrator account to copy that from a working user and rewrite the files in both of mine that were not used in some background process. This allowed me to once again access SSMS both as my regular user and with my elevated administrator account.
I had this same issue (it happened all of a sudden perhaps due to a windows update). I also tried all the other solutions listed above, but the only thing that worked for me was to uninstall and then reinstall version 7.9.1 like the original poster recommended.
In my case I only have 1 user on the computer, so the other user accounts being able to access was not applicable.
I got the error on the title in my project (which is working well in production on remote server). My local server is Apache, WAMP package.
By default, SQL Server is the database conection so I can't even login. I'm going to share many screenshots because I try many solutions what I found while searching on Google but no one fix my issue.
First of all, the exception message which is almost the same for everyone.
[
So now, my System variables with PHP and Postgrade path.
Here is the PHP Extension list enabled/disabled
And the "extension_dir" on PHP.ini
Finally, laravel files setting up the connection...
start.php -> set my "local" environment
and my local/database.php settings
So I got eveything properly setted (I think) and even like this I can't connect.
Any some other help, please?
Finally, the problem was the arquitecture used on WAMP, should be 32bits, not 64 as I got.
An attempted deployment from (localhost) to (remote server) yielded the Error 27123 which, appears to be a credentials-related issue. After spending several hours the resolution appears to be one of assigning local-to-the-remote server Windows credentials that are used to launch DTEexec.exe. I am using VS2012 Ultimate locally with SQL Server 2014 Developer version and remote SQL version 2012 SP1. However, my attempts have failed so far.
I would VERY much like to be able to deploy to the remote server inside of VS2012, including creating folders, etc but am still at a loss as to the missing piece needed.
We do not have Active Directory set up as the remote is on the Amazon S3 cloud bit other than that is pretty much a plain vanilla setup. I also noted some folks suggested a Kerberos-based response but before I ask our network guru to proceed I'd like at least to get confirmation.
I AM able to manually FTP, install and run packages when remoted in but that stinks for my contractor who I would also like to be able to have me out of his way. s
All found online materials have not yet yielded the one last piece. I suspect my ignorance rather than the lack of a real solution and would appreciate any guidance.
Thanks in advance.
I'm working on a Mavericks machine running a Windows 8.1 VM, trying to install an Oracle Database 12c. The installation runs fine up until it gets to the Database Configuration Assistant portion, where it immediately gives me the error mentioned above, "ORA-12560: TNS:protocol adapter error".
The database installer gives the option to skip a step, so I've tried doing so, and the database installation continues and completes. After it is completed, the Database Configuration Assistant is installed as an application. Running this application gives the same error immediately after setting some of the basic information (like database name, password, etc.).
I'm more or less brand new to Oracle databases, and I have no clue as to what this error might mean, or how to fix it. Does anybody have any idea as to why this error is appearing? I'm eager to provide any more information if it's needed, and would greatly appreciate any ideas or tips.
Thanks!
It seems to me that your oracle database is not up and running, this is a common issue for some first time users, what you need is to setup your database before anything else.
Try going to Control Panel, then Administrative Tools, then Services. Restart both OracleXETNSListener and the OracleServiceXE.
Or just go to start Start >> Run >> type "services.msc"
search for OracleXETNSListener and OracleServiceXE, right click then hit Start.
I am getting a very strange error message at one of our client sites and I am having very little luck trying to figure out what is going on.
Hr=80040154 ERR:OpenDB failed getting
pub version 28627
That is the error message that is from the Merge Agent (IIS) logs. From what I can tell, it is a COM error not being able to load a specific COM object, but I don't know which one. From that, I think this client might not have something installed, but I don't know what that something.
Does any one have any thoughts about what might not be installed? Any other ideas on how to troubleshoot this?
Thanks.
This error could be related to permissions: Did you configure a snapshot share and give the IUSER_Machine name rights to Read and List Files and Folders?
You could restart the synchronization with verbose history logging as described here: How to enable replication agents for logging to output files in SQL Server.
Check these:
Ensure your subscription database is not timing out on auto-grow.
Make sure there is enough space to apply the snapshot on the subscriber
It turns out that there was a DLL that wasn't registered. It was sqloledb.dll (C:\Program Files\Common Files\System\Ole DB). I found this by using the ?diag on the merge agent.
http:////sqlcesa35.dll?diag
That page shows a nice summary of the versions of DLLs that it is using and such. When I did that at the client's site, it showed "unknown" for the version of that DLL. Running regsvr32 on the DLL allowed sqlcesa35.dll to see it and the diag page showed a version number.