I'm analyzing a dump file taken with procdump -ma w3wp on a Windows Server 2008 R2 SP1 machine running .NET 4.
!ASPXPages –ip
Going to dump the HttpContexts found in the heap.
HttpContext Client IP Server IP ThreadId
Total 42 HttpContext objects
This command output list just the headers and no values compared to !ASPXPages which fills in the normal output (but no IP's). Any ideas why this is happening on my dump file?
Related
I have installed Firebird 3.0.2 (x64) and IBExpert 2018.12.15.1.
I'm trying to create a Firebird DB on IBExpert but everytime getting this error:
Unsuccessful execution caused by system error that does not preclude successful execution of subsequent statements.
Error loading plugin Engine12.
Module C:\Program Files\Firebird\Firebird_Server\plugins/Engine12 exists but can not be loaded.*
My configuration:
Server/Protocol
Local, XNet (FB3)
Database
C:\Data\Example.fdb
Connection string
xnet://C:\Data\Example.fdb
Client Library File
C:\Program Files\Firebird\Firebird_Server\WOW64\fbclient.dll
Username
SYSDBA
Password
masterkey
Page size
126384
SQL Dialect 3
How to solve this problem?
This happens to me when I select the firebird fbclient dll from the following location
C:\Program Files\Firebird\Firebird_3_0\WOW64\fbclient.dll
However if I instead (against all sanity and reason) chose what I think ought to be a 64 bit dll, from c:\windows\system32, it works.
ie, client choice:
c:\windows\system32
Now it might seem logical to some readers that system32 could contain a 32 bit dll, but actually almost every dll in there, and probably EVERY dll in there SHOULD be 64 bit, on windows 64 bit systems. However I am guessing that whatever is in there must be a 32 bit fbclient.dll in the main windows 10 system directory.
Microsoft made a now ancient but at the time, kind of odd decision that c:\windows\system32 will be full of 64 bit stuff on Windows XP 64 bit, and has kept it that way. It appears to me there's something wrong with Firebird 3.0.4's installer team's decisions.
I'm just getting started using KDB again. At my old job everything was all set up on the server with a number of tables and I would just query the data. I'm now loading in my own data files and want to be able to query it from a GUI client.
The two I used in the past were QStudio and QPadInsight. For both of these, I need to connect to the server. I'm pretty sure I need to have it listen to localhost since the server is running on my desktop computer where the client is also running. I don't know what port to set it to. Also, do I need to do anything to have the server running other than opening a command prompt and running Q (c:\q\w32\q.q)?
Thanks for the help.
You only need to set the port for connecting it via qpad.
However, you can also load a specific file in that session from the command prompt.
c:\q\w32>q server.q -p 1234 //load the server.q file in q session
KDB+ 3.5 2017.11.30 Copyright (C) 1993-2017 Kx Systems
q)
If you are just bringing up the q session then you have to set the port and load some server-specific code manually.
c:\q\w32>q
KDB+ 3.5 2017.11.30 Copyright (C) 1993-2017 Kx Systems
q)\l server.q
q)\p 1234
Now it can be connected via qstudio or qpad using the connection string `::1234
Check this out to set the QHOME
You can set the QINIT variable to point to some q file that can act as the bootstrap file for all the q sessions you will run on your box (e.g. helper functions)
You can add the commands to a bat file to avoid any manual steps.
set QHOME=C:\q
set QINIT=C:\code\server.q
set PATH=%PATH%;%QHOME%;%QHOME%\w32
q -p 1234
I have been using this connection string with no problem on a number of databases and MS operating systems. Windows Server 2003, 2008 R2 and 2012 R2 Eval, all Express versions.
I am now trying to deploy to a new Windows Server 2012 R2 installation and I am getting some errors. I have the SQL Server 2008 R2 installation on the Windows Server 2012 R2 machine.
My con string:
connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\myDB.mdf;Integrated Security=True;User Instance=False" ProviderName="System.Data.SqlClient"
I think this must have something to do with the installation sequence of the components on the new server.
I have in the past been able to simply copy myDB.mdf to basically any web server and open or access the DB tables. This DB includes an ASP membership for the web site that it is tied to.
Here is the error:
CREATE DATABASE permission denied in database 'master'. An attempt to
attach an auto-named database for file
C:\inetpub\techTran\App_Data\myDB.mdf failed. A database with
the same name exists, or specified file cannot be opened, or it is
located on UNC share.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: CREATE
DATABASE permission denied in database 'master'.
I thought I understood what this error was. I have checked permissions and they match the other servers where this database has been deployed. My SQL Server installations are basically all the same. The only difference here is that this is Windows Server 2012 R2 on a VM. Or I did not install the SQL Server 2008 R2 the same way I have done in the past 5 servers I have set up. (Which I am guessing is probably the case.)
UPDATE: Uninstalled and reinstalled SQL Server and SSMS.
I know there is only one database name on the server called myDB.mdf, so I don't believe the "same name" portion of error. I have added security to the db so that it can be opened and I even installed Visual Studio 2012 on the server to be certain that the db could be opened. I can run the full app on the localhost (server 2012) but I can not access it over a web connection.
I believe the specific error message relating to
CREATE DATABASE permission denied in database 'master'
is the issue.
I have never seen this error before.
I typically assign NETWORK SERVICE account to the database to allow access and this is how this one is set up as well. I also thought this might be a connection string issue. But this same string has worked on 4 different servers now with no changes. Server 2003, 2008 R2, and 2012 (demo platform)(all Express versions), now in production this is failing.
The home page loads and then the login throws the above error.
Your connection string says AttachDbFilename=|DataDirectory|\myDB.mdf. Well, your path must have changed in one place (SQL Server) and not the other (app configuration). AttachDbFilename will try to create a new DB if it can't find that file. That's probably your error.
As an aside, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 all have differences, especially with security and in particular with how SQL Server behaves, but you keep using them interchangeably. That makes it very confusing to tell what's going on. Also, your connection string says Data Source=.\SQLEXPRESS. Is this SQL Server Express? Because that has important differences with most other editions of SQL Server, too. More recent editions are very similar to Standard edition, but the older the edition, the more quirks it has. They're generally considered different beasts.
SOLVED: I am not sure how this happened or perhaps why it didn't happen. But for some reason the installation of SQL did not add the NETWORK SERVICE account to the sysadmin Server Role. I cross referenced this with the SERVER 2003 installation where SQL 2008 R2 is also running, and discovered that the sysadmin SQL Server Role included NETWORK SERVICE in my correctly functioning environment. So once I added the user account to this role, everything came up fine.
I believe this might have been an issue during the installation of SQL 2008 R2. I did specify NETWORK SERVICE, but for some reason it was not provided the role.
I need to create a script that reads some Access DBs and writes some values into a SQL Server DB.
Since I have Office 32 bits installed, I can only install the 32 bit Access provider.
But I want to use the SQL Server snap-ins to run the SQL commands, which are 64 bits.
Now, how can I combine both ? I need to run an Access query using Powershell x86, and send the fetched data to Powershell x64 so that it can insert it to SQL Server.
The only solution I see is dropping the SQL snap-ins, and re-writing the SQL wrappers myself, but that's just sad.
It turns out that the SQL Server snap-ins are outdated, and have been replaced with the SQLPS module.
The latest SQLPS version can be downloaded from here: http://www.microsoft.com/en-us/download/details.aspx?id=35580 (select the PowerShellTools.msi you need).
After installing x86\PowerShellTools.msi, the SQLPS module is available from x86 PowerShell, and has the same features as the "old" add-in (Invoke-SqlCmd...)
I want to un-install completely SQL Server 2008 R2 from my 64bit system. When I tried to install, I experienced a common problem about "INSTALLSHAREDWOWDIR" but I managed to install anyway. Now, I can't un-install.
I even tried cmd but when action is uninstall, it doesn't accept INSTALLSHAREDWOVDIR command.
Here is the error I got;
The INSTALLSHAREDWOWDIR command line value is not valid. Please ensure
the specified path is valid and
different than the INSTALLSHAREDDIR
path.
Note that, this error is NOT for installation, it's for removal of SQL.
Regards